On Friday 19 November 2004 07:21, john cooper wrote:
> > Fixed in 2.6.10-rc2?
>
> Hmm, not in my case. Connects/disconnects don't appear
> to be recognized after boot. Again if a device is there
> at boot time all seems well.
One possibility is that your hardware isn't issuing
the interrupts i
David Brownell wrote:
On Friday 19 November 2004 03:41, john cooper wrote:
I combed through the mail archives but didn't see
anything relevant. Has anyone experienced similar
problems?
Fixed in 2.6.10-rc2?
Hmm, not in my case. Connects/disconnects don't appear
to be recognized after boot. Agai
On Friday 19 November 2004 03:41, john cooper wrote:
> I combed through the mail archives but didn't see
> anything relevant. Has anyone experienced similar
> problems?
Fixed in 2.6.10-rc2?
---
This SF.Net email is sponsored by: InterSystems
I've been seeing a weird problem with the later 2.6
series kernels where a usb device is recognized
correctly if present at kernel boot time. However
connection (or removal) of a device doesn't seem to
generate connect/disconnect interrupts to ohci_hcd
according to /proc/interrupts.
Behavior varie
