<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 8, 2019, at 2:19 PM, Stefano Zampini <<a href="mailto:stefano.zampini@gmail.com" class="">stefano.zampini@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">You can circumvent the problem by using a sequential solver for it. There's a command line option in petsc as well as API that allows you to do so. -mat_mumps_icntl_13 1</span></div></blockquote></div><br class=""><div class="">Stefano, </div><div class=""><br class=""></div><div class=""> Do you know if there is a performance penalty to using this option as opposed to fixing it with the patch? </div><div class=""><br class=""></div><div class="">-Manav</div></body></html>