On Fri, 23 Jan 2009 16:29:38 -0800 Matthew Dharm <mdharm-usb@xxxxxxxxxxxxxxxxxx> wrote: > On Fri, Jan 23, 2009 at 04:16:54PM -0800, Dirk Hohndel wrote: > > On Fri, 23 Jan 2009 15:18:58 -0800 > > Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > > > > > On Fri, Jan 23, 2009 at 02:29:03PM -0800, Dirk Hohndel wrote: > > > > > > > > Note this is completely unrelated from my previous email - different > > > > hardware, different issue. > > > > > > > > This is on a Thinkpad X200s. With 2.6.29-rc2 I can no longer access USB > > > > sticks. Other USB storage still works (e.g., a SATA drive connected via > > > > USB/SATA adapter). > > > > > > > > Kernel messages look sane: > > > > > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.182104] usb 1-1: new high speed USB device using ehci_hcd and address 4 > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.297199] usb 1-1: New USB device found, idVendor=0204, idProduct=6025 > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.297376] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.297532] usb 1-1: Product: Flash Disk > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.297666] usb 1-1: Manufacturer: USB > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.297801] usb 1-1: SerialNumber: F08060500572 > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.299038] usb 1-1: configuration #1 chosen from 1 choice > > > > Jan 22 13:49:48 dhohndel-mobl4 kernel: [ 41.315924] scsi4 : SCSI emulation for USB Mass Storage devices > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.317046] scsi 4:0:0:0: Direct-Access USB Flash Disk 5.00 PQ: 0 ANSI: 2 > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.319676] sd 4:0:0:0: [sdb] 4109312 512-byte hardware sectors: (2.10 GB/1.95 GiB) > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.320617] sd 4:0:0:0: [sdb] Write Protect is off > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.320764] sd 4:0:0:0: [sdb] Assuming drive cache: write through > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.323999] sd 4:0:0:0: [sdb] 4109312 512-byte hardware sectors: (2.10 GB/1.95 GiB) > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.325121] sd 4:0:0:0: [sdb] Write Protect is off > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.325279] sd 4:0:0:0: [sdb] Assuming drive cache: write through > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.325909] sdb:<7>usb-storage: queuecommand called > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.326963] sdb1 > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.329437] sd 4:0:0:0: [sdb] Attached SCSI removable disk > > > > Jan 22 13:49:53 dhohndel-mobl4 kernel: [ 46.330022] sd 4:0:0:0: Attached scsi generic sg1 type 0 > > > > > > I looked at Dirk's output yesterday. Dirk, there wasn't any output for sdb > > > after this point, correct? So it looked like to me like the USB MSD driver's > > > queue command function was never returning. > > > > That's correct. Nothing after that. > > Unless you have verbose debugging turned on, I wouldn't expect anything > after that. Yes, I turned all the debugging options on that Sarah suggested. > Given that you're seeing a "medium not found" message, communication with > the device is likely working just fine. However, the device is simply > reporting that there is no medium present. This happens for EVERY SINGLE USB stick that I've tried. Something like seven total. And they all work fine on a different system (the EeePC), also with 2.6.29-RC2. That's why I think there's something really weird happening... > To figure this out, you'll probably have to turn on mass storage verbose > debug (build option) and see what the device is reporting at a low-level. I thought that's what I have... let me check... yeah: CONFIG_USB_DEBUG=y CONFIG_USB_STORAGE_DEBUG=y /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
