Messages in this thread | | | Date | Sat, 5 Feb 2005 00:23:02 +0100 | From | Pavel Machek <> | Subject | Re: 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.
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.
-- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |