Summary: | Hibernating while utilising i915 with modeset=1 results in crash. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Volker Gronau <vjay> | ||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||
Version: | unspecified | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | HSW | i915 features: | power/suspend-resume | ||||||
Attachments: |
|
Description
Volker Gronau
2016-06-08 18:39:13 UTC
Correction: kernels from 3.9 -> Kernel 3.19 I found this, somebody reporting the same issue having a Toshiba laptop too. https://bugs.freedesktop.org/show_bug.cgi?id=94203 Maybe it helps. On 01.org it is advised to open a separate report anyway. (In reply to Volker Gronau from comment #1) > I found this, somebody reporting the same issue having a Toshiba laptop too. > https://bugs.freedesktop.org/show_bug.cgi?id=94203 > > Maybe it helps. On 01.org it is advised to open a separate report anyway. That one is Ironlake, this one is Haswell. (In reply to Volker Gronau from comment #0) > Created attachment 124405 [details] > ZIP files containing screenshots and dmesg of system startup For future reference, please attach each file directly, unpacked. > Very seldom the display comes up after this and a kernel message could be > seen. I took a screenshot (literally) because you cannot write to the hard > disk anymore. Whatever you do causes the system to fully die. Unfortunately, the screenshots do not contain the full backtrace. :( > Sadly I saw the instruction for posting bug reports utilising drm.debug=0x1e > too late. As I already mentioned it is a rarity to capture a kernel panic at > all but I try to catch one with this mode set. Please attach such a dmesg running drm-intel-nightly over a hibernate-resume sequence even if it doesn't result in a crash; it may provide valueable information anyway. > (If somebody in the future experiences the same problem and it was never > fixed with this https://github.com/vjay82/Linux-i915-Backlight-Control you > can at least control the backlight but anyway you will loose acceleration.) I can't recommend anyone using intel_reg for anything except testing and debugging. Created attachment 124425 [details]
dmesg of hibernate and resume cycles
I did add the proposed kernel parameters "drm.debug=0x1e log_buf_len=1M", took a dmesg of the system startup and let it continually log into the file.
Each time i cycled i echoed it into the file too.
Does this help? Can I provide sth else?
I forgot to mention it: As you can see in the truncated file, after the third cycle the system did not come back. The screen stayed black and it did not answer when pinged. I was asking if I can provide more specific information because I prefer contributing that over randomly crashing the machine and hoping for another chance to screenshot it. fixed with today's nightly |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.