On Tue, 27 Jul 2004, Jean-Yves LENHOF wrote: > Good catch... I uncommented the good lines under my debian in > syslog.conf and I think I can give some more informations...
If you're relying on syslogd to send the log messages to the screen where you can copy them down, then you're probably missing the last few (and most important!) messages. That's because when the computer crashes syslogd will stop working and won't get the last log messages. Don't rely on syslogd! Use the Alt-SysRq-9 setting instead. > First all tests I've just done are under kernel 2.6.8-rc2 on USB 2.0 > port and with doing a "rmmod ehci_hcd".... and the thing that you have > to notice is that sometime, not very often, things work just okay... > > OK now let's see three different trace I have had when my computer just > hang (I repeat I never had this problem with kernel 2.4) > > OK now first with udev activated (Hand written what I have on my screen > before hang) : > --- > > R0 Stat 0x0 > Attached scsi removable disk sda at scsi1, channel 0, id0, lun 0 > usb-storage : scsci cmd done, result=0x0 > usb-storage : queuecommand called > Attached scsi removable disk sda at scsi1, channel 0, id0, lun 0 > usb-storage: *** thread sleeping > usb-storage: *** thread awakened > usb-storage: Bad target number (6:0) > usb-storage: scsi cmd done, result =0x 40000 > usb-storage: queuecommand called > usb-storage: *** thread sleeping > usb-storage: *** thread awakened > usb-storage: Bad target number (7:0) > usbcore: registered new driver > USB Mass Storage support registered > usb.agent [4855] : usb-storage: loaded successfully > usb-storage: scsi cmd done result=0x 40000 > USB Mass Storage device found at 2 > usbcore: registered new driver usb-storage > USB Mass Storage support registered > usb-storage: *** thread sleeping > udev[4968]: creating device node '/dev/sda' > udev[4968]: creating device node '/dev/sda1' > > OK now second one with udev deactivated (Hand written what I have on my > screen before hang) : > --- > > usb-storage:*** thread awakened > usb-storage:Command ALLOW_MEDIUM_REMOVAL (6 bytes) > usb-storage: 1e 00 00 00 00 00 > usb-storage: Bulk Command S 0x43425355 T 0x11e L 0 F0 Trg 0 LUN 0 CL 6 > usb-storage: usb_stor_bulk_transfer_buf : xfer 31 bytes > usb-storage: Status code 0, transferred 31/31 > usb-storage: --transfer complete > usb-storage: Bulk command transfer result=0 > usb-storage: Attempting to get CSW... > usb-storage: usb_stor_bulk_transer_buf: xfer 13 bytes > usb-storage: Status code 0; transferred 13/13 > usb-storage: --transfer complete > usb-storage: Bulk status result=0 > usb-storage: Bulk Status S 0x53425355 T 0x11e R 0 Stat 0x0 > Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 > usb-storage: scsi cmd done, result=0x0 > Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 > usb-storage: *** thread sleeping In both cases the hang seems to occur while the device is idle, not doing anything. > If I have some extra time I will try with different kernel if it make a > difference.... And I will try without removing ehci_hcd > > I think that there are more than one problem perhaps...thread ? sleep > too short ? Could be... I can't tell what's going on. It's quite possible that the problem doesn't lie in the USB subsystem at all but somewhere else entirely. Or maybe there's a bizarre hardware problem that doesn't show up in the debugging logs. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
