public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: bugme-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net
Subject: Re: [Bug 12120] [Block layer or SCSI] requests aborted too early during check_partition()
Date: Sun, 30 Nov 2008 10:44:02 +0100	[thread overview]
Message-ID: <49326062.6000800@s5r6.in-berlin.de> (raw)
In-Reply-To: <1228003702.4636.29.camel@localhost.localdomain>

James Bottomley wrote:
> Theory number two is a block timeout cockup.  It looks like
> sdev->timeout is vestigial and has zero value, so we shouldn't be using
> it in the start command, so try this.
> 
> If this works, the correct fix will be to kill the sdev timeout
> parameter so we get a compile failure where anything tries to use it.
> 
> James
> 
> ---
> 
> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
> index 3863617..de3f6d0 100644
> --- a/drivers/scsi/scsi_error.c
> +++ b/drivers/scsi/scsi_error.c
> @@ -933,7 +933,7 @@ static int scsi_eh_try_stu(struct scsi_cmnd *scmd)
>  
>  		for (i = 0; rtn == NEEDS_RETRY && i < 2; i++)
>  			rtn = scsi_send_eh_cmnd(scmd, stu_command, 6,
> -						scmd->device->timeout, 0);
> +						3*SENSE_TIMEOUT, 0);
>  
>  		if (rtn == SUCCESS)
>  			return 0;
> 
> 

Yes, this works with all of the SBP-2 bridges here which exhibit this
false TEST UNIT READY "GOOD" status.

BTW, 3 * SENSE_TIMEOUT == 30 seconds may actually be a little bit narrow
as a START UNIT timeout.  The disks which I tested here --- a few 7200
RPM IDE or SATA disks behind the SBP-2 bridges --- usually take about 7
seconds to spin up in single-disk enclosures and 14 seconds in dual-disk
enclosures, since the bridge spins them up serially.  But a dual-disk
enclosure with Hitachi Deskstar 7K400 took 28 seconds.  Maybe this
should be used in scsi_eh_try_stu:
include/scsi/scsi.h:#define START_STOP_TIMEOUT          (60 * HZ)

Thanks a lot,
-- 
Stefan Richter
-=====-==--- =-== ====-
http://arcgraph.de/sr/

  reply	other threads:[~2008-11-30  9:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 13:19 [Bug 12120] New: [Block layer or SCSI] requests aborted too early during check_partition() bugme-daemon
2008-11-29 15:12 ` Stefan Richter
2008-11-29 18:35   ` James Bottomley
2008-11-29 15:12 ` [Bug 12120] " bugme-daemon
2008-11-29 18:36 ` bugme-daemon
2008-11-29 19:29 ` bugme-daemon
2008-11-29 19:32 ` bugme-daemon
2008-11-29 19:54   ` James Bottomley
2008-11-29 21:30     ` Stefan Richter
2008-11-29 21:45       ` Stefan Richter
2008-11-30  0:08       ` James Bottomley
2008-11-30  9:44         ` Stefan Richter [this message]
2008-11-30 16:16           ` James Bottomley
2008-11-29 19:55 ` bugme-daemon
2008-11-29 21:30 ` bugme-daemon
2008-11-29 21:45 ` bugme-daemon
2008-11-30  0:08 ` bugme-daemon
2008-11-30  9:44 ` bugme-daemon
2008-11-30 16:16 ` bugme-daemon
2008-12-04  1:15 ` bugme-daemon
2008-12-04  6:38 ` bugme-daemon

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=49326062.6000800@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox