[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080129193713.GP14375@one-eyed-alien.net>
Date: Tue, 29 Jan 2008 11:37:13 -0800
From: Matthew Dharm <mdharm-kernel@...-eyed-alien.net>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: Oliver Neukum <oliver@...kum.org>,
Boaz Harrosh <bharrosh@...asas.com>, Greg KH <greg@...ah.com>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
linux-scsi@...r.kernel.org
Subject: Re: [BUG] 2.6.24-git usb reset problems
On Tue, Jan 29, 2008 at 08:15:04PM +0100, Jens Axboe wrote:
> On Tue, Jan 29 2008, Matthew Dharm wrote:
> > On Tue, Jan 29, 2008 at 07:39:11PM +0100, Jens Axboe wrote:
> > > On Tue, Jan 29 2008, Jens Axboe wrote:
> > > > On Tue, Jan 29 2008, Oliver Neukum wrote:
> > > > > Am Dienstag, 29. Januar 2008 15:11:08 schrieb Jens Axboe:
> > > > > > On Tue, Jan 29 2008, Boaz Harrosh wrote:
> > > > > > > On Tue, Jan 29 2008 at 15:54 +0200, Jens Axboe <jens.axboe@...cle.com> wrote:
> > > > > > > > On Tue, Jan 29 2008, Boaz Harrosh wrote:
> > > > > > > >> Greg KH wrote:
> > > > >
> > > > > > > > No difference, still just a lot of resets.
> > > > > > > >
> > > > > > > Where you able to figure out which usb storage transport is used?
> > > > > > >
> > > > > > > in drivers/usb/storage/usb.c you have get_protocol() and get_transport()
> > > > > > > functions. I'm not sure if these get stored in sysfs perhaps. This will
> > > > > > > pinpoint better where to look. Let me research a bit.
> > > > > >
> > > > > > Did the quick'n easy and dumped it. Protocol is 'Transparent SCSI' and
> > > > > > transport is 'Bulk'
> > > > >
> > > > > You can recompile your kernel with CONFIG_USB_DEBUG and CONFIG_STORAGE_DEBUG
> > > > > That should tell the reason for the resets.
> > > >
> > > > Sure, I'll do that. Will post the results tonight.
> > >
> > > OK, fresh boot with CONFIG_USB_DEBUG and CONFIG_STORAGE_DEBUG. Plugged
> > > in the device, waited 10 seconds or so and pulled it out. These are the
> > > messages.
> > >
> > > It all looks good until the MODE_SENSE command, where it only transfers
> > > 4 of 192 bytes.
> >
> > No, that's not the problem. This is the problem:
>
> It's where the problem starts, otherwise there would not be a need to
> sense :-)
MODE_SENSE has nothing to do with it. A short MODE_SENSE response is
perfectly valid, and the log shows it was handled correctly and subsequent
commands worked just fine. It's not until the TUR fails that we get the
problem.
Matt
--
Matthew Dharm Home: mdharm-usb@...-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
P: Nine more messages in admin.policy.
M: I know, I'm typing as fast as I can!
-- Pitr and Mike
User Friendly, 11/27/97
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists