<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW desktop] Resume from s4 causes call trace and system hang, with cool boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=63586#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW desktop] Resume from s4 causes call trace and system hang, with cool boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=63586">bug 63586</a> from <a class="email" href="mailto:cancan.feng@intel.com" title="cancan,feng <cancan.feng@intel.com>"> cancan,feng</a> <pre>(In reply to <a href="show_bug.cgi?id=63586#c14">comment #14</a>) > It's strange that the first jpeg of a calltrace is completely different from > the 2nd one. Is it always different like that? > > Also, the 2nd calltrace is cut off at the beginning. Can you try to capture > the top, too? There's a special kernel option to slow down kernel debug > output to the console, see the boot_delay option in > Documentation/kernel-parameters.txt (I hope it also works in general). I'm sorry I didn't make it clear. The first jpeg and 2nd jpeg are from two machines of HSW desktop, the issue have different symptoms on them, I think we could focus on the first jpeg of "Call Trace info" instead of "S4 resume with call trace and system hang", because the symptom on this machine is a little easier to reproduce. Bisect info is from this machine too. I think the issue is a little complicated, and I'm not sure how to define it. At first, I thought system hang after resume from S4, because the machine can't be accessed by ssh, and have no response by keyboarding. But sometimes it will probably flash messages on screen slowly...So I got information of system coolboot and resume from S4 by serial port, I attached it in the attachment. If you need any information, please feel free to let me know.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>