[Bug 687998] New: 2.6.39-rc3: suspend to RAM crashes after a few tries (WiFi related?)
https://bugzilla.novell.com/show_bug.cgi?id=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c0 Summary: 2.6.39-rc3: suspend to RAM crashes after a few tries (WiFi related?) Classification: openSUSE Product: openSUSE 11.5 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de CC: rjw@novell.com Found By: Third Party Developer/Partner Blocker: --- Created an attachment (id=425263) --> (http://bugzilla.novell.com/attachment.cgi?id=425263) photograph of a panic On a ThinkPad X200s, suspend to RAM crashes reproducibly after a few cycles (often on the second try). It seems to panic, sometimes the capslock LED is blinking, sometimes I get a panic on the framebuffer, but sometimes it just hangs solid when going into suspend. This happens only on a full boot, init=/bin/bash works fine. It *seems* to be related to WiFi, bluetooth or WWAN, since switching off the killswitch before suspending and switching it on after resume made it survive more cycles than usual (>> 5), but on the next try without switching off the killswitch I got the panic. It does not matter if I run X with fbdev (because of the recently broken Intel X driver) or with the intel driver. I did take a photograph of the panic, but it most likely shows only the aftermath of the catastrophe. Maybe it is helpful anyway. Suspend has been rock solid on this machine before for a long time. -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c1 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |seife@novell.slipkontur.de AssignedTo|kernel-maintainers@forge.pr |rjw@novell.com |ovo.novell.com | --- Comment #1 from Rafael Wysocki <rjw@novell.com> 2011-04-18 22:28:30 UTC --- The kernel is based on 2.6.39-rc, right? -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c2 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|seife@novell.slipkontur.de | --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-04-19 08:24:02 CEST --- Yes, it's 2.6.39-rc3 Even switching off WiFi before suspend has not been reliable (the kernel seemed to lock up hard on plain WiFi activity), so it might not necessarily be a suspend problem. I just thought it would be good to report it early in the cycle :-) I'm back to 2.6.38 for now, but will retest once Kernel:HEAD gets a new build. -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c3 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@novell.com, | |vbotka@novell.com --- Comment #3 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-04-30 15:28:12 CEST --- Still there with 2.6.39-rc5-14, both -desktop and -vanilla (KOTD of today). I found out that it is most probably the bluetooth stuff that's to blame. If I "killall bluetoothd" before suspend (which brings btusb usage count to zero and would allow its unloading), then it never crashes. Otherwise, I get a pretty reproducible kernel panic (visible by blinking capslock, nothing on console). But the bug is not that simple ;-) * unloading btusb, then loading it and starting bluetoothd, then suspending => no crash * then virtually un-/replugging the bluetooth adapter (via thinkpad-acpi module facilities), then suspending => crash Basically the workaround for me is to make sure that bluetooth is disabled (I have configured a hotkey for that), disabling via the gnome bluetooth applet is enough, before suspending. I'm suspecting that something in the btusb autosuspend code fails during suspend to RAM. Unfortunately, I'm not able to get any backtrace or similar at all. This is all with the vanilla kernel, with the SUSE desktop kernel I don't even get the blinking capslock led... To add another data point: if I disable intel modesetting (i915.modeset=0 vga=0), which I tried in order to get a backtrace on plain VGA, then the VESA driver is used by X - and then it does not crash. So I really suspect it's a nasty race condition. Again - this is all with a vanilla kernel, so it is a bad upstream regression. Should I also complain loudly on LKML to avoid 2.6.39 being a show stopper on x200s? Adding Oliver to CC who might know something about btusb suspend code :-) -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|2.6.39-rc3: suspend to RAM |2.6.39-rc3: suspend to RAM |crashes after a few tries |crashes after a few tries |(WiFi related?) |(Bluetooth related?) -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c4 --- Comment #4 from Rafael Wysocki <rjw@novell.com> 2011-05-02 19:50:43 UTC --- Created an attachment (id=427602) --> (http://bugzilla.novell.com/attachment.cgi?id=427602) Bluetooth fix I'm carrying the attached patch locally for a Bluetooth-related resume issue, care to try 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |seife@novell.slipkontur.de -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c5 --- Comment #5 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-05-02 22:50:07 CEST --- Yes. I applied the patch on top of current linus' git and just rebuilt the bluetooth module (in order to save me from a complete rebuild and reboot ;) I'll test it. Should I file a bug on bugzilla.kernel.org? Or is this regression already tracked? (It's actually the first suspend regression I got on this box for almost a year). -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c6 --- Comment #6 from Rafael Wysocki <rjw@novell.com> 2011-05-02 21:17:22 UTC --- It's a known issue (hence the patch ;-)), but I'm not sure what the mainline status of the fix is. Presumably on its way to Linus somewhere. It's https://bugzilla.kernel.org/show_bug.cgi?id=33142 . -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c7 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|seife@novell.slipkontur.de | --- Comment #7 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-05-07 12:44:37 CEST --- Ok, I have been using SUSE's -rc5 with the bluetooth.ko built from linus' master tree for some days (since the modified fix went upstream) and had no problems there. So once 2.6.39-rc6 finishes build and hits the mirrors, this bug should be dealt with. Thanks for the hint on where to look :-) -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c8 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #8 from Rafael Wysocki <rjw@novell.com> 2011-05-09 19:35:19 UTC --- Well, I think our master branch i based on it right now. -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c9 Vinzenz Bargsten <vbargsten@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |vbargsten@freenet.de Resolution|FIXED | --- Comment #9 from Vinzenz Bargsten <vbargsten@freenet.de> 2011-12-25 19:31:20 UTC --- I am using 3.1.0-1.2-default / openSuse 12.1 and I think I still have the bluetooth + suspend problem, but with suspend to disk. Before update I used opensuse 11.4 with kernel up to 3.0.7, bluetooth / radio was definitely a problem. I got used to disabling it via function key before suspending, which makes a successful resume much more likely. Afaik, the function key removes the bluetooth device from usb, the wifi device (seems to be pci-ex) just has no signal. I tested only a few times so far with 3.1.0. I could not resume from disk with enabled bluetooth / radio, from RAM it seems to work. -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c10 Rafael Wysocki <rjw@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #10 from Rafael Wysocki <rjw@suse.com> 2011-12-25 22:35:14 UTC --- So this is a different issue, because the original bug description refers directly to suspend to RAM. Could you please avoid hijacking the existing bug entries and create a separate one for the problem you're seeing? -- 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=687998 https://bugzilla.novell.com/show_bug.cgi?id=687998#c11 --- Comment #11 from Vinzenz Bargsten <vbargsten@freenet.de> 2011-12-26 13:20:28 UTC --- Ok, here it is: https://bugzilla.novell.com/show_bug.cgi?id=738586 -- 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