From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: James Bottomley <James.Bottomley@SteelEye.com>,
linux1394-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org
Cc: Ben Collins <bcollins@debian.org>
Subject: Re: infinite loop with 36 Byte inquiry (sbp2 regression in 2.6.14-rcX)
Date: Mon, 24 Oct 2005 21:05:16 +0200 [thread overview]
Message-ID: <435D306C.20202@s5r6.in-berlin.de> (raw)
In-Reply-To: <1130167914.3325.27.camel@mulgrave>
James Bottomley wrote:
> Like I said, I think that's because you send an orb to the device with a
> command indicated length of 36 but a buffer length of 37
It happens regardless of what I force sbp2_send_command() to do:
request_bufflen = cmd[4] = 0x24;
or
request_bufflen = cmd[4];
or none of that.
> I don't see any loops in the lun probing routines. For UNIT_ATTENTION
> to inquiry, we should retry three times and then give up. If you enable
> debugging at the SCSI layer, that might give a better indication of
> what's going on.
Yes, I will do so.
> There's an #if 0 around an incorrect piece of code that would return
> DID_BUS_BUSY in this condition, you don't have that enabled, do you?
>
> DID_BUS_BUSY is a dangerous reply because it causes an immediate retry
> without decrementing the retry count. If you return it for a condition
> that never clears, it used to cause a hang. Now it should actually exit
> the loop after the command times out (6 seconds, I think).
The #if 0 block is still deactivated here.
Thanks a lot for the advice. I will post what I find out.
--
Stefan Richter
-=====-=-=-= =-=- ==---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2005-10-24 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 0:33 infinite loop with 36 Byte inquiry (sbp2 regression in 2.6.14-rcX) Stefan Richter
2005-10-23 7:46 ` Stefan Richter
2005-10-23 22:43 ` James Bottomley
2005-10-24 6:58 ` Stefan Richter
2005-10-24 15:31 ` James Bottomley
2005-10-24 19:05 ` Stefan Richter [this message]
2005-10-24 7:17 ` Stefan Richter
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=435D306C.20202@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@SteelEye.com \
--cc=bcollins@debian.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