> The bug was present in the 2.4-test2
> backport I used for our new PowerMac 2.2 kernels.
Hmm, could you share a brief update on PowerMac and 2.4?
If I go by Paulus' page at
http://linuxcare.com.au/paulus/kernels.html
what I see is "2.3.99-pre6-pre3" (??) labeled as current.
That dates from back in April -- not actually very current.
But 'penguinppc.org' lists a BitKeeper CVS that's relatively
current (mentions a 2.4.0-test5 pre-release).
As you know, I'm curious when I can rip out the PMAC_PBOOK
stuff in the OHCI driver and just use the normal 2.4 PCI
interfaces for that functionality (no platform-specific stuff).
> In the meantime, I implemented a hack that makes sohci_unlink_urb() safe
> to call from interrupts,
It should be safe already for async unlinking; synchronous
unlinks are trouble, since they'd require the interrupt
code to sleep (Oops!) or something almost as rude.
> at the expense of several milliseconds spend in
> the interrupt handler (which is bad, but at least won't crash). It's
> purely a workaround for bad drivers, so I'm considering adding a ton of
> printk's next to it in order to catch them.
I'd actually rather just see sohci_unlink_urb() report EWOULDBLOCK,
with a single err() to report that USB device driver bug. Then at
least the failure report is in the hands of the driver that caused it,
and it can maybe resolve it. (I've yet to send around such a patch,
but it's in the queue while I track down a different bug.)
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
