All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Retry INQUIRY on power-on
Date: Mon, 03 Apr 2006 12:37:08 -0500	[thread overview]
Message-ID: <44315D44.6080508@cs.wisc.edu> (raw)
In-Reply-To: <4430C4EA.8070609@suse.de>

Hannes Reinecke wrote:
> James Bottomley wrote:
>> On Fri, 2006-03-31 at 15:12 +0200, Hannes Reinecke wrote:
>>> So we really should loosen that statement to do retry for all ASC 0x29
>>> values as a power-on might well have occured without a reset.
>> Actually, there's probably no reason to qualify the UNIT_ATTENTION at
>> all.  Any device that replies UNIT_ATTENTION to INQUIRY is out of spec,
>> so it's reasonable to assume that the ASC/ASCQ responses aren't in spec
>> either.  There doesn't seem to be a disadvantage to just retrying three
>> times in all unit attention cases.
>>
> Well, after looking through the trace I discovered it's not actually a
> broken device, but rather more a driver issue:
> 
> - SCSI ML sends inquiry
> - HBA cannot send message as transport parameters are invalid
> - HBA requests sense
> - HBA sets the sense code and returns command with code 'ADD_TO_MLQUEUE'
>   to inform ML to retry the command
> 
> Only the ML fails to honour the ADD_TO_MLQUEUE code as this is
> scsi_scan(), which doesn't check for it.
> So if anything then rather the code in scsi_scan should been fixed to
> retry the command if so advised from the LLD.
> 

Normally, a request from the scsi scan code should go through 
scsi_softirq_done which checks for scsi_decide_disposition returning 
ADD_TO_MLQUEUE. Is aic7xxx setting the host byte to DID_REQUEUE?

      reply	other threads:[~2006-04-03 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 13:12 [PATCH] Retry INQUIRY on power-on Hannes Reinecke
2006-03-31 15:16 ` James Bottomley
2006-04-03  6:47   ` Hannes Reinecke
2006-04-03 17:37     ` Mike Christie [this message]

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=44315D44.6080508@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@SteelEye.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    /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.