On Sat, Dec 20, 2003 at 12:06:17PM +0100, [EMAIL PROTECTED] wrote: > > You forgot to pass it through ksymoops. > > > > But I can tell that the device won't work if the oops is fixed. > > The root cause is a firmware lockup.
> Sorry about that. I passed it through now, but I guess its just more of the > same. > >>EIP; c02522ac <usb_submit_urb+1c/40> <===== > Trace; c02523a0 <usb_start_wait_urb+70/180> > Trace; c0252513 <usb_internal_control_msg+63/70> > Trace; c02525c1 <usb_control_msg+a1/d0> > Trace; c0253521 <usb_set_address+61/70> > Trace; c0256715 <usb_reset_device+a5/3b0> > Trace; c022ed9d <scsi_try_bus_reset+3d/a0> > Trace; c022f782 <scsi_unjam_host+5e2/830> > Trace; c022faa6 <scsi_error_handler+d6/120> > Trace; c01073bb <arch_kernel_thread+2b/40> > Trace; c022f9d0 <scsi_error_handler+0/120> Looks familiar. This might help: http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107091524218255&w=2 > Since this has been happening to me on two different mainboards, while the > stick seems to work on WinDO$ on the same hardware, do you think I have a > strange and out of spec kernel configuration? Is there anything I can do in > to just make the thing work? It's not so much configuration, but something that Linux does is not expected by the firmware. You might want to experiment a little. Usually it's the last command that does the deed, devices are not too smart. So, just change #undef DEBUG into #define DEBUG in the usb-storage, try to guess what it didn't like. -- Pete ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
