On Thu, 29 Mar 2001, johan verrept wrote:
> Tony Hoyle wrote:
> >
> > If an application calls the USBDEVFS_SUBMITURB ioctl to submit a read,
> > when the async completion routine is called, the kernel goes into a hard
> > deadlock (no response to ping, etc.). I've narrowed it down to the
> >
Tony Hoyle wrote:
>
> If an application calls the USBDEVFS_SUBMITURB ioctl to submit a read,
> when the async completion routine is called, the kernel goes into a hard
> deadlock (no response to ping, etc.). I've narrowed it down to the
> async_completed routine in usb.c. That's the only place
I've enabled spinlock debugging, and generated a nice oops... The USB
system is definately doing something wrong somewhere.
Tony
--
Don't click on this sig - a cyberwoozle will eat your underwear.
[EMAIL PROTECTED]http://www.nothing-on.tv
ksymoops 2.3.7 on i686 2.4.2-ac26. Options
If an application calls the USBDEVFS_SUBMITURB ioctl to submit a read,
when the async completion routine is called, the kernel goes into a hard
deadlock (no response to ping, etc.). I've narrowed it down to the
async_completed routine in usb.c. That's the only place where spinlocks
are used.
4 matches
Mail list logo
