lkml.org 
[lkml]   [2005]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [linux-usb-devel] 2.6.11-rc[23]: swsusp & usb regression
On Sat, 5 Feb 2005, Pavel Machek wrote:

> 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

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

-
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/

\
 
 \ /
  Last update: 2005-03-22 14:10    [W:0.041 / U:23.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site