[Bug 91585] [BDW] System hard lock-up on resume from suspend
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Aug 20 03:27:51 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=91585
Jerome <an.inbox at free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
i915 platform| |BDW
--- Comment #6 from Jerome <an.inbox at free.fr> ---
With Intel kernel 4.2.0rc5, with old driver 2.21.15 (so LLVMpipe for 3D): I had
a lock-up at the 3rd resume (long hibernations, > 1h). I then tried quick
suspend/resume cycles and got 2 lock-ups in 6 cycles.
I then update the X Intel driver to 2.99.917 (still with Intel kernel
4.2.0rc5). Because glxgears may be too light to make a difference, I installed
and ran Tux racer. Then did suspend/resume cycles, mostly in short succession
but with some pauses of a few minutes at times: it locked-up at the 22nd resume
only.
So, to resume:
- the issue occurs both with LLVMpipe (X driver 2.21.15) and real hardware
acceleration (X driver 2.99.917). Also both with kernels 4.1.3 (Debian testing)
and Intel 4.2.0rc5, all 4 combinations tested;
- having running 3D clients when suspending does not seem to increase the
likelihood of a lock-up;
- the lock-up seems to happen early, before the mode switch to a graphical
setting (still in console mode when it locks up). By this I mean that anytime I
saw the glitch/flicker that happens when switching to graphical mode, then the
resume went fine (no lock-up);
- the lock-up frequency is highly variable, it's hard to make reliable
conclusion based on it. So ignore my previous comment on getting lock-up after
a long suspend duration, it's likely just chance and not relevant.
Please let me know how how you want to proceed here. Thanks
--
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/20150820/40080bed/attachment.html>
More information about the intel-gfx-bugs
mailing list