[Bug 826481] New: Attempting to hibernate Dell Precision M6500 crashes system
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c0 Summary: Attempting to hibernate Dell Precision M6500 crashes system Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: rlk@alum.mit.edu QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=545378) --> (http://bugzilla.novell.com/attachment.cgi?id=545378) lsmod output User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Attempting to hibernate my Dell M6500 consistently results in a system crash. The screen goes to the "snapshotting system", and then immediately blanks, the capslock and one of the other LEDs flash for maybe 5 seconds, and the system powers off without having saved state. I usually do this via KDE, but it happens also if I run it by hand. Reproducible: Always Steps to Reproduce: 1.Suspend from the KDE applet or acpi command 2.Watch system crash 3. Actual Results: System crashes without saving state. Expected Results: System should save state. uname -a output: Linux rlk-mobile.rlk 3.7.10-1.16-desktop #1 SMP PREEMPT Fri May 31 20:21:23 UTC 2013 (97c14ba) x86_64 x86_64 x86_64 GNU/Linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c1 --- Comment #1 from Robert Krawitz <rlk@alum.mit.edu> 2013-06-24 13:42:40 UTC --- Created an attachment (id=545380) --> (http://bugzilla.novell.com/attachment.cgi?id=545380) /etc/suspend.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c2 --- Comment #2 from Robert Krawitz <rlk@alum.mit.edu> 2013-06-24 13:43:22 UTC --- Created an attachment (id=545381) --> (http://bugzilla.novell.com/attachment.cgi?id=545381) /var/log/pm-suspend.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c3 --- Comment #3 from Robert Krawitz <rlk@alum.mit.edu> 2013-06-24 13:44:58 UTC --- Created an attachment (id=545384) --> (http://bugzilla.novell.com/attachment.cgi?id=545384) Output of YaST hardware information -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c Robert Krawitz <rlk@alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Critical -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c4 --- Comment #4 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-04 01:18:20 UTC --- Created an attachment (id=546743) --> (http://bugzilla.novell.com/attachment.cgi?id=546743) More debug information on hibernate. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |bpetkov@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c5 Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov@suse.com --- Comment #5 from Borislav Petkov <bpetkov@suse.com> 2013-07-15 16:47:20 UTC --- Was this box ever able to suspend to disk properly? Also, does this work (you need to run it as root): echo "shutdown" > /sys/power/disk echo "disk" > /sys/power/state Also, can you try the latest upstream 3.10 kernel? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c6 --- Comment #6 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-15 17:05:14 UTC --- 1) The box was able to suspend with 12.2 (and probably also 12.1, but I don't remember whether I actually had 12.1 installed on this laptop). 2) Those two commands resulted in the same failure. By "latest upstream kernel", do you mean the kernel from Kernel:HEAD/standard? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c7 --- Comment #7 from Borislav Petkov <bpetkov@suse.com> 2013-07-15 17:20:21 UTC --- Yep, http://kernel.opensuse.org/packages/master. Btw, you could try the daily builds here: http://download.opensuse.org/repositories/Kernel:/HEAD/standard/x86_64/ Also, are you able to connect this box over a serial port and collect full dmesg of such a suspend run? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c8 --- Comment #8 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-15 18:01:39 UTC --- I'll try Kernel:/HEAD/standard at my next opportunity. Unfortunately, no serial port on this laptop (2xUSB3, 2xUSB2, 1x1394, 1x100?0?baseT, 1xVGA, 1xDisplayPort). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c9 --- Comment #9 from Borislav Petkov <bpetkov@suse.com> 2013-07-15 20:51:30 UTC --- Ok, thanks. About the logging part - when it comes to it, we can try the blockconsole bits with which you can log to an usb stick. But for that we'll have to build our own kernel. Which we will :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c10 --- Comment #10 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-16 01:02:08 UTC --- Works fine with Linux rlk-mobile.rlk 3.10.1-1.g062e800-desktop #1 SMP PREEMPT Sun Jul 14 07:09:42 UTC 2013 (062e800) x86_64 x86_64 x86_64 GNU/Linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c11 --- Comment #11 from Borislav Petkov <bpetkov@suse.com> 2013-07-16 13:06:08 UTC --- Ok, good. So, are you fine running this kernel (you can easily update it as often as you can for we do have the daily builds) or would you rather want to stick with 3.7.10 and bisect the issue until we've found the offending commit? Bear in mind that bisection is a rather time-consuming process which involves building and booting max. 15ish kernels in our case and there's no guarantee for success :-) Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c12 --- Comment #12 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-16 13:37:30 UTC --- Bisecting kernels is indeed a very time-consuming process that I want to avoid if practicable. I did it plenty 15 years ago (although it was a somewhat faster process then), and I've also done it professionally. What level of QA do you do on the kernel head vs. the baseline kernel (in addition to what upstream does)? And does the stock kernel get any additional patches or other changes that the kernel head doesn't. Regardless, I'd like this bug left open so that if anyone else hits it they can find it more easily. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c13 Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jeffm@suse.com InfoProvider| |rlk@alum.mit.edu --- Comment #13 from Jeff Mahoney <jeffm@suse.com> 2013-07-16 12:05:38 EDT --- The upstream kernel doesn't get any patches that we don't carry. It's a rare thing for us to /revert/ an upstream change in one of our releases that isn't also reverted in a -stable update. The QA that goes into openSUSE is mostly by our users during the beta cycles. We try to minimize the number of patches we apply on top of the official Linux release we use as a base. "Our users" includes SUSE developers, but our core responsibility is to develop and maintain our enterprise products since that's what keeps the lights on in the offices. We try to eat our own dog food as much as possible, but most of the openSUSE bugs tend to be with end-user consumer hardware that may not be available to testers and/or developers. Since 3.10 works for you, we'd like to track down what the real fix is and incorporate it into the 12.3 release, but without access to the hardware or detailed logs describing the problem, it's basically impossible for us to do that without help from bug reporters. From the information you've provided, we only know that it /is/ crashing. It could be any driver on your system. Another way to narrow it down without bisecting it, would be to gradually unload drivers and try to reproduce the problem. Once you can suspend successfully, report the driver that made the difference, and we can look at the changes to it between 3.4 and 3.7 to identify a potential failure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c14 --- Comment #14 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-16 16:15:09 UTC --- The most obvious thing to do would be to start by booting single user and trying to suspend from there. Note that the Precision laptops are classified as "mobile workstations", and are not typically consumer products. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c15 --- Comment #15 from Borislav Petkov <bpetkov@suse.com> 2013-07-16 16:33:26 UTC --- (In reply to comment #14)
The most obvious thing to do would be to start by booting single user and trying to suspend from there.
Whatever helps to narrow this down. Right now we have no idea where the issue happens. What you could also do is go through the different suspend test modes in Documentation/power/basic-pm-debugging.txt and report. That same file also explains how to do logging with, say firewire, as this is what you have. Alternatively, you can use netconsole: Documentation/networking/netconsole.txt
Note that the Precision laptops are classified as "mobile workstations", and are not typically consumer products.
What does this have to do with anything? HTH. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c16 --- Comment #16 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-16 17:00:06 UTC --- Since suspend works fine, any particular suggestions? I mentioned the "mobile workstation" in the context of it perhaps being more popular among corporate users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c17 --- Comment #17 from Borislav Petkov <bpetkov@suse.com> 2013-07-16 17:06:34 UTC --- (In reply to comment #16)
Since suspend works fine, any particular suggestions?
Documentation/power/basic-pm-debugging.txt, section a) especially. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c18 --- Comment #18 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-16 18:45:28 UTC --- So here's what I've found so far. 1) This happens in single user mode too (FAIL). 2) Appending processor.max_cstate=1 succeeds in hibernation (SUCCESS) 3) Platform test mode succeeds, processors test mode fails. So it looks like the problem lies somewhere in processor handling. The next obvious thing for me too try would be disabling hyperthreading. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c19 --- Comment #19 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-16 18:56:46 UTC --- Hyperthreading makes no difference. Again, note that suspend to RAM works just fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c20 --- Comment #20 from Borislav Petkov <bpetkov@suse.com> 2013-07-16 22:07:19 UTC --- Interesting. ACPI-related. (what else, I wonder :-() I'm afraid the only thing we're left with is bisection. You could try the vanilla 12.3 kernel here: http://download.opensuse.org/repositories/Kernel:/openSUSE-12.3/standard/x86... to check if it still hangs. Then, according to the result, you could try the major kernel releases 3.8 and 3.9 to cut down some of the patch space and save yourself a couple of bisection steps. Then, once you've found the major good and bad revisions, you can start bisecting as it is described in the git-bisect manpage. Feel free to ask any questions if something's not clear. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c21 --- Comment #21 from Robert Krawitz <rlk@alum.mit.edu> 2013-07-18 01:03:13 UTC --- That's going to be very time-consuming, and I'm not sure when I'm going to get to it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c22 Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rlk@alum.mit.edu | --- Comment #22 from Borislav Petkov <bpetkov@suse.com> 2013-07-23 20:44:00 UTC --- Closing. Please reopen if needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826481 https://bugzilla.novell.com/show_bug.cgi?id=826481#c23 Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |UPSTREAM --- Comment #23 from Borislav Petkov <bpetkov@suse.com> 2013-07-23 20:44:59 UTC --- Ok, now closing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com