public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 11:27:08 +0300	[thread overview]
Message-ID: <4A6D64DC.3020001@panasas.com> (raw)
In-Reply-To: <yq18wiakfq4.fsf@sermon.lab.mkp.net>

On 07/27/2009 05:43 AM, Martin K. Petersen wrote:
>>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:
> 
> First let's see if I actually interpreted the responses correctly and
> that this fixes the issue.
> 
> Matthew> and the sd code seems to check for that.  So what bug are you
> Matthew> papering over here?
> 
> The USB drive in question appears to go tits up when we send it an
> extended inquiry.  I contemplated adding a BLIST option but we really
> only need EVPD to access pages 0xB0 and 0xB1.  

I don't understand. The device in question breaks when we try to read
a page that it reported it supports? we did do
        /* Ask for all the pages supported by this device */
        result = scsi_vpd_inquiry(sdev, buf, 0, 255);
        if (result)
                goto fail;
Didn't we? Are we checking that 0xB0 or 0xB1 are returned?

The Block Limits page
> appeared in SBC2 so I'm just trying to play it safe.  And hopefully fix
> Tarkan's problem in the process.
> 

Thanks
Boaz

  reply	other threads:[~2009-07-27  8:27 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 [this message]
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
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=4A6D64DC.3020001@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