2.6.11-rc[23]: swsusp & usb regression
Hi!
In 2.6.11-rc[23], I get problems after swsusp resume:
Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0: over-current change on port 1 Feb 4 23:54:39 amd kernel: done Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2
After unplugging usb bluetooth key, machine hung. Sysrq still responded with help but I could not get any usefull output.
Parts of .config:
# CONFIG_USB_IRDA is not setCONFIG_USB=y
# CONFIG_USB_DEBUG is not setCONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not setCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_MIDI is not setCONFIG_USB_ACM=yCONFIG_USB_PRINTER=yCONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not setCONFIG_USB_STORAGE_SDDR09=y
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not setCONFIG_USB_HID=y
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Hi!
Quoted 10 lines
In 2.6.11-rc[23], I get problems after swsusp resume:
Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0: over-current change on port 1 Feb 4 23:54:39 amd kernel: done Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2
Quoted 2 lines
After unplugging usb bluetooth key, machine hung. Sysrq still responded with help but I could not get any usefull output.
I tried deselecting CONFIG_USB_EHCI_HCD, and got repeating stream of
Feb 5 00:21:17 amd kernel: Restarting tasks... done Feb 5 00:21:17 amd kernel: hub 3-0:1.0: over-current change on port 1 Feb 5 00:21:18 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:18 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 5 00:21:20 amd kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled Feb 5 00:21:20 amd kernel: hub 1-0:1.0: over-current change on port 1 Feb 5 00:21:21 amd kernel: hub 1-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:21 amd kernel: hub 1-0:1.0: over-current change on port 2 Feb 5 00:21:23 amd kernel: hub 1-0:1.0: connect-debounce failed, port 2 disabled Feb 5 00:21:23 amd kernel: hub 2-0:1.0: over-current change on port 1 Feb 5 00:21:24 amd kernel: hub 2-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:24 amd kernel: hub 2-0:1.0: over-current change on port 2 Feb 5 00:21:24 amd kernel: usb 2-2: USB disconnect, address 2 Feb 5 00:21:26 amd kernel: hub 2-0:1.0: connect-debounce failed, port 2 disabled Feb 5 00:21:26 amd kernel: hub 3-0:1.0: over-current change on port 1 Feb 5 00:21:28 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:28 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 5 00:21:29 amd kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled Feb 5 00:21:29 amd kernel: hub 1-0:1.0: over-current change on port 1 Feb 5 00:21:31 amd kernel: hub 1-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:31 amd kernel: hub 1-0:1.0: over-current change on port 2 Feb 5 00:21:32 amd kernel: hub 1-0:1.0: connect-debounce failed, port 2 disabled Feb 5 00:21:32 amd kernel: hub 2-0:1.0: over-current change on port 1 Feb 5 00:21:34 amd kernel: hub 2-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:34 amd kernel: hub 2-0:1.0: over-current change on port 2 Feb 5 00:21:35 amd kernel: hub 2-0:1.0: connect-debounce failed, port 2 disabled Feb 5 00:21:35 amd kernel: hub 3-0:1.0: over-current change on port 1
...in syslog.
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Quoted 12 lines · Pavel Machek
Hi!
In 2.6.11-rc[23], I get problems after swsusp resume:
Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0: over-current change on port 1 Feb 4 23:54:39 amd kernel: done Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2
Quoted 2 lines
After unplugging usb bluetooth key, machine hung. Sysrq still responded with help but I could not get any usefull output.
Your logs don't indicate which host controller driver is bound to each of your hubs. /proc/bus/usb/devices will contain that information. Without it, it's hard to diagnose what happened.
At the moment usbcore is undergoing a lengthy, and not terribly rapid, series of changes to the generic bus glue layer, as are the host controller drivers themselves. Part of this change will involve the way suspend/resume is handled. (Not to the mention the fact that the power management core itself is in the midst of change!)
As the uhci-hcd maintainer, I can safely say that the suspend/resume support in that driver is badly out of date. Fixing it up is one of the ingredients planned for this series of changes.
As things stand now, however, there's likely to be lots of problems in the coordination of suspend/resume activities among the HCDs, the glue layer, and the hub driver. One thing you could try is to turn on CONFIG_USB_SUSPEND. It's likely to change things, although not necessarily for the better. :-)
Alan Stern
Hi!
Quoted 10 lines
Quoted 10 lines
In 2.6.11-rc[23], I get problems after swsusp resume:
Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0: over-current change on port 1 Feb 4 23:54:39 amd kernel: done Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2
Quoted 6 lines
Quoted 2 lines
After unplugging usb bluetooth key, machine hung. Sysrq still responded with help but I could not get any usefull output.
Your logs don't indicate which host controller driver is bound to each of your hubs.
/proc/bus/usb/deviceswill contain that information. Without it, it's hard to diagnose what happened.
I do not think I have any hubs... no external hubs anyway. And I do not have /proc/bus/usb/devices file :-(. There's something in /sys/bus/usb/devices/.
Quoted 5 lines
As things stand now, however, there's likely to be lots of problems in the coordination of suspend/resume activities among the HCDs, the glue layer, and the hub driver. One thing you could try is to turn on
CONFIG_USB_SUSPEND. It's likely to change things, although not necessarily for the better. :-)
:-).
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Quoted 9 lines · Pavel Machek
Hi!
Quoted 3 lines
Your logs don't indicate which host controller driver is bound to each of your hubs.
/proc/bus/usb/deviceswill contain that information. Without it, it's hard to diagnose what happened.I do not think I have any hubs... no external hubs anyway. And I do not have
/proc/bus/usb/devicesfile :-(. There's something in/sys/bus/usb/devices/.
So what does "lspci -v|grep HCI" say then?
You could try "mount -t usbfs on /proc/bus/usb" ... ;)
Periodically I think that it'd be useful to have the hub driver messages report the HCD involved, somehow, instead of just "hub", at least when root hub ports are involved. It could improve the utility of some bug reports by a significant amount.
- Dave
Hi!
Quoted 9 lines
Quoted 7 lines
Quoted 3 lines
Your logs don't indicate which host controller driver is bound to each of your hubs.
/proc/bus/usb/deviceswill contain that information. Without it, it's hard to diagnose what happened.I do not think I have any hubs... no external hubs anyway. And I do not have
/proc/bus/usb/devicesfile :-(. There's something in/sys/bus/usb/devices/.So what does "lspci -v|grep HCI" say then?
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) 0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) 0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) 0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) 0000:00:13.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI])
Quoted 1 line
You could try "mount -t usbfs on
/proc/bus/usb" ... ;)
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.11-rc3 uhci_hcd S: Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3) S: SerialNumber=0000:00:10.2 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 23/900 us ( 3%), #Int= 1, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.11-rc3 uhci_hcd S: Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) S: SerialNumber=0000:00:10.1 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0db0 ProdID=1967 Rev= 5.25 C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=250mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none) E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none) E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none) E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none) E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none) E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none) E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.11-rc3 uhci_hcd S: Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller S: SerialNumber=0000:00:10.0 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.11-rc3 ehci_hcd S: Product=VIA Technologies, Inc. USB 2.0 S: SerialNumber=0000:00:10.3 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Quoted 15 lines · Pavel Machek
Hi!
In 2.6.11-rc[23], I get problems after swsusp resume:
Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0: over-current change on port 1 Feb 4 23:54:39 amd kernel: done Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2After unplugging usb bluetooth key, machine hung. Sysrq still responded with help but I could not get any usefull output.
Quoted 7 lines
I tried deselecting
CONFIG_USB_EHCI_HCD, and got repeating stream ofFeb 5 00:21:17 amd kernel: Restarting tasks... done Feb 5 00:21:17 amd kernel: hub 3-0:1.0: over-current change on port 1 Feb 5 00:21:18 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:18 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 5 00:21:20 amd kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Considering all the known problems in uhci-hcd's suspend support, I'm not sure it's worth pursuing this. On the other hand, all those "over-current change" messages you kept getting might indicate a more serious kind of failure.
Does setting CONFIG_USB_SUSPEND help at all?
Alan Stern
Hi!
Quoted 21 lines
Quoted 13 lines
In 2.6.11-rc[23], I get problems after swsusp resume:
Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0: over-current change on port 1 Feb 4 23:54:39 amd kernel: done Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2After unplugging usb bluetooth key, machine hung. Sysrq still responded with help but I could not get any usefull output.
Quoted 7 lines
I tried deselecting
CONFIG_USB_EHCI_HCD, and got repeating stream ofFeb 5 00:21:17 amd kernel: Restarting tasks... done Feb 5 00:21:17 amd kernel: hub 3-0:1.0: over-current change on port 1 Feb 5 00:21:18 amd kernel: hub 3-0:1.0: connect-debounce failed, port 1 disabled Feb 5 00:21:18 amd kernel: hub 3-0:1.0: over-current change on port 2 Feb 5 00:21:20 amd kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Quoted 4 lines
Considering all the known problems in uhci-hcd's suspend support, I'm not sure it's worth pursuing this. On the other hand, all those "over-current change" messages you kept getting might indicate a more serious kind of failure.
Oops, I tried again with latest -bk kernel and no patches, and it works okay; that means that failure was probably caused by my local patches.
Sorry about the noise.
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!