USB problem with a mass storage device on 2.6.10

USB problem with a mass storage device on 2.6.10

[Roseline Bonchamp]

Hello,

I have a PQI 1GB Intelligent Stick, which does'nt work most of the
time on 2.6.10 (sometime when I plug/unplug it does work, but most of
the time it does'nt)

When it does not work, I see this when I plug it:

kernel: usb 1-3: new high speed USB device using ehci_hcd and address 6
kernel: usb 3-1: new full speed USB device using uhci_hcd and address 4
kernel: usb 3-1: new full speed USB device using uhci_hcd and address 5

When it does work, I only see the first one (high speed), and then USB
mass storage stuff.

On kernel 2.6.9 it does work, but seems to produce a kernel crash (log
attached) (but I still can use it and mount it)

I tried on a knoppix 3.6 (2.6.7, not vanilla) kernel, and it seems to work too.

Even with 2.6.10 I have no problem with some other USB mass storage devices.

I already did a post about this, but the subject of the mail was wrong
(sorry), and it was not mailed to linux-usb:
http://www.ussg.iu.edu/hypermail/linux/kernel/0501.1/0371.html

Regards,

Re: USB problem with a mass storage device on 2.6.10

[Roseline Bonchamp]

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

I forgot the attachments.

I tried this on 5 different PCs, here is lspci from one of them.
The other log is from kernel 2.6.9 wich seems to "crash", but allow me
to use my mass storage device perfectly (2.6.10 does'nt)

Roseline

[-- Attachment #2: kernel_crash.2.6.9.log --]
[-- Type: application/octet-stream, Size: 8553 bytes --]

Jan 10 13:32:20 localhost kernel: usb 1-2: USB disconnect, address 4


Jan 10 13:32:24 localhost kernel: usb 1-2: new high speed USB device using address 5
Jan 10 13:32:25 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Jan 10 13:32:25 localhost kernel:   Vendor: I-Stick2  Model: IntelligentStick  Rev: 2.00
Jan 10 13:32:25 localhost kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Jan 10 13:32:25 localhost kernel: sda: Unit Not Ready, sense:
Jan 10 13:32:25 localhost kernel: Current : sense key Unit Attention
Jan 10 13:32:25 localhost kernel: Additional sense: Not ready to ready change, medium may have changed
Jan 10 13:32:25 localhost kernel: sda : READ CAPACITY failed.
Jan 10 13:32:25 localhost kernel: sda : status=1, message=00, host=0, driver=08
Jan 10 13:32:25 localhost kernel: Current sd: sense key Unit Attention
Jan 10 13:32:25 localhost kernel: Additional sense: Not ready to ready change, medium may have changed
Jan 10 13:32:25 localhost kernel: sda: assuming Write Enabled
Jan 10 13:32:25 localhost kernel: sda: Unit Not Ready, sense:
Jan 10 13:32:25 localhost kernel: Current : sense key Unit Attention
Jan 10 13:32:25 localhost kernel: Additional sense: Not ready to ready change, medium may have changed
Jan 10 13:32:25 localhost kernel: sda : READ CAPACITY failed.
Jan 10 13:32:25 localhost kernel: sda : status=1, message=00, host=0, driver=08
Jan 10 13:32:25 localhost kernel: Current sd: sense key Unit Attention
Jan 10 13:32:25 localhost kernel: Additional sense: Not ready to ready change, medium may have changed
Jan 10 13:32:25 localhost kernel: sda: assuming Write Enabled
Jan 10 13:32:26 localhost kernel: sda: Unit Not Ready, sense:
Jan 10 13:32:26 localhost kernel: Current : sense key Unit Attention
Jan 10 13:32:26 localhost kernel: Additional sense: Not ready to ready change, medium may have changed
Jan 10 13:32:26 localhost kernel: SCSI device sda: 2047488 512-byte hdwr sectors (1048 MB)
Jan 10 13:32:26 localhost kernel: sda: assuming Write Enabled
Jan 10 13:32:26 localhost kernel:  /dev/scsi/host1/bus0/target0/lun0: p1 p2
Jan 10 13:32:26 localhost kernel:  /dev/scsi/host1/bus0/target0/lun0: p1 p2
Jan 10 13:32:26 localhost kernel: devfs_mk_dev: could not append to parent for scsi/host1/bus0/target0/lun0/part1
Jan 10 13:32:26 localhost kernel: kobject_register failed for sda1 (-17)
Jan 10 13:32:26 localhost kernel:  [<c01bbbab>] kobject_register+0x5b/0x60
Jan 10 13:32:26 localhost kernel:  [<c017fcbb>] add_partition+0xeb/0x120
Jan 10 13:32:26 localhost kernel:  [<c017fe9a>] register_disk+0x14a/0x180
Jan 10 13:32:26 localhost kernel:  [<c021c45c>] add_disk+0x4c/0x60
Jan 10 13:32:26 localhost kernel:  [<c021c3e0>] exact_match+0x0/0x10
Jan 10 13:32:26 localhost kernel:  [<c021c3f0>] exact_lock+0x0/0x20
Jan 10 13:32:26 localhost kernel:  [<e083bbab>] sd_probe+0x23b/0x390 [sd_mod]
Jan 10 13:32:26 localhost kernel:  [<c0186848>] sysfs_add_file+0x78/0xa0
Jan 10 13:32:26 localhost kernel:  [<c0213a6f>] bus_match+0x3f/0x70
Jan 10 13:32:26 localhost kernel:  [<c0213aef>] device_attach+0x4f/0xa0
Jan 10 13:32:26 localhost kernel:  [<c01bbd6a>] kobject_get+0x1a/0x30
Jan 10 13:32:26 localhost kernel:  [<c0213e0b>] bus_add_device+0x5b/0xb0
Jan 10 13:32:26 localhost kernel:  [<c0212b31>] device_add+0xa1/0x130
Jan 10 13:32:26 localhost kernel:  [<c025af22>] scsi_sysfs_add_sdev+0x52/0x200
Jan 10 13:32:26 localhost kernel:  [<c0279e5b>] slave_configure+0x2b/0x90
Jan 10 13:32:26 localhost kernel:  [<c0279e30>] slave_configure+0x0/0x90
Jan 10 13:32:26 localhost kernel:  [<c02597d9>] scsi_add_lun+0x2d9/0x380
Jan 10 13:32:26 localhost kernel:  [<c0259959>] scsi_probe_and_add_lun+0xd9/0x240
Jan 10 13:32:26 localhost kernel:  [<c025a1f8>] scsi_scan_target+0xa8/0x130
Jan 10 13:32:26 localhost kernel:  [<c025a309>] scsi_scan_channel+0x89/0xa0
Jan 10 13:32:26 localhost kernel:  [<c025a3f1>] scsi_scan_host_selected+0xd1/0x110
Jan 10 13:32:26 localhost kernel:  [<c025a460>] scsi_scan_host+0x30/0x40
Jan 10 13:32:26 localhost kernel:  [<c027cb46>] storage_probe+0x146/0x1e0
Jan 10 13:32:26 localhost kernel:  [<c01862b0>] init_file+0x0/0x20
Jan 10 13:32:26 localhost kernel:  [<c0261aab>] usb_probe_interface+0x6b/0x80
Jan 10 13:32:26 localhost kernel:  [<c0213a6f>] bus_match+0x3f/0x70
Jan 10 13:32:26 localhost kernel:  [<c0213aef>] device_attach+0x4f/0xa0
Jan 10 13:32:26 localhost kernel:  [<c01bbd6a>] kobject_get+0x1a/0x30
Jan 10 13:32:26 localhost kernel:  [<c0213e0b>] bus_add_device+0x5b/0xb0
Jan 10 13:32:26 localhost kernel:  [<c0212b31>] device_add+0xa1/0x130
Jan 10 13:32:26 localhost kernel:  [<c0268d03>] usb_set_configuration+0x303/0x470
Jan 10 13:32:26 localhost kernel:  [<c0263f32>] usb_new_device+0xb2/0x170
Jan 10 13:32:26 localhost kernel:  [<c0264c58>] hub_port_connect_change+0x1e8/0x3b0
Jan 10 13:32:26 localhost kernel:  [<c0265074>] hub_events+0x254/0x380
Jan 10 13:32:26 localhost kernel:  [<c02651d5>] hub_thread+0x35/0x120
Jan 10 13:32:26 localhost kernel:  [<c0116e70>] autoremove_wake_function+0x0/0x60
Jan 10 13:32:26 localhost kernel:  [<c0116e70>] autoremove_wake_function+0x0/0x60
Jan 10 13:32:26 localhost kernel:  [<c02651a0>] hub_thread+0x0/0x120
Jan 10 13:32:26 localhost kernel:  [<c01042ad>] kernel_thread_helper+0x5/0x18
Jan 10 13:32:26 localhost kernel: devfs_mk_dev: could not append to parent for scsi/host1/bus0/target0/lun0/part2
Jan 10 13:32:26 localhost kernel: kobject_register failed for sda2 (-17)
Jan 10 13:32:26 localhost kernel:  [<c01bbbab>] kobject_register+0x5b/0x60
Jan 10 13:32:26 localhost kernel:  [<c017fcbb>] add_partition+0xeb/0x120
Jan 10 13:32:26 localhost kernel:  [<c017fe9a>] register_disk+0x14a/0x180
Jan 10 13:32:26 localhost kernel:  [<c021c45c>] add_disk+0x4c/0x60
Jan 10 13:32:26 localhost kernel:  [<c021c3e0>] exact_match+0x0/0x10
Jan 10 13:32:26 localhost kernel:  [<c021c3f0>] exact_lock+0x0/0x20
Jan 10 13:32:26 localhost kernel:  [<e083bbab>] sd_probe+0x23b/0x390 [sd_mod]
Jan 10 13:32:26 localhost kernel:  [<c0186848>] sysfs_add_file+0x78/0xa0
Jan 10 13:32:26 localhost kernel:  [<c0213a6f>] bus_match+0x3f/0x70
Jan 10 13:32:26 localhost kernel:  [<c0213aef>] device_attach+0x4f/0xa0
Jan 10 13:32:26 localhost kernel:  [<c01bbd6a>] kobject_get+0x1a/0x30
Jan 10 13:32:26 localhost kernel:  [<c0213e0b>] bus_add_device+0x5b/0xb0
Jan 10 13:32:26 localhost kernel:  [<c0212b31>] device_add+0xa1/0x130
Jan 10 13:32:26 localhost kernel:  [<c025af22>] scsi_sysfs_add_sdev+0x52/0x200
Jan 10 13:32:26 localhost kernel:  [<c0279e5b>] slave_configure+0x2b/0x90
Jan 10 13:32:26 localhost kernel:  [<c0279e30>] slave_configure+0x0/0x90
Jan 10 13:32:26 localhost kernel:  [<c02597d9>] scsi_add_lun+0x2d9/0x380
Jan 10 13:32:26 localhost kernel:  [<c0259959>] scsi_probe_and_add_lun+0xd9/0x240
Jan 10 13:32:26 localhost kernel:  [<c025a1f8>] scsi_scan_target+0xa8/0x130
Jan 10 13:32:26 localhost kernel:  [<c025a309>] scsi_scan_channel+0x89/0xa0
Jan 10 13:32:26 localhost kernel:  [<c025a3f1>] scsi_scan_host_selected+0xd1/0x110
Jan 10 13:32:26 localhost kernel:  [<c025a460>] scsi_scan_host+0x30/0x40
Jan 10 13:32:26 localhost kernel:  [<c027cb46>] storage_probe+0x146/0x1e0
Jan 10 13:32:26 localhost kernel:  [<c01862b0>] init_file+0x0/0x20
Jan 10 13:32:26 localhost kernel:  [<c0261aab>] usb_probe_interface+0x6b/0x80
Jan 10 13:32:26 localhost kernel:  [<c0213a6f>] bus_match+0x3f/0x70
Jan 10 13:32:26 localhost kernel:  [<c0213aef>] device_attach+0x4f/0xa0
Jan 10 13:32:26 localhost kernel:  [<c01bbd6a>] kobject_get+0x1a/0x30
Jan 10 13:32:26 localhost kernel:  [<c0213e0b>] bus_add_device+0x5b/0xb0
Jan 10 13:32:26 localhost kernel:  [<c0212b31>] device_add+0xa1/0x130
Jan 10 13:32:26 localhost kernel:  [<c0268d03>] usb_set_configuration+0x303/0x470
Jan 10 13:32:26 localhost kernel:  [<c0263f32>] usb_new_device+0xb2/0x170
Jan 10 13:32:26 localhost kernel:  [<c0264c58>] hub_port_connect_change+0x1e8/0x3b0
Jan 10 13:32:26 localhost kernel:  [<c0265074>] hub_events+0x254/0x380
Jan 10 13:32:26 localhost kernel:  [<c02651d5>] hub_thread+0x35/0x120
Jan 10 13:32:26 localhost kernel:  [<c0116e70>] autoremove_wake_function+0x0/0x60
Jan 10 13:32:26 localhost kernel:  [<c0116e70>] autoremove_wake_function+0x0/0x60
Jan 10 13:32:26 localhost kernel:  [<c02651a0>] hub_thread+0x0/0x120
Jan 10 13:32:26 localhost kernel:  [<c01042ad>] kernel_thread_helper+0x5/0x18
Jan 10 13:32:26 localhost kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
Jan 10 13:32:26 localhost scsi.agent[3109]: disk at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host1/1:0:0:0


[-- Attachment #3: lspci.log --]
[-- Type: application/octet-stream, Size: 1791 bytes --]

0000:00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03)
0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
0000:02:04.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
0000:02:06.0 CardBus bridge: O2 Micro, Inc. OZ711M3 SmartCardBus MultiMediaBay Controller
0000:02:06.1 CardBus bridge: O2 Micro, Inc. OZ711M3 SmartCardBus MultiMediaBay Controller
0000:02:06.2 System peripheral: O2 Micro, Inc. OZ711Mx MultiMediaBay Accelerator
0000:02:06.3 CardBus bridge: O2 Micro, Inc. OZ711M3 SmartCardBus MultiMediaBay Controller
0000:02:0e.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M_2 Gigabit Ethernet (rev 03)

Re: [Linux-usb-users] USB problem with a mass storage device on 2.6.10

[Stephen J. Gowdy]

What is in /proc/bus/usb/devices when it doesn't work (and when it works)?
What command fails?

On Mon, 10 Jan 2005, Roseline Bonchamp wrote:

> Hello,
>
> I have a PQI 1GB Intelligent Stick, which does'nt work most of the
> time on 2.6.10 (sometime when I plug/unplug it does work, but most of
> the time it does'nt)
>
> When it does not work, I see this when I plug it:
>
> kernel: usb 1-3: new high speed USB device using ehci_hcd and address 6
> kernel: usb 3-1: new full speed USB device using uhci_hcd and address 4
> kernel: usb 3-1: new full speed USB device using uhci_hcd and address 5
>
> When it does work, I only see the first one (high speed), and then USB
> mass storage stuff.
>
> On kernel 2.6.9 it does work, but seems to produce a kernel crash (log
> attached) (but I still can use it and mount it)
>
> I tried on a knoppix 3.6 (2.6.7, not vanilla) kernel, and it seems to work too.
>
> Even with 2.6.10 I have no problem with some other USB mass storage devices.
>
> I already did a post about this, but the subject of the mail was wrong
> (sorry), and it was not mailed to linux-usb:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0501.1/0371.html
>
> Regards,
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Linux-usb-users@lists.sourceforge.net
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-users
>

--
 /------------------------------------+-------------------------\
|Stephen J. Gowdy                     | SLAC, MailStop 34,       |
|http://www.slac.stanford.edu/~gowdy/ | 2575 Sand Hill Road,     |
|http://calendar.yahoo.com/gowdy      | Menlo Park CA 94025, USA |
|EMail: gowdy@slac.stanford.edu       | Tel: +1 650 926 3144     |
 \------------------------------------+-------------------------/

Re: [Linux-usb-users] USB problem with a mass storage device on 2.6.10

[Roseline Bonchamp]

> What is in /proc/bus/usb/devices when it doesn't work (and when it works)?
> What command fails?

When it does'nt work, I see my 2 UHCI controllers and my EHCI
controller (driver=Hub)

When it does work, I see the same, plus:

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 15 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0ea0 ProdID=2168 Rev= 2.00
S:  Manufacturer=USB
S:  Product=Flash Disk
S:  SerialNumber=106C1141B1C3762C
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   2 Ivl=125us

What fails is that I don't see anything related to USB mass storage in
logs, and so cannot access the device through de SCSI interface
(/dev/sda...)

Also I've just fount out that it seems that "echo y >
/sys/module/usbcore/parameters/old_scheme_first" makes it work!