<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [v4.13 ARCH] GPU HANG: DMAR: DRHD: handling fault status reg 3 (arch reverted the use of intel_iommu=igfx_off)" href="https://bugs.freedesktop.org/show_bug.cgi?id=103076#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [v4.13 ARCH] GPU HANG: DMAR: DRHD: handling fault status reg 3 (arch reverted the use of intel_iommu=igfx_off)" href="https://bugs.freedesktop.org/show_bug.cgi?id=103076">bug 103076</a> from <a class="email" href="mailto:carstenmattner@gmail.com" title="Carsten Mattner <carstenmattner@gmail.com>"> Carsten Mattner</a> <pre>(In reply to Carsten Mattner from <a href="show_bug.cgi?id=103076#c25">comment #25</a>) > Been trying to provoke it under two different Wayland compositors for > several hours (same workload as yesterday), and it seems much harder to > trigger there (same drm-tip kernel). Despite the familiar PF_MEMALLOC fault, after having run Wayland compositor for 3+ hours, and having switched to Xorg after that, no reboot inbetween, I still haven't hit the hang yet. Uneducated speculation would be that using Wayland first after boot put the stack in a more forgiving state and increased the time and operations needed for it to trigger. Wayland was run natively via its drm backend. I'll reboot soon for other reasons, but if Wayland manages to hide the drm regression, I might have to use it as the main daily driver, although there's no drop-in replacement for my usual X11 window manager environment (yet).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>