public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: scsi: aic7xxx hang since v2.6.28-rc1 ...
Date: Wed, 18 Feb 2009 11:16:43 -0800	[thread overview]
Message-ID: <20090218191643.GA16347@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090218155817.GC23989@elte.hu>

Ingo Molnar <mingo@elte.hu> wrote:
> 
> * Alan Stern <stern@rowland.harvard.edu> wrote:
> 
> > I have no idea if this will make any difference for the 
> > problem you're seeing, but it has been submitted and it's 
> > worth trying out.  If the problem still occurs, I'll write a 
> > diagnostic patch to add log messages giving the destiny of 
> > each request in scsi_io_completion().
> 
> OK, i've undone the reverts and have applied your fix - it will 
> take a few hours to see whether the hang still occurs.
> 

I know already started your testing, but..

I find it informative to set my scsi logging to the value below to display
non-zero IO status on commands. The overhead impact is low for good
completions.

sysctl -w dev.scsi.logging_level=4100

Note: This does not provide the exact policy that scsi_io_completion will
take on the IO, but it provides the input to scsi_io_completion which
should help.

-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com

  reply	other threads:[~2009-02-18 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15 11:44 scsi: aic7xxx hang since v2.6.28-rc1 Ingo Molnar
2009-02-15 11:58 ` Ingo Molnar
2009-02-17 20:10   ` Alan Stern
2009-02-18 15:58     ` Ingo Molnar
2009-02-18 19:16       ` Mike Anderson [this message]
2009-02-18 19:20         ` Ingo Molnar
2009-02-19 20:12       ` Alan Stern
2009-02-19 20:23         ` Ingo Molnar

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=20090218191643.GA16347@linux.vnet.ibm.com \
    --to=andmike@linux.vnet.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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