[Bug 59321] S4 broken with Haswell

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Thu Jun 6 23:21:57 PDT 2013


https://bugzilla.kernel.org/show_bug.cgi?id=59321





--- Comment #11 from Takashi Iwai <tiwai at suse.de>  2013-06-07 06:21:57 ---
(In reply to comment #8)
> Ok, so I have been playing with this for some time today. The machine I've used
> has only an eDP monitor.
> 
> I enabled a bunch of debug options in the Kernel, including kmemleak. I could
> reproduce the bug a few times, and so far I notice that the S4 problem only
> happens *after* I see kmemleak complains about some weird stuff that happens
> when we're trying to turn the eDP panel power on. I have seen this 3 times:
> 
> - Boot the machine
> - Check for kmemleak on dmesg
> - S4 suspend
> - Boot again and check for kememleak on dmesg
> - So far, I have only seen crashes after dmesg complains about kmemleak
> 
> Another thing I have to point is that the crash happens when I'm already back
> to X, many seconds after the real reboot.
> 
> Do you also observe that?

OK, will try with kmemleak.  I already tried other debug options but it didn't
catch anything special before the crash.

The crashing behavior isn't always same.  As stated in the bug description,
with a luck, you can get the Oops message.  With a bad luck, the machine
immediately crashes during the resume.  Possibly because lots of tasks run via
pm-utils resume hooks.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list