All of lore.kernel.org
 help / color / mirror / Atom feed
From: mama Smurf <roseline.bonchamp@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: remove Attach another file remove Attach another file remove Attach another file USB mass storage not always detecting my 1GB PQI intelligent stick
Date: Sun, 9 Jan 2005 17:25:55 +0100	[thread overview]
Message-ID: <884a349a050109082516b0740e@mail.gmail.com> (raw)

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

Hello,

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

>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

[-- Attachment #2: kern.log --]
[-- Type: application/octet-stream, Size: 3919 bytes --]

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)

             reply	other threads:[~2005-01-09 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 16:25 mama Smurf [this message]
2005-01-09 16:42 ` remove Attach another file remove Attach another file remove Attach another file USB mass storage not always detecting my 1GB PQI intelligent stick Indrek Kruusa
2005-01-09 19:12   ` Roseline Bonchamp
2005-01-09 19:26     ` Indrek Kruusa
2005-01-09 22:17       ` Roseline Bonchamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=884a349a050109082516b0740e@mail.gmail.com \
    --to=roseline.bonchamp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.