On Tue, 27 Jan 2009 15:56:11 -0500 (EST) Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Tue, 27 Jan 2009, Dirk Hohndel wrote: > > > Here you go: > > >From the middle of the log (after the partition table has been read): > > > [ 32.056855] usb-storage: queuecommand called > > [ 32.056886] usb-storage: *** thread awakened. > > [ 32.056888] usb-storage: Command START_STOP (6 bytes) > > [ 32.056889] usb-storage: 1b 00 00 00 02 00 > > [ 32.056894] usb-storage: Bulk Command S 0x43425355 T 0x24 L 0 F 0 Trg 0 LUN 0 CL 6 > > [ 32.056896] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > > [ 32.057328] usb-storage: Status code 0; transferred 31/31 > > [ 32.057329] usb-storage: -- transfer complete > > [ 32.057330] usb-storage: Bulk command transfer result=0 > > [ 32.057332] usb-storage: Attempting to get CSW... > > [ 32.057333] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes > > [ 32.057430] usb-storage: Status code 0; transferred 13/13 > > [ 32.057432] usb-storage: -- transfer complete > > [ 32.057433] usb-storage: Bulk status result = 0 > > [ 32.057435] usb-storage: Bulk Status S 0x53425355 T 0x24 R 0 Stat 0x0 > > [ 32.057437] usb-storage: scsi cmd done, result=0x0 > > [ 32.057440] usb-storage: *** thread sleeping. > > This command is basically an Eject. Even though the device doesn't > have removable media, it apparently gets very confused when it receives > this command. > > > [ 32.058987] usb-storage: queuecommand called > > [ 32.059053] usb-storage: *** thread awakened. > > [ 32.059055] usb-storage: Command TEST_UNIT_READY (6 bytes) > > [ 32.059057] usb-storage: 00 00 00 00 00 00 > > [ 32.059062] usb-storage: Bulk Command S 0x43425355 T 0x25 L 0 F 0 Trg 0 LUN 0 CL 6 > > [ 32.059064] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > > [ 32.059191] usb-storage: Status code 0; transferred 31/31 > > [ 32.059193] usb-storage: -- transfer complete > > [ 32.059194] usb-storage: Bulk command transfer result=0 > > [ 32.059195] usb-storage: Attempting to get CSW... > > [ 32.059197] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes > > [ 32.059403] usb-storage: Status code 0; transferred 13/13 > > [ 32.059404] usb-storage: -- transfer complete > > [ 32.059406] usb-storage: Bulk status result = 0 > > [ 32.059407] usb-storage: Bulk Status S 0x53425355 T 0x25 R 0 Stat 0x1 > > [ 32.059409] usb-storage: -- transport indicates command failure > > [ 32.059410] usb-storage: Issuing auto-REQUEST_SENSE > > [ 32.059413] usb-storage: Bulk Command S 0x43425355 T 0x26 L 18 F 128 Trg 0 LUN 0 CL 6 > > [ 32.059415] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > > [ 32.059556] usb-storage: Status code 0; transferred 31/31 > > [ 32.059557] usb-storage: -- transfer complete > > [ 32.059559] usb-storage: Bulk command transfer result=0 > > [ 32.059561] usb-storage: usb_stor_bulk_transfer_sglist: xfer 18 bytes, 1 entries > > [ 32.059686] usb-storage: Status code 0; transferred 18/18 > > [ 32.059688] usb-storage: -- transfer complete > > [ 32.059690] usb-storage: Bulk data transfer result 0x0 > > [ 32.059691] usb-storage: Attempting to get CSW... > > [ 32.059693] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes > > [ 32.059799] usb-storage: Status code 0; transferred 13/13 > > [ 32.059800] usb-storage: -- transfer complete > > [ 32.059802] usb-storage: Bulk status result = 0 > > [ 32.059804] usb-storage: Bulk Status S 0x53425355 T 0x26 R 0 Stat 0x0 > > [ 32.059806] usb-storage: -- Result from auto-sense is 0 > > [ 32.059807] usb-storage: -- code: 0x70, key: 0x2, ASC: 0x3a, ASCQ: 0x0 > > [ 32.059811] usb-storage: Not Ready: Medium not present > > [ 32.059813] usb-storage: scsi cmd done, result=0x2 > > [ 32.059816] usb-storage: *** thread sleeping. > > As you can see, thereafter the device responds to all commands with a > "Medium not present" error. > > So the real question is: Who is responsible for sending that Eject > command? It certainly isn't usb-storage or any other part of the USB > stack. Maybe something in the SCSI disk driver or maybe a user > program. This was done with as little running as possible. This is a typical 64bit Fedora 10 setup. I booted into runlevel 3 and inserted the USB stick. So none of the Gnome-gimmicks should be up and running at that point. How can I figure out who is responsible for sending that Eject command? Is there an easy way of doing that? /D -- Dirk Hohndel Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
