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.
>
> 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.
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/.
> 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
--
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
