From: David Brownell <david-b@pacbell.net>
To: Ashwin Bihari <abihari@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: HS USB errors on OMAP3530
Date: Thu, 7 Aug 2008 12:38:30 -0700 [thread overview]
Message-ID: <200808071238.30983.david-b@pacbell.net> (raw)
In-Reply-To: <1f11a5490808071135i3ac8e5dfl4076c21c5296d254@mail.gmail.com>
On Thursday 07 August 2008, Ashwin Bihari wrote:
> sd 0:0:0:0: [sda] Attached SCSI removable disk
> usb 1-2: reset high speed USB device using ehci-omap and address 2
> usb 1-2: device descriptor read/64, error -110
> usb 1-2: device descriptor read/64, error -110
> usb 1-2: reset high speed USB device using ehci-omap and address 2
> usb 1-2: device descriptor read/64, error -110
> usb 1-2: device descriptor read/64, error -110
> usb 1-2: reset high speed USB device using ehci-omap and address 2
> usb 1-2: device not accepting address 2, error -110
> usb 1-2: reset high speed USB device using ehci-omap and address 2
> usb 1-2: device not accepting address 2, error -110
> usb 1-2: USB disconnect, address 2
> sd 0:0:0:0: Device offlined - not ready after error recovery
> Result: hostbyte=0x01 driverbyte=0x00
> end_request: I/O error, dev sda, sector 775288
> end_request: I/O error, dev sda, sector 775288
> ...
I wouldn't assume this is specifically an OMAP issue -- though
it might be in this case. If you could throw a USB sniffer at
the problem and report what that shows, it may be enlightening...
Folk have been reporting these symptoms for some time, but
nobody can quite track it down. I think one person who was
able to observe the problem (I've never seen it) reported that
switching disk, USB cable, *OR* PC host made the problem go
away ... but MS-Windows didn't see it on the same hardware.
As I recall, one person had some recent success shrinking the
"let SET_ADDRESS settle" mdelay in drivers/usb/hub.c (near
line 2535). Strictly speaking, that shouldn't be needed.
- Dave
next parent reply other threads:[~2008-08-07 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1f11a5490808071135i3ac8e5dfl4076c21c5296d254@mail.gmail.com>
2008-08-07 19:38 ` David Brownell [this message]
2008-08-08 1:23 ` HS USB errors on OMAP3530 Ashwin Bihari
2008-08-08 2:25 ` David Brownell
2008-08-07 18:39 Ashwin Bihari
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=200808071238.30983.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=abihari@gmail.com \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox