Copied to linux-scsi, so a bit context for folks there... On a 64bit 2.6.29-rc2 system (and a few earlier kernels that I have tried) I can no longer use USB sticks. When I connect one it gets correctly identified, but then when I try to access it I get "Medium not present" error. Turning on debugging in the USB storage subsystem indicates that we are sending START_STOP to the device which really confuses it... 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. Doing some googling around that seems to imply that this is not unusual for USB devices... > 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. That's one valid question... maybe someone on the linux-scsi list can sched some light onto this? Are there SCSI specific debugging options I should turn on? The other one is "why isn't the USB stack filtering that command when it comes down from SCSI?" Way back when in 2002 Matt Dharm suggested doing just that and Greg applied it: http://osdir.com/ml/usb.devel/2002-08/msg00357.html http://osdir.com/ml/usb.devel/2002-08/msg00447.html A few months later this code was removed again as we allegedly don't need it anymore: http://www.mail-archive.com/linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx/msg09331.html Maybe we need to bring such code back? /D -- Dirk Hohndel Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
