Hi, (I don't know if my earlier mail went through, I had a full disk)
David Brownell:
> But there are some OHCI implementations (OPTi comes to mind, and SiS)
> that won't issue UE ... in /sys/class/usb_host/usbN/registers, there
No such file exists on my system (2.6.11, mostly). Has that been added
recently, and/or is it available with debugging only?
I couldn't find that string in my kernel tree.
Anyway, of *course* it's an Opti (no wonder that company died...).
Worse, the chip is on a PC-Card, and it's hardwired to an USB-interfaced
GSM 'modem', so there's no way to rip it out and test with something
else. Believe me, I *want* to. :-/
I'm also looking at Apple's OPTi fixes,
> One way to shake such problems loose earlier is to turn on the slab
> poisoning options (CONFIG_DEBUG_SLAB).
It's also a good way to prevent the problem from occurring in the first
place. In my case anyway...
> 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.
>
So I involve it. Or call the UE interrupt handler myself when that
happens.
The important part, for me, is to get the system back into a state it
can recover from -- as long as that doesn't involve rebooting, my client
will be reasonably happy. "Flaky hardware", if approximately correct,
is good enough a reason.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
The teacher comes when the soul calls -- and thank goodness,
for the ego is never fully ready.
-- Clarissa Pinkola Estes, "Women Who Run With the Wolves"
signature.asc
Description: Digital signature
