From: Joe Sevy <jmsevy@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: usb mass storage bug
Date: Mon, 11 Jul 2005 13:30:47 -0700 (PDT) [thread overview]
Message-ID: <20050711203047.39437.qmail@web33113.mail.mud.yahoo.com> (raw)
Sorry, no logs or dmesg to report; just performance.
Using kernel 2.6.12: USB flash drive (san-disk cruzer
micro) Copy FROM drive is normal and quick; copy TO
drive is amazingly slow. (30 minutes for 50K file).
Used same configuration as for 2.6.11.11. Cured by
going back to old kernel.
Sorry I can't give better report.
Thank you.
Joe Sevy
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2005-07-11 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 20:30 Joe Sevy [this message]
2005-07-12 3:09 ` usb mass storage bug Greg KH
[not found] ` <mailman.1121138161.21500.linux-kernel2news@redhat.com>
2005-07-13 5:50 ` Pete Zaitcev
2005-07-13 20:53 ` Greg KH
2005-07-13 21:16 ` Alberto Santini
2005-07-13 21:31 ` Pete Zaitcev
[not found] <mailman.1121114341.22024.linux-kernel2news@redhat.com>
2005-07-13 5:39 ` Pete Zaitcev
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=20050711203047.39437.qmail@web33113.mail.mud.yahoo.com \
--to=jmsevy@yahoo.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).