From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Greg KH <greg@kroah.com>,
Christian Axelsson <smiler@lanil.mine.nu>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [2.6.10-rc2-mm3] Broken usb2 mass-storage?
Date: Tue, 30 Nov 2004 08:34:04 -0800 [thread overview]
Message-ID: <200411300834.04188.david-b@pacbell.net> (raw)
In-Reply-To: <20041129232014.GB21134@kroah.com>
On Monday 29 November 2004 3:20 pm, Greg KH wrote:
> > Then I try to access the disk (via fdisk or mount anything) and I get
> > the following in dmesg:
> >
> > usb 1-2: reset high speed USB device using ehci_hcd and address 4
> > usb 1-2: scsi_eh_0 timed out on ep0in
>
> Ick, not good.
Has this device always needed a reset? The interesting
bits of the log are probably the ones immediatelly preceding
the decision to reset it. Two possibilities come to mind:
something broke the reset logic (the device is clearly not
working right after the reset) ... or something changed to
make the device go bonkers _before_ the reset, which seems
a bit more likely with my current lack-of-facts. (Especially
if rc2 works and mm3 doesn't.)
- Dave
> ...
>
> > usb 1-2: device descriptor read/64, error -110
> > usb 1-2: scsi_eh_0 timed out on ep0in
> > usb 1-2: device descriptor read/64, error -110
> > usb 1-2: reset high speed USB device using ehci_hcd and address 4
> > usb 1-2: scsi_eh_0 timed out on ep0in
> > usb 1-2: device descriptor read/64, error -110
> >
> > Then it stalls a while and this shows up:
> >
> > scsi: Device offlined - not ready after error recovery: host 0
> > channel 0 id 0 lun 0
> > usb 1-2: USB disconnect, address 4
> > scsi0 (0:0): rejecting I/O to offline device
> > scsi0 (0:0): rejecting I/O to offline device
> > usb-storage: device scan complete
> > usb 1-2: new high speed USB device using ehci_hcd and address 5
> > usb 1-2: khubd timed out on ep0in
> > usb 1-2: device descriptor read/64, error -110
> >
> > And repeats this.. I think you get the point ;)
> > The process trying to access the disk hangs.
> > Note: the drive works flawless under windows and has worked fine under
> > linux during various stages of the 2.5 and early 2.6 kernels :)
> >
prev parent reply other threads:[~2004-11-30 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 22:36 Christian Axelsson
2004-11-29 23:20 ` Greg KH
2004-11-30 16:34 ` David Brownell [this message]
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=200411300834.04188.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=smiler@lanil.mine.nu \
/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
all inboxes | Powered by JetHome®