From: Mike Anderson <andmike@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-scsi@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] instrument ide-scsi in 2.5.68
Date: Mon, 5 May 2003 01:46:17 -0700 [thread overview]
Message-ID: <20030505084617.GG8416@beaverton.ibm.com> (raw)
In-Reply-To: <3EB385F3.6010708@torque.net>
Douglas Gilbert [dougg@torque.net] wrote:
> The issued command is a MODE SENSE (10 byte) for page 0x2a
> and just the first 2 bytes (i.e. tell me the length you
> will return). There must have been 10 of the exact same
> commands executed successfully prior to this point.
>
> "hdd: lost interrupt" seems to indicate a timeout (ide-scsi
> sets its timeouts to max(10, whatever_app_wants) seconds).
> Then it re-enters the ide-scsi driver in the
> idescsi_pc_intr() routine and things look corrupted. It tries
> to finish off a DMA transfer but that 2 byte data_in request
> was not set up as DMA. It is all downhill from there.
>
> Naturally I don't see any errors on my box. However I can
> shorten the timeout so it will go off on a READ command.
> The timeout log looks quite different from yours and
> my driver continues in a healthy state.
>
> ide-scsi: hdd: que 11417, cmd = [ 28 0 0 0 0 0 0 0 1 0 ]
> hdd: irq timeout: status=0xd0 { Busy }
> hdd: ATAPI reset complete
> hdd: irq timeout: status=0xc0 { Busy }
> hdd: ATAPI reset complete
> hdd: irq timeout: status=0xc0 { Busy }
> ide-scsi: hdd: I/O error for 11417
>
>
> Does anyone have any suggestions for further testing?
>
It might be interesting if timeouts are happening to see what the error
handler is doing. If SCSI_LOGGING is config'd. Then
echo scsi log error 4 > /proc/scsi/scsi
should not be too verbose.
> I have cleaned up the logging messages a little but
> that does not justify releasing a new version yet.
>
>
> An additional observation concerning Randy's capture:
> the failed command (MODE SENSE) has serial number 91.
> After ide-scsi thinks it has cleared the timeout and
> the DMA transfer it issues a TEST UNIT READY which
> also get 91 as a serial number. This looks like a
> bug in the mid level.
>
Well ++serial_number and scsi_pid++ are not very safe, but is the TUR
coming from the error handler as it will have the same serial number
that the timed out command had. Alan Stern was asking about this in
another thread a few days ago.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-05-05 8:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 13:02 [PATCH] instrument ide-scsi in 2.5.68 Douglas Gilbert
2003-05-01 22:52 ` Randy.Dunlap
2003-05-01 22:57 ` Randy.Dunlap
2003-05-01 23:29 ` Douglas Gilbert
2003-05-01 23:44 ` Willem Riede
2003-05-02 0:38 ` Randy.Dunlap
2003-05-02 1:10 ` Douglas Gilbert
2003-05-02 8:40 ` Douglas Gilbert
2003-05-02 16:55 ` Randy.Dunlap
2003-05-03 9:03 ` Douglas Gilbert
2003-05-05 8:46 ` Mike Anderson [this message]
2003-05-05 16:57 ` Randy.Dunlap
2003-05-06 8:38 ` Douglas Gilbert
2003-05-06 14:39 ` Randy.Dunlap
2003-05-07 13:21 ` Douglas Gilbert
2003-05-07 18:16 ` Randy.Dunlap
2003-05-07 21:20 ` Randy.Dunlap
2003-05-08 0:00 ` Douglas Gilbert
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=20030505084617.GG8416@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox