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. > but when I try to access the device, I get a strange error message that > I can't quite make sense of: > > [hohndel@dhohndel-mobl4 linux]$ sudo fdisk /dev/sdb > Unable to open /dev/sdb > [hohndel@dhohndel-mobl4 linux]$ sudo less -f /dev/sdb > /dev/sdb: No medium found > > (no medium found??? the kernel earlier said it found sdb1 so it must > have read the sdb partition table...) > > > lsusb sees the device: > > [hohndel@dhohndel-mobl4 linux]$ lsusb > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 006 Device 017: ID 05ac:0304 Apple, Inc. Optical USB Mouse [Mitsumi] > Bus 006 Device 016: ID 044f:b203 ThrustMaster, Inc. 360 Modena Pro Wheel > Bus 006 Device 015: ID 046d:c207 Logitech, Inc. WingMan Extreme Digital 3D > Bus 006 Device 008: ID 05ac:0220 Apple, Inc. Aluminum Keyboard > Bus 006 Device 007: ID 0557:7000 ATEN International Co., Ltd Hub > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 001 Device 006: ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 004 Device 003: ID 0a5c:2145 Broadcom Corp. > Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > here's the lspci in case that matters > > [hohndel@dhohndel-mobl4 linux]$ lspci > 00:00.0 Host bridge: Intel Corporation Cantiga Memory Controller Hub (rev 07) > 00:02.0 VGA compatible controller: Intel Corporation Cantiga Integrated Graphics Controller (rev 07) > 00:02.1 Display controller: Intel Corporation Cantiga Integrated Graphics Controller (rev 07) > 00:03.0 Communication controller: Intel Corporation Cantiga MEI Controller (rev 07) > 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) > 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) > 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) > 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) > 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) > 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) > 03:00.0 Network controller: Intel Corporation Device 4236 > > I tried with several USB sticks (that are all working fine in other > systems - except for the Staples one; see my other email). Always the > same situation. The stick is found and recognized by the kernel but then > can't be accessed. > > More system information: I'm running pretty much up-to-date Fedora 10 > x86-64 on this system with my own kernel > > Let me know if I can provide any additional information > > Thanks > > /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 -- 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
