From: "Rogério Brito" <rbrito@ime.usp.br>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Robert Hancock <hancockrwd@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [2.6.30-rc2] usb reset during big file transfer and ext3 error
Date: Sun, 24 May 2009 04:16:37 -0300 [thread overview]
Message-ID: <20090524071637.GA5487@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0905011509220.2989-100000@iolanthe.rowland.org>
Hi, Alan & Co.
On May 01 2009, Alan Stern wrote:
> I've got a USB disk drive and cable that do not work on my home PC,
> although they do work on my office PC. If I use a different cable then
> the drive does work on the home PC. If I use the same cable but
> substitute a USB stick for the drive, again it works. So which
> component is bad: the home PC, the cable, or the drive?
Yes, right.
Resuming our earlier discussion, I got another case of weird USB
messages here with kernel 2.6.30-rc5 (sorry, I have not yet had time to
use anything newer).
My father has a USB (1.1, I would say, which matches what the logs say)
stick/pen drive that, when I connect to my ECHI controller on my machine
with an ICH5 chipset, I get:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ 2285.628018] usb 4-2: new full speed USB device using uhci_hcd and address 2
[ 2285.784924] usb 4-2: New USB device found, idVendor=067b, idProduct=2315
[ 2285.784932] usb 4-2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 2285.784936] usb 4-2: Product: USB Embedded Hub
[ 2285.784939] usb 4-2: Manufacturer: Leading Driver Co.,LTD.
[ 2285.785039] PM: Adding info for usb:4-2
[ 2285.785084] usb 4-2: configuration #1 chosen from 1 choice
[ 2285.787985] PM: Adding info for usb:4-2:1.0
[ 2285.788046] hub 4-2:1.0: USB hub found
[ 2285.789956] hub 4-2:1.0: 2 ports detected
[ 2285.794051] PM: Adding info for No Bus:usbdev4.2_ep81
[ 2285.794137] PM: Adding info for No Bus:usbdev4.2_ep00
[ 2286.064854] usb 4-2.1: new full speed USB device using uhci_hcd and address 3
[ 2286.184819] usb 4-2.1: New USB device found, idVendor=067b, idProduct=2317
[ 2286.184825] usb 4-2.1: New USB device strings: Mfr=1, Product=4, SerialNumber=0
[ 2286.184830] usb 4-2.1: Product: USB Mass Storage Device
[ 2286.184833] usb 4-2.1: Manufacturer: Leading Driver Co.,LTD.
[ 2286.184926] PM: Adding info for usb:4-2.1
[ 2286.184974] usb 4-2.1: configuration #1 chosen from 1 choice
[ 2286.187878] PM: Adding info for usb:4-2.1:1.0
[ 2286.187994] PM: Adding info for No Bus:usbdev4.3_ep01
[ 2286.188068] PM: Adding info for No Bus:usbdev4.3_ep82
[ 2286.188133] PM: Adding info for No Bus:usbdev4.3_ep00
[ 2286.239239] SCSI subsystem initialized
[ 2286.253935] Initializing USB Mass Storage driver...
[ 2286.254816] usb 4-2.2: new full speed USB device using uhci_hcd and address 4
[ 2286.255696] scsi0 : SCSI emulation for USB Mass Storage devices
[ 2286.255763] PM: Adding info for scsi:host0
[ 2286.255830] PM: Adding info for No Bus:host0
[ 2286.256419] usbcore: registered new interface driver usb-storage
[ 2286.256426] USB Mass Storage support registered.
[ 2286.257378] usb-storage: device found at 3
[ 2286.257382] usb-storage: waiting for device to settle before scanning
[ 2286.372799] usb 4-2.2: New USB device found, idVendor=067b, idProduct=2316
[ 2286.372807] usb 4-2.2: New USB device strings: Mfr=1, Product=5, SerialNumber=0
[ 2286.372811] usb 4-2.2: Product: USB Security Device
[ 2286.372814] usb 4-2.2: Manufacturer: Leading Driver Co.,LTD.
[ 2286.372906] PM: Adding info for usb:4-2.2
[ 2286.372957] usb 4-2.2: configuration #1 chosen from 1 choice
[ 2286.375825] PM: Adding info for usb:4-2.2:1.0
[ 2286.375951] PM: Adding info for No Bus:usbdev4.4_ep00
[ 2291.258587] usb-storage: device scan complete
[ 2291.261567] scsi 0:0:0:0: Direct-Access Prolific USB Flash Disk 1.00 PQ: 0 ANSI: 0 CCS
[ 2291.262023] PM: Adding info for scsi:target0:0:0
[ 2291.262497] PM: Adding info for scsi:0:0:0:0
[ 2291.262711] PM: Adding info for No Bus:0:0:0:0
[ 2291.273924] Driver 'sd' needs updating - please use bus_type methods
[ 2291.274557] PM: Adding info for No Bus:0:0:0:0
[ 2291.280525] sd 0:0:0:0: [sda] 256000 512-byte hardware sectors: (131 MB/125 MiB)
[ 2291.283532] sd 0:0:0:0: [sda] Write Protect is off
[ 2291.283539] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 2291.283543] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 2291.283603] PM: Adding info for No Bus:sda
[ 2291.290517] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.290523] : Sense Key : 0x0 [current]
[ 2291.290529] : ASC=0x0 ASCQ=0x0
[ 2291.298513] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 2291.298520] sda: sda1
[ 2291.304573] PM: Adding info for No Bus:sda1
[ 2291.309522] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.309527] : Sense Key : 0x0 [current]
[ 2291.309533] : ASC=0x0 ASCQ=0x0
[ 2291.309625] PM: Adding info for No Bus:8:0
[ 2291.309651] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 2291.330510] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.330518] : Sense Key : 0x0 [current]
[ 2291.330524] : ASC=0x0 ASCQ=0x0
[ 2291.634434] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.634440] : Sense Key : 0x0 [current]
[ 2291.634446] : ASC=0x0 ASCQ=0x0
[ 2291.703422] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.703430] : Sense Key : 0x0 [current]
[ 2291.703436] : ASC=0x0 ASCQ=0x0
[ 2291.725411] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.725415] : Sense Key : 0x0 [current]
[ 2291.725420] : ASC=0x0 ASCQ=0x0
[ 2291.735409] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2291.735417] : Sense Key : 0x0 [current]
[ 2291.735423] : ASC=0x0 ASCQ=0x0
[ 2292.036329] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2292.036336] : Sense Key : 0x0 [current]
[ 2292.036342] : ASC=0x0 ASCQ=0x0
[ 2292.046354] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2292.046361] : Sense Key : 0x0 [current]
[ 2292.046367] : ASC=0x0 ASCQ=0x0
[ 2292.348248] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2292.348255] : Sense Key : 0x0 [current]
[ 2292.348261] : ASC=0x0 ASCQ=0x0
[ 2292.414240] sd 0:0:0:0: ioctl_internal_command return code = 8000002
[ 2292.414246] : Sense Key : 0x0 [current]
[ 2292.414252] : ASC=0x0 ASCQ=0x0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
In particular, those ioctl_internal_command return code messages seem
strange, regarding other USB devices that I have. Are they being shown
because I have some debugging information in my kernel or are they
abnormal?
Thanks for any help,
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next prev parent reply other threads:[~2009-05-24 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 11:10 [2.6.30-rc2] usb reset during big file transfer and ext3 error Rogério Brito
2009-04-22 0:34 ` Robert Hancock
2009-04-22 22:06 ` Rogério Brito
2009-04-23 2:53 ` Alan Stern
2009-05-01 9:15 ` Rogério Brito
2009-05-01 19:16 ` Alan Stern
2009-05-24 7:16 ` Rogério Brito [this message]
2009-05-24 14:40 ` Alan Stern
2009-05-24 15:32 ` ioctl_internal_command messages (was: Re: [2.6.30-rc2] usb reset during big file transfer and ext3 error) Rogério Brito
2009-05-24 16:11 ` [2.6.30-rc2] usb reset during big file transfer and ext3 error Rogério Brito
2009-05-25 2:34 ` Alan Stern
2009-05-25 15:13 ` [PATCH] usb-storage: include USB drive in unusual_devs list Rogério Brito
2009-05-25 21:03 ` Alan Stern
2009-05-25 21:41 ` Rogério Brito
2009-08-01 18:30 ` Rogério Brito
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=20090524071637.GA5487@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.