<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW] resume from s4 sporadically causes call trace and system hang, with warm boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=65496#c42">Comment # 42</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW] resume from s4 sporadically causes call trace and system hang, with warm boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=65496">bug 65496</a> from <a class="email" href="mailto:yangweix.shui@intel.com" title="shui yangwei <yangweix.shui@intel.com>"> shui yangwei</a> <pre>Created <a href="attachment.cgi?id=87366" name="attach_87366" title="netconsole grab information">attachment 87366</a> <a href="attachment.cgi?id=87366&action=edit" title="netconsole grab information">[details]</a> netconsole grab information (In reply to <a href="show_bug.cgi?id=65496#c41">comment #41</a>) > (In reply to <a href="show_bug.cgi?id=65496#c39">comment #39</a>) > > (In reply to <a href="show_bug.cgi?id=65496#c37">comment #37</a>) > > > Hi > > > > > > Can you please try the patches from comments 22 and 23 form bug > > > <a href="https://bugzilla.kernel.org/show_bug.cgi?id=59321">https://bugzilla.kernel.org/show_bug.cgi?id=59321</a> ? > > > > > > Thanks, > > > Paulo > > > > Addition: > > ------------------ > > No matter patches from <a href="show_bug.cgi?id=65496#c22">comment 22</a> 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 <<a href="mailto:paulo.r.zanoni@intel.com">paulo.r.zanoni@intel.com</a>> 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</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>