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. I'm not familiar enough with them to see what the error is, though. The system runs fine until the packet is returned, then it just locks solid (On the alcatel USB modem I used for testing it will not respond until it gets sync, which may be several seconds). Others have found that just compiling SMP into the kernel is enough to break it, you don't actually need two processors. Tony -- Don't click on this sig - a cyberwoozle will eat your underwear. [EMAIL PROTECTED] http://www.nothing-on.tv - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
