<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [SKL] Flashing black screen ([drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun)" href="https://bugs.freedesktop.org/show_bug.cgi?id=94605#c84">Comment # 84</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [SKL] Flashing black screen ([drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun)" href="https://bugs.freedesktop.org/show_bug.cgi?id=94605">bug 94605</a> from <a class="email" href="mailto:registo.mailling@gmail.com" title="Mauro Santos <registo.mailling@gmail.com>"> Mauro Santos</a> <pre>(In reply to syphyr from <a href="show_bug.cgi?id=94605#c83">comment #83</a>) > Could you try replacing "intel_iommu=on" with: > intel_iommu=igfx_off > > I also still have problems with intel_iommu=on. I have been trying something alonf those lines, so far I've given a good afternoon with intel_iommu=on,igfx_off and I didn't see any problems, now I'm testing without intel_iommu in the cmdline and I expect to see no problems. If the problem is not solved it is much harder to trigger now, however partially disabling the iommu kind of defeats one of the main points of using it, restricting devices form having full unchecked access to the whole ram. On another note, if I'm not wrong, using intel_iommu=igfx_off is the same as having the iommu completely off so you may want to check dmesg and make sure if the iommu is on or not.</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>