From: Boaz Harrosh <bharrosh@panasas.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
Tarkan Erimer <tarkan.erimer@turknet.net.tr>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [BISECTED] Re: [BUG] Linux-2.6.31-rc1 Fails To Recognize Some USB Disks
Date: Mon, 27 Jul 2009 18:47:52 +0300 [thread overview]
Message-ID: <4A6DCC28.7000309@panasas.com> (raw)
In-Reply-To: <4A6DCA7F.4080006@panasas.com>
On 07/27/2009 06:40 PM, Boaz Harrosh wrote:
> On 07/27/2009 06:19 PM, Martin K. Petersen wrote:
>>>>>>> "Boaz" == Boaz Harrosh <bharrosh@panasas.com> writes:
>> Boaz> Haa, OK. I thought INQUIRY EVPD=1 page=0 was so old it sure must
>> Boaz> be supported but you are saying it's only SBC2/SPC3. So I guess
>> Boaz> there is nothing else we can do.
>>
>> Yes, EVPD must be supported. USB-ATA bridge firmware writers are
>> dyslexic. Film at 11.
>>
>> What I'm saying is that *our* reason for sending out extended inquiry
>> appeared in SBC2 (block limits VPD). So there is no point in asking
>> devices older than that.
>>
>> The fact that this fixes the problem for Tarkan's crappy disk is a
>> (quasi-intentional) side effect. My patch simply tries to be
>> conservative about asking for those pages.
>>
>>
>> Boaz> What I hate about all this is that in USB the scsi_level is hard
>> Boaz> coded at the driver, without actually been able to probe the
>> Boaz> device about it.
>>
>> Huh, what?
>>
>
> Look in drivers/usb/storage::slave_configure
>
> /* Some devices report a SCSI revision level above 2 but are
> * unable to handle the REPORT LUNS command (for which
> * support is mandatory at level 3). Since we already have
> * a Get-Max-LUN request, we won't lose much by setting the
> * revision level down to 2. The only devices that would be
> * affected are those with sparse LUNs. */
> if (sdev->scsi_level > SCSI_2)
> sdev->sdev_target->scsi_level =
> sdev->scsi_level = SCSI_2;
>
Maybe it should be:
if (sdev->scsi_level > SCSI_2 && sdev->scsi_level < SCSI_SPC_2)
sdev->sdev_target->scsi_level =
sdev->scsi_level = SCSI_2;
To account for the devices the comment is talking about. Which seems to be
written at the time SCSI_3 was the highest level.
> So the scsi_level is hard coded to very low.
> Or am I reading this code wrong and it is only triggered for some but not
> all devices?
>
> Boaz
> --
Sigh
Boaz
next prev parent reply other threads:[~2009-07-27 15:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 7:03 [BUG] Linux-2.6.31-rc1 Fails To Recognize Some USB Disks Tarkan Erimer
2009-06-29 3:21 ` Martin K. Petersen
2009-06-29 8:17 ` Tarkan Erimer
2009-06-29 14:30 ` Martin K. Petersen
2009-07-15 7:46 ` Tarkan Erimer
2009-07-20 2:25 ` Martin K. Petersen
2009-07-21 8:08 ` Tarkan Erimer
2009-07-24 10:55 ` [BISECTED] " Tarkan Erimer
2009-07-24 11:44 ` Tarkan Erimer
2009-07-24 14:02 ` Martin K. Petersen
2009-07-24 15:17 ` Tarkan Erimer
2009-07-27 1:28 ` Martin K. Petersen
2009-07-27 2:06 ` Matthew Wilcox
2009-07-27 2:43 ` Martin K. Petersen
2009-07-27 8:27 ` Boaz Harrosh
2009-07-27 14:29 ` Martin K. Petersen
2009-07-27 14:50 ` Matthew Wilcox
2009-07-27 15:10 ` Martin K. Petersen
2009-07-27 14:51 ` Boaz Harrosh
2009-07-27 15:19 ` Martin K. Petersen
2009-07-27 15:40 ` Boaz Harrosh
2009-07-27 15:47 ` Boaz Harrosh [this message]
2009-07-27 15:55 ` Martin K. Petersen
2009-07-27 7:31 ` Tarkan Erimer
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=4A6DCC28.7000309@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthew@wil.cx \
--cc=tarkan.erimer@turknet.net.tr \
/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