> Normally, with this message is "done", an interrupt is generated and the
> ohci->hcca->done_head points to the TD. BUT here is the interesting parts,
> this TD does not match ANY of the TD send.
Likely caused by the td hashchain corruption; I just reposted the
patch for this stuff.
> Questions:
> - what is the use of the khubd thread? Why new device are not handled in
> hc_interrupt() when (ints & OHCI_INTR_RHSC) is true?
khubd sequences device enumeration and, sometimes, driver binding.
That can take a second or so; it'd make a lousy interrupt handler.
> - Is there a PCI stuff I'm missing? I've seen strange message about PCI in
> my logs (see at the end of this mail).
Wouldn'd think so, but that '486 pci setup is a bit funky to need two
different corrections to latency (0 --> 64 --> 4).
> - Why invalid value of ohci->hcca->done_head are handled with the macro
> BUG()? I see no reason why a driver should trust value from its
> "outside" world.
>
> - And why ohci->hcca->done_head is wrong???
Likely it's a bug fixed by the patch mentioned above.
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
