[Bug 91585] [BDW] System hard lock-up on resume from suspend

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91585

--- Comment #16 from Jerome <an.inbox at free.fr> ---
Hi Joonas. Regarding your comment #14, the lack of interaction does help. I
tried 3 things:

1) as suggested, from boot I waited until KDM logging screen. From there, with
no interaction I did suspend to disk / resume cycles using only the power
button (keyboard for DM crypt unlock at boot too). No lock-up in 40 cycles.

2) then I logged in KDM, until I got my KDE session. From there, I tried the
same: no interaction, suspend/resume cycles using the power button only. No
lock-up in 40 cycles too.

3) from there, I continued doing the suspend/resume cycles the way I used to
before. It has very little interactions: at the beginning I check hw
acceleration with glxinfo, kernel version, just to make sure I have the right
environment. Then open a konsole. At each cycle I do a "date ; echo N" where N
is the cycle number, just to keep track. Sometimes I clear the notifications,
and once in a while browse the web (uncommon, not correlated with the lock-up
as far as I can tell). So really limited interaction, mostly it's key up in
konsole to get the previous command, edit the number and type return. I got a
lock-up at the 8th resume this way.

So interaction does seem a part of it. If you'd like me to try something else,
let me know.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151008/31eb45cc/attachment.html>