3.4.0-rc7 regression: bluetooth vs. s2ram

From: Pavel Machek
Date: Tue May 15 2012 - 09:15:28 EST


In 3.4-rc7, if I suspend while bnep0 over btusb is connected, then
resume, system dies with a backtrace. (Unfortunately, it is not
exactly easy to capture).

If I suspend without bnep0 active, resume works.

(This has worked before, but "before" may mean 3.2 in this case).

Can someone test/reproduce this? Ideas?


PS: Under normal suspend/resume, I see these warnings in the
log. Maybe relevant?

ehci_hcd 0000:00:1d.7: GetStatus port:7 status 003002 0 ACK POWER OWNER sig=se0 CSC
usb 5-2: finish reset-resume
uhci_hcd 0000:00:1d.3: port 1 portsc 0093,00
usb 5-1: finish reset-resume
usb 5-2: reset full-speed USB device number 3 using uhci_hcd
usb 5-2: ep0 maxpacket = 8
usb 5-1: reset full-speed USB device number 2 using uhci_hcd
btusb 5-1:1.0: no reset_resume for driver btusb?
btusb 5-1:1.1: no reset_resume for driver btusb?
btusb 5-1:1.0: forced unbind
usb usb2: suspend_rh (auto-stop)
usb usb3: suspend_rh (auto-stop)
usb usb4: suspend_rh (auto-stop)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/