<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL] System hang when screens go into standby" href="https://bugs.freedesktop.org/show_bug.cgi?id=92926#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL] System hang when screens go into standby" href="https://bugs.freedesktop.org/show_bug.cgi?id=92926">bug 92926</a> from <a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>(In reply to Imre Deak from <a href="show_bug.cgi?id=92926#c13">comment #13</a>) > Ok, this one is a separate issue from what the dmc-fixes branch solves. Here > we are trying to access (In reply to Norbert Varzariu from <a href="show_bug.cgi?id=92926#c12">comment #12</a>) > > Created <a href="attachment.cgi?id=119707" name="attach_119707" title="dmesg dmc-fixes branch">attachment 119707</a> <a href="attachment.cgi?id=119707&action=edit" title="dmesg dmc-fixes branch">[details]</a> > > dmesg dmc-fixes branch > > I see three issues in the log: > 1. HPD IRQ storm during booting on both HDMI pins: > "hotplug event received, stat 0x00200000, dig 0x10101012, pins 0x00000020" > "hotplug event received, stat 0x00400000, dig 0x10101210, pins 0x00000040" > > AFAICS you have two HDMI monitors attached, could you confirm? Also could > you still try if it this storm happens on this kernel branch consistently > during boot and whether booting with disable_power_well=0 makes a difference? > > 2. > """ > WARNING: CPU: 0 PID: 109 at drivers/gpu/drm/i915/intel_pm.c:3538 > skl_update_other_pipe_wm+0x1a7/0x1b0 [i915]() > WARN_ON(!wm_changed) > """ > > Looks like some atomic state tracking issue, I think Maarten has a patch for > this. CC'ing him. > > 3. > """ > WARNING: CPU: 3 PID: 1556 at drivers/gpu/drm/i915/intel_uncore.c:606 > hsw_unclaimed_reg_debug+0x69/0x90 [i915]() > Nov 16 15:40:41 desktop.basis kernel: Unclaimed register detected after > writing to register 0x71240 > """ > We are accessing 0x71240 while PW2 is off, which is bogus. Again Maarten may > have an idea here. (In reply to Norbert Varzariu from <a href="show_bug.cgi?id=92926#c16">comment #16</a>) > Created <a href="attachment.cgi?id=119717" name="attach_119717" title="dmesg dmc-fixes branch with enable_power_well=0">attachment 119717</a> <a href="attachment.cgi?id=119717&action=edit" title="dmesg dmc-fixes branch with enable_power_well=0">[details]</a> > dmesg dmc-fixes branch with enable_power_well=0 Thanks. I couldn't reproduce this issue with an SKL/HDMI box. As I understand your bug report was against 4.3 and that should be fixed by disabling the power well support. The patch for that is submitted for mainline already, so I think this bug could be closed. Point 2. above is tracked at: <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL ] WARN_ON(!wm_changed) hit in the WM code with multiple pipes enabled" href="show_bug.cgi?id=89055">https://bugs.freedesktop.org/show_bug.cgi?id=89055</a> Point 1. and 3. are new so we would need to file separate tickets for them, if they can be reproduced with drm-intel-nightly. Wrt. 1 what seems to happen is that your display is woken up after DPMS off due to the HPD IRQ storm. If you didn't see this storm on earlier kernels it would make sense to bisect it starting from drm-intel-nightly.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>