On Tue, Jan 29, 2008 at 08:15:04PM +0100, Jens Axboe wrote:
quoted text
> 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@or=
acle.com> wrote:
quoted text
> > > > > > > > On Tue, Jan 29 2008, Boaz Harrosh wrote:
> > > > > > > >> Greg KH wrote:
> > > > > =20
> > > > > > > > No difference, still just a lot of resets.
> > > > > > > >=20
> > > > > > > Where you able to figure out which usb storage transport is u=
sed?
quoted text
> > > > > > >=20
> > > > > > > in drivers/usb/storage/usb.c you have get_protocol() and get_=
transport()
quoted text
> > > > > > > functions. I'm not sure if these get stored in sysfs perhaps.=
 This will
quoted text
> > > > > > > pinpoint better where to look. Let me research a bit.=20
> > > > > >=20
> > > > > > Did the quick'n easy and dumped it. Protocol is 'Transparent SC=
SI' and
quoted text
> > > > > > transport is 'Bulk'
> > > > >=20
> > > > > You can recompile your kernel with CONFIG_USB_DEBUG and CONFIG_ST=
ORAGE_DEBUG
quoted text
> > > > > That should tell the reason for the resets.
> > > >=20
> > > > Sure, I'll do that. Will post the results tonight.
> > >=20
> > > 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 t=
he
quoted text
> > > messages.
> > >=20
> > > It all looks good until the MODE_SENSE command, where it only transfe=
rs
quoted text
> > > 4 of 192 bytes.
> >=20
> > No, that's not the problem.  This is the problem:
>=20
> 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

--=20
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.=
net=20
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