public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [linux-usb-devel] 2.6: USB disk unusable level of data corruption
Date: Fri, 4 Feb 2005 12:41:27 -0800	[thread overview]
Message-ID: <200502041241.28029.david-b@pacbell.net> (raw)
In-Reply-To: <1107519382.1703.7.camel@localhost.localdomain>

On Friday 04 February 2005 4:16 am, Rusty Russell wrote:
> 
> Is USB/SCSI just terminally broken under 2.6?  

I don't think so, but there are problems that appear in some
hardware configs and not others.  Many folk report no problems;
a (very) few report nothing but.

If you've verified this on 2.6.10, then you certainly have
have the ehci-hcd (re)queueing race fix that has made a big
difference for some folk.  I don't know of any other issues
in that driver that could explain usb-storage problems.

What hardware config do you have?

  - Whose EHCI controller and revision?  I've never had
    good luck with VIA VT6202.  ("lspci -v".)

  - Whose USB storage adapter?  ("lsusb -v", or in this
    case the /proc/bus/usb/devices entry would be ok.)
    GeneSys adapters have been the most problematic,
    but they're hardly the only ones with quirks.

Thing is, that driver stack isn't especially thin:  SCSI isn't
the top, and it's got usb-storage, usbcore, and a USB HCD under
it.  That makes it harder to track down root causes, even when
there is just a single one and it's in those drivers (rather
than being hardware misbehavior).

- Dave

  reply	other threads:[~2005-02-04 20:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 12:16 2.6: USB disk unusable level of data corruption Rusty Russell
2005-02-04 20:41 ` David Brownell [this message]
2005-02-05  0:39   ` [linux-usb-devel] " John Stoffel
2005-02-06 15:59     ` Giuseppe Bilotta
2005-02-07  4:01       ` David Brownell
2005-02-07 22:39         ` Giuseppe Bilotta
2005-02-07  2:55   ` Rusty Russell
2005-02-07  5:15     ` David Brownell
2005-02-07  6:46       ` Rusty Russell
2005-02-04 20:55 ` Alan Stern
2005-02-04 21:31   ` David Brownell
2005-02-06  5:18   ` 2.6: USB Storage hangs machine on bootup for ~2 minutes Parag Warudkar
2005-02-04 21:37 ` 2.6: USB disk unusable level of data corruption Pete Zaitcev
2005-02-05  0:40   ` Parag Warudkar
2005-02-05  1:44     ` Greg KH
2005-02-05  2:30       ` Parag Warudkar
2005-02-05  4:54         ` Greg KH

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=200502041241.28029.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=rusty@rustcorp.com.au \
    /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