Hi, David Brownell: > > I am not sure how to recover from that. Apparently the chip has wedged > > itself into a corner..? > > Or someone's wedged it. What drivers did you say were active at > the time? > The new Option driver (mine, incidentally), though it also happens with the standard Serial driver if you feed it with the appropriate parameters.
> But there are some OHCI implementations (OPTi comes to mind, and SiS)
OPTi. :-/
> like this. If you can temporarily switch over to a different OHCI
> controller (add-in PCI cards are handy!) that supports UE, you might
> find it a bit more congenial for chasing this kind of bug.
>
It's a PC-card, so no, I can't switch it. I'm investigating the Apple
OPTi fixes, though it's not entirely clear what exactly they are doing
and *why*.
> One way to shake such problems loose earlier is to turn on the slab
> poisoning options (CONFIG_DEBUG_SLAB). Doesn't always do it, but
I tried that. It turned out to be a very good way to make the problem
disappear. :-/ (Different timing?)
> > My brute-force idea would be to sample that frame
> > number every couple of jiffies and, if it hasn't changed, call
> > ohci_restart() and hope for the best. :-/
>
> I'd avoid such things; if usbcore isn't involved in shutting
> down and restarting the HCDs, it's going to get deeply confused
> and start throwing tantrums.
>
Good point...
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
I'm Luke Skywalker, I'm here to rescue you.
-- Luke Skywalker
signature.asc
Description: Digital signature
