Stuart MacDonald wrote:
Below you will find the log of a recent 2.5.43 test of the whiteheat driver;
stock kernel, using the driver that's included.
Some automatic checks have been triggered, and I'm wondering where
the error lies.
I don't think I'm calling usb_clear_halt in a an illegal manner (cases
1, 2 and 3), but am not sure.
Actually you are: calling it with a spinlock held. It allocates
memory with SLAB_KERNEL, which means "no spinlocks". Don't call
it with that lock held.
Though if you know what that "hcd bug" it's trying to work around,
it'd be good to hear what's wrong! In fact, if you could create a
test case, that'd be very useful.
The last two are unusual; the callback doesn't actually unlink anything,
so I'm not sure how the progression from
Sometimes those stack traces seem plain wrong.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
