From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Alan Stern <stern@rowland.harvard.edu>,
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 13:31:36 -0800 [thread overview]
Message-ID: <200502041331.37042.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0502041539350.674-100000@ida.rowland.org>
On Friday 04 February 2005 12:55 pm, Alan Stern wrote:
>
> The most likely explanation seems to be hardware problems. Particularly
> for high-speed USB devices, 2.6 drives the hardware much closer to the
> limit than 2.4 or Windows (to judge by the problem reports we've seen).
Agreed ... though limiting usb-storage I/O requests to 64 KB does tend to
mask that difference. Some network adapters get better throughput than
Windows, too. URB queueing does the trick ... not really usable on 2.4
kernels, but the costs on 2.6 seem substantially lower than on Windows.
> One case came up just a couple of days ago, in which this sort of data
> corruption was definitively traced to a known erratum in the peripheral's
> USB interface. (The controller chip was an old revision which has been
> supplanted, but who knows what sort of hardware lurks in the hearts of
> commercial drives?)
If you're thinking of that net2280 issue, that erratum was specific
to full speed modes, and never appeared at high speed. Also, that chip
wouldn't be used in mass market IDE adapters. (Too pricey compared to
the custom chips that have no need for a CPU or PCI.)
But the point is good: it's easy for hardware to have bugs there.
- Dave
next prev parent reply other threads:[~2005-02-04 21:52 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 ` [linux-usb-devel] " David Brownell
2005-02-05 0:39 ` 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 [this message]
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=200502041331.37042.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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox