Yes, those stack traces were iffy. "khubd" was missing, and I saw at least one fragmented stack frame. Bigger kernel log buffers might help (somewhere in kconfig) ... or running without an X11 desktop.
Alan Stern wrote:
The bus_reset() procedure (which involves doing a USB port reset) has always been a bit iffy, especially when it occurs during initial probing as it did here.
There are two deadlocks I've seen in usb_reset_device() during probe(). Oddly enough, one for each of the locks it acquires:
- address0_sem ... it's held way too long by khubd, fixed in a reset patch I've not yet re-sent for 2.6.3;
- the usb rwsem ... which is in fact the wrong lock to grab, and is likely the issue Chris is seeing.
"A bit iffy" suggests you may be prone to understatement. ;)
- Dvae
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
