All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
Cc: Matthew Wilcox <matthew@wil.cx>,
	LKML-SCSI <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	mike.miller@hp.com,
	James Bottomley <james.bottomley@hansenpartnership.com>
Subject: Re: READ CAPACITY (16) failing
Date: Fri, 10 Apr 2009 17:04:07 -0400	[thread overview]
Message-ID: <49DFB447.5040009@interlog.com> (raw)
In-Reply-To: <20090410193134.GA2615@beardog.cca.cpqcorp.net>

Mike Miller (OS Dev) wrote:
> On Wed, Apr 08, 2009 at 01:54:48PM -0600, Matthew Wilcox wrote:
>> On Wed, Apr 08, 2009 at 02:43:57PM -0500, Mike Miller (OS Dev) wrote:
>>> I'm working on the HP Smart Array SCSI driver (hpsa) and I'm seeing the
>>> following failures:
>>>
>>> hpsa1: <0x3230> at PCI 0000:02:00.0 IRQ 76 using DAC
>>> scsi4 : hpsa
>>> scsi 4:0:0:0: Direct-Access     HP       LOGICAL VOLUME   5.20 PQ: 0 ANSI: 5
>>> sd 4:0:0:0: Attached scsi generic sg4 type 0
>>> sd 4:0:0:0: [sdd] READ CAPACITY(16) failed
>>> sd 4:0:0:0: [sdd] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
>>> sd 4:0:0:0: [sdd] Sense not available.
>>> hpsa: cp ffff8800cf400000 has check condition: unknown type: Sense: 0x5,
>>> ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[a0 00 00 00 00 00 00 00 10
>>> 00]
>>> The READ CAPACITY failures are what I'm concerned about. I can't seem to track
>>> down why that's failing.
>>> I've tried printing out the_result from sd but it's not printing out. I'm
>>> assuming that anytime I load the driver it goes thru sd.
>>>
>>> 	if (the_result) {
>>> 		sense_valid = scsi_sense_valid(&sshdr);
>>> 		if (sense_valid &&
>>> 			sshdr.sense_key == ILLEGAL_REQUEST &&
>>> 			(sshdr.asc == 0x20 || sshdr.asc == 0x24) &&
>>> 			sshdr.ascq == 0x00)
>>> 			/* Invalid Command Operation Code or
>>> 			 * Invalid Field in CDB, just retry
>>> 			 * silently with RC10 */
>>> 			return -EINVAL;
>>> 		}
>>> 	retries--;
>>> 	} while (the_result && retries);
>>> 	printk(KERN_WARNING "sd-mfm: the_result = %d\n", the_result);
>> Probably the device you're testing against doesn't support RC16, which
>> is fine.  But for some reason, we're not getting valid sense data back
>> from the device.  Now, there's two responses to this that seem rational
>> to me:
>>
>>  - In sd.c, if the drive has returned no/invalid sense data, try RC10
>>    silently, just like the 0x20 / 0x24 ASC case.
>>  - Find out why this drive doesn't report valid sense data when attached
>>    to hpsa.  I assume it does report valid sense data when attached to
>>    some other scsi card?
> 
> Me again,
> The controllers do support RC16. After some more work it looks like RC16 is
> never getting to the driver. I'm snooping the CDB's of all requests as well
> as the completions from the driver and I never see a 0x9e. I do see the
> RC10 (0x25) though, so I think my debug is right.
> 
> Why would I never the see the command in the driver?

struct Scsi_host::max_cmd_len < 16 would be one reason but
one would expect an indicative message in the log.

Does a 'sg_readcap --long -vvv <device>' give you any further
information?

Doug Gilbert

  reply	other threads:[~2009-04-10 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 19:43 READ CAPACITY (16) failing Mike Miller (OS Dev)
2009-04-08 19:54 ` Matthew Wilcox
2009-04-09 15:22   ` Mike Miller (OS Dev)
2009-04-10 19:31   ` Mike Miller (OS Dev)
2009-04-10 21:04     ` Douglas Gilbert [this message]
2009-04-10 22:28     ` James Bottomley
2009-04-14 18:23       ` Mike Miller (OS Dev)

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=49DFB447.5040009@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mike.miller@hp.com \
    --cc=mikem@beardog.cca.cpqcorp.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.