<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [bdw] GPU HANG: ecode 8:0:0x86dffffd, in Xorg" href="https://bugs.freedesktop.org/show_bug.cgi?id=105155#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [bdw] GPU HANG: ecode 8:0:0x86dffffd, in Xorg" href="https://bugs.freedesktop.org/show_bug.cgi?id=105155">bug 105155</a> from <a class="email" href="mailto:elizabethx.de.la.torre.mena@intel.com" title="Elizabeth <elizabethx.de.la.torre.mena@intel.com>"> Elizabeth</a> <pre>Well I found interesting that this messages are just before the hang report, from dmesg: [ 154.524158] DMAR: DRHD: handling fault status reg 3 [ 154.524160] DMAR: [DMA Read] Request device [00:02.0] fault addr 38d000 [fault reason 05] PTE Write access is not set And looking around I believe I found why you have to use the intel_iommu=igfx_off: "On HPE ProLiant Gen9-series servers running Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, SUSE Linux Enterprise Server 11 SP3, or SUSE Linux Enterprise Server 12 with the I/O Memory Management Unit (IOMMU) option Enabled in the ROM-Based Setup Utility (RBSU) and with "intel_iommu=on" added to the Linux kernel boot parameters, the IP addresses assigned to interface will not be accessible and a message similar to "CPU stuck" may be displayed on the console. In addition, DMAR fault messages are logged in the /var/log/messages as follows: > dmar: DRHD: handling fault status reg 2 > dmar: DMAR:[DMA Write] Request device [02:00.1] fault addr 791dc000 > DMAR:[fault reason 05] PTE Write access is not set > dmar: DMAR:[DMA Write] Request device [02:00.1] fault addr 791dc000 > DMAR:[fault reason 05] PTE Write access is not set > dmar: DMAR:[DMA Write] Request device [02:00.1] fault addr 791dc000 > DMAR:[fault reason 05] PTE Write access is not set This occurs because of a known limitation that the bnx2x driver has with the Option Card Black Box - Active Health (OCBB) feature when IOMMU is enabled. The network adapter firmware will attempt to access a memory area that is no longer assigned the network devices when bringing up/down the interface or loading/unloading the driver. When this occurs, a reboot is required." Information from here <a href="https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04565693">https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04565693</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>