[Bug 65496] [HSW] resume from s4 sporadically causes call trace and system hang, with warm boot

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Oct 10 07:23:02 CEST 2013


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

--- Comment #42 from shui yangwei <yangweix.shui at intel.com> ---
Created attachment 87366
  --> https://bugs.freedesktop.org/attachment.cgi?id=87366&action=edit
netconsole  grab information

(In reply to comment #41)
> (In reply to comment #39)
> > (In reply to comment #37)
> > > Hi
> > > 
> > > Can you please try the patches from comments 22 and 23 form bug
> > > https://bugzilla.kernel.org/show_bug.cgi?id=59321 ?
> > > 
> > > Thanks,
> > > Paulo
> > 
> > Addition: 
> > ------------------
> > No matter patches from comment 22 only or with 23, I find my HSW Desktop
> > failed to suspend from S4, I saw indicator light output is 0004, and the fan
> > isn't stop. I also tried the latest -next-queued without patches, it can
> > resume but with call trace and hang at first round.
> 
> Can you please push the branch you tested somewhere so I can confirm the
> patches are indeed correct.
> 

Oh, all my tests are based on -next-queued latest and the patches also applied
on it.

The commit be used yesterday:
--------------------
commit a94b013b91de055572183c6772865123fa955027
Author: Paulo Zanoni <paulo.r.zanoni at intel.com>
Date:   Thu Sep 19 17:03:06 2013 -0300

    drm/i915: wait for IPS_ENABLE when enabling IPS

    At the end of haswell_crtc_enable we have an intel_wait_for_vblank
    with a big comment, and the message suggests it's a workaround for
    something we don't really understand. So I removed that wait and
    started getting HW state readout error messages saying that the IPS
    state is not what we expected.



> Also, can you collect the error state?

OK, get the errors through netconsole. I find there's call trace. You could
find the messages from the attachment.

[   65.311787] [ BUG: systemd-udevd/2856 still has locks held! ]
[   65.311810] 3.12.0-rc3_drm-intel-next-queued_a94b01_20131009+ #1 Not tainted
[   65.311836] -------------------------------------
[   65.311854] 2 locks held by systemd-udevd/2856:
[   65.311872] Freezing user space processes ...
[   65.311872]  #0:  (microcode_mutex){+.+.+.}, at: [<ffffffffa039b0a7>]
microcode_init+0xa7/0x1b4 [microcode]
[   65.311945]  #1:  (subsys mutex#4){+.+.+.}, at: [<ffffffff81415ee2>]
subsys_interface_register+0x51/0xd9
[   65.311992]
[   65.311992] stack backtrace:
[   65.312010] CPU: 1 PID: 2856 Comm: systemd-udevd Not tainted
3.12.0-rc3_drm-intel-next-queued_a94b01_20131009+ #1
[   65.312048] Hardware name: Intel Corporation Shark Bay Client
platform/SthiPpvRsvd2, BIOS HSWLPTU1.86C.0120.R00.1303312001 03/31/2013
[   65.312092]  ffff880438dbdee0 ffff88003731da78 ffffffff817f313c
0000000000000006
[   65.312126]  ffff880438dbdee0 ffff88003731da98 ffffffff8108df33
0000000000000004
[   65.312160]  0000000000000000 ffff88003731db08 ffffffff8104df35
ffff88003731dad8
[   65.312194] Call Trace:
[   65.312208]  [<ffffffff817f313c>] dump_stack+0x46/0x58
[   65.312230]  [<ffffffff8108df33>] debug_check_no_locks_held+0x8f/0x93
[   65.312255]  [<ffffffff8104df35>] usermodehelper_read_trylock+0xa9/0xfa
[   65.312282]  [<ffffffff810581e5>] ? __init_waitqueue_head+0x50/0x50
[   65.312308]  [<ffffffff814211bc>] _request_firmware+0x285/0x880
[   65.312331]  [<ffffffff81421847>] request_firmware+0x38/0x4c

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20131010/0c057acd/attachment.html>


More information about the intel-gfx-bugs mailing list