[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <479F4B4B.2020000@panasas.com>
Date: Tue, 29 Jan 2008 17:50:35 +0200
From: Boaz Harrosh <bharrosh@...asas.com>
To: Oliver Neukum <oliver@...kum.org>
CC: Jens Axboe <jens.axboe@...cle.com>, Greg KH <greg@...ah.com>,
Matthew Dharm <mdharm-usb@...-eyed-alien.net>,
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 16:31 +0200, Oliver Neukum <oliver@...kum.org> 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.
>
> Regards
> Oliver
> -
I can not see what it is. Yes CONFIG_USB_STORAGE_DEBUG will help.
I have a device here that uses the same trasport/protocol I'll
try to reproduce the failure here.
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists