Skip to contentSkip to conversation

remove Attach another file remove Attach another file remove Attach another file USB mass storage not always detecting my 1GB PQI intelligent stick

DISCUSSION mama Smurf 2 participants 5 messages Jan 9, 2005

lore
Share & tools
lore

mama Smurf

author
#0 lore raw

Hello,

my 1 GB PQI Intelligent Stick is often not beeing used by mass storage driver when I plug it.

Quoted 1 line

From a fresh reboot it works, I see:

Jan  9 16:54:43 parachute kernel: usb 1-3: new high speed USB device
using ehci_hcd and address 2
Jan  9 16:54:43 parachute kernel: scsi0 : SCSI emulation for USB Mass
Storage devices
Jan  9 16:54:48 parachute kernel:   Vendor: I-Stick2  Model:
IntelligentStick  Rev: 2.00
Jan  9 16:54:48 parachute kernel:   Type:   Direct-Access             
        ANSI SCSI revision: 02
Jan  9 16:54:49 parachute kernel: sda: Unit Not Ready, sense:

then a lot of other stuff, and I can use it.

But if I unplug/replug it, it's not longer detected as mass storage device. I can see 3 new USB devices detected 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

But it's no longer beeing detected as mass storage.

I have other USB 2.0 keys which are working perfectly. Moreover this USB key seems to work properly on some other machines/OSes

In the attached file, full log and result of lspci.

Roseline

Jan  9 16:54:43 parachute kernel: usb 1-3: new high speed USB device using ehci_hcd and address 2
Jan  9 16:54:43 parachute kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Jan  9 16:54:48 parachute kernel:   Vendor: I-Stick2  Model: IntelligentStick  Rev: 2.00
Jan  9 16:54:48 parachute kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Jan  9 16:54:49 parachute kernel: sda: Unit Not Ready, sense:
Jan  9 16:54:49 parachute kernel: Current : sense = 70  6
Jan  9 16:54:49 parachute kernel: ASC=28 ASCQ= 0
Jan  9 16:54:49 parachute kernel: Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 
Jan  9 16:54:49 parachute kernel: sda : READ CAPACITY failed.
Jan  9 16:54:49 parachute kernel: sda : status=1, message=00, host=0, driver=08 
Jan  9 16:54:49 parachute kernel: Current sd: sense = 70  6
Jan  9 16:54:49 parachute kernel: ASC=28 ASCQ= 0
Jan  9 16:54:49 parachute kernel: Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 
Jan  9 16:54:49 parachute kernel: sda: assuming Write Enabled
Jan  9 16:54:49 parachute kernel: sda: Unit Not Ready, sense:
Jan  9 16:54:49 parachute kernel: Current : sense = 70  6
Jan  9 16:54:49 parachute kernel: ASC=28 ASCQ= 0
Jan  9 16:54:49 parachute kernel: Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 
Jan  9 16:54:49 parachute kernel: sda : READ CAPACITY failed.
Jan  9 16:54:49 parachute kernel: sda : status=1, message=00, host=0, driver=08 
Jan  9 16:54:49 parachute kernel: Current sd: sense = 70  6
Jan  9 16:54:49 parachute kernel: ASC=28 ASCQ= 0
Jan  9 16:54:49 parachute kernel: Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 
Jan  9 16:54:49 parachute kernel: sda: assuming Write Enabled
Jan  9 16:54:49 parachute kernel: SCSI device sda: 2047488 512-byte hdwr sectors (1048 MB)
Jan  9 16:54:49 parachute kernel: sda: assuming Write Enabled
Jan  9 16:54:49 parachute kernel:  /dev/scsi/host0/bus0/target0/lun0:<7>usb-storage: queuecommand called
Jan  9 16:54:49 parachute kernel:  p1 p2
Jan  9 16:54:49 parachute kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Jan  9 16:54:49 parachute kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
Jan  9 16:55:19 parachute kernel: usb 1-3: USB disconnect, address 2

< I unplug/replug >

Jan  9 17:07:17 parachute kernel: usb 1-3: new high speed USB device using ehci_hcd and address 6
Jan  9 17:07:17 parachute kernel: usb 3-1: new full speed USB device using uhci_hcd and address 4
Jan  9 17:07:18 parachute kernel: usb 3-1: new full speed USB device using uhci_hcd and address 5

< I unplug/replug >

Jan  9 17:10:21 parachute kernel: usb 1-3: new high speed USB device using ehci_hcd and address 7
Jan  9 17:10:21 parachute kernel: usb 3-1: new full speed USB device using uhci_hcd and address 6
Jan  9 17:10:22 parachute kernel: usb 3-1: new full speed USB device using uhci_hcd and address 7

--------------

result of lspci:

0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 02) 0000:00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge (rev 02) 0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) 0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) 0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) 0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 02) 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02)

#1 lore raw
Quoted 6 lines · mama Smurf

Hello,

my 1 GB PQI Intelligent Stick is often not beeing used by mass storage driver when I plug it.

Do you have several different USB devices connected in the same time? It is possible that devices with different USB speed (high/full) cannot work together. I am not the kernel developer but this is just my experience with latest Linux distributions. The situation can be different with current USB developments.

regards,
Indrek

#2 lore raw
Quoted 5 lines

Do you have several different USB devices connected in the same time? It is possible that devices with different USB speed (high/full) cannot work together. I am not the kernel developer but this is just my experience with latest Linux distributions. The situation can be different with current USB developments.

I tried to remove every other USB device. What is really strange is that it works when I've just booted Linux, but if I unplug/replug the device it seems to be "detected", but is not listed in /proc/bus/usb/devices

#3 lore raw

Which distro/kernel do you have? Have you looked at your distro's bugzilla/buglist? Have you all latest update packages installed?

Quoted 22 lines · Roseline Bonchamp
Quoted 7 lines

Do you have several different USB devices connected in the same time? It is possible that devices with different USB speed (high/full) cannot work together. I am not the kernel developer but this is just my experience with latest Linux distributions. The situation can be different with current USB developments.

I tried to remove every other USB device. What is really strange is that it works when I've just booted Linux, but if I unplug/replug the device it seems to be "detected", but is not listed in /proc/bus/usb/devices
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

.

#4 lore raw
Quoted 3 lines

Which distro/kernel do you have? Have you looked at your distro's bugzilla/buglist? Have you all latest update packages installed?

I use kernel 2.6.10 vanilla.

The distro has nothing to do here I suppose, but it's debian unstable.