From: Mike Lampard <mike@mtgambier.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: long-term regression with some usb mass storage devices
Date: Sat, 21 Feb 2009 02:12:03 +1030 [thread overview]
Message-ID: <200902210212.04737.mike@mtgambier.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0902201012150.3071-100000@iolanthe.rowland.org>
On Sat, 21 Feb 2009 01:45:37 am Alan Stern wrote:
> On Fri, 20 Feb 2009, Mike Lampard wrote:
> > On Fri, 20 Feb 2009 05:17:42 pm Mike Lampard wrote:
> > > Hi All,
> > >
> > > I recently plonked a dvd into my usb-attached Pioneer DVR-107d only to
> > > find that the current kernels no longer saw the drive as DVD capable.
> > > In fact, the kernel no longer saw _any_ features of the drive: sr0:
> > > scsi3-mmc drive: 0x/0x caddy. After much bisecting and even more blind
> > > luck I narrowed the problem down to this commit:
> > >
> > > commit bdb2b8cab4392ce41ddfbd6773a3da3334daf836
> > > Author: Alan Stern <stern@rowland.harvard.edu>
> > > Date: Tue Jun 24 14:03:14 2008 -0400
> > >
> > > [SCSI] erase invalid data returned by device
> > >
> > > This patch (as1108) fixes a problem that can occur with certain USB
> > > mass-storage devices: They return invalid data together with a
> > > residue indicating that the data should be ignored. Rather than leave
> > > the invalid data in a transfer buffer, where it can get misinterpreted,
> > > the patch clears the invalid portion of the buffer.
> > >
> > > This solves a problem (wrong write-protect setting detected)
> > > reported by Maciej Rutecki and Peter Teoh.
>
> If this affected your device then the device must not report residues
> correctly. If you provide the device's entry in /proc/bus/usb/devices,
> I'll write a patch adding a blacklist entry for it.
Many thanks.
> It would help if you could also provide a usbmon trace showing what
> happens when you plug the drive in. Instructions are in the kernel
> source file Documentation/usb/usbmon.txt.
/proc/bus/usb/devices:
T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=05e3 ProdID=0701 Rev= 0.02
S: Manufacturer=Genesyslogic
S: Product=USB Mass Storage Device
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 96mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
I'll email the usbmod log directly, to save spamming the list with a 100kb
attachment.
Mike
next prev parent reply other threads:[~2009-02-20 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:47 Mike Lampard
2009-02-20 7:41 ` Mike Lampard
2009-02-20 15:15 ` Alan Stern
2009-02-20 15:42 ` Mike Lampard [this message]
2009-02-20 19:15 ` Alan Stern
2009-02-21 6:43 ` Mike Lampard
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=200902210212.04737.mike@mtgambier.net \
--to=mike@mtgambier.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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
all inboxes | Powered by JetHome®