From: Tejun Heo <htejun@gmail.com>
To: Vasily Averin <vvs@sw.ru>
Cc: albertl@mail.com, Jeff Garzik <jgarzik@pobox.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
devel@openvz.org
Subject: Re: unexpected scsi timeout
Date: Wed, 25 Jul 2007 16:42:37 +0900 [thread overview]
Message-ID: <46A6FEED.2050403@gmail.com> (raw)
In-Reply-To: <46A6FD8E.7090803@sw.ru>
Vasily Averin wrote:
> Albert Lee wrote:
>>>> Vasily Averin wrote:
>>>>> I've noticed that some scsi commands for DVD-drive attached to pata_via
>>>>> successfully finishes without any delays but reports about TIMEOUT condition. It
>>>>> happens because of ATA_ERR bit is set in status register. As result for each
>>>>> command Error Handler thread awakened, requests sense buffer and go to sleep again.
>>>> Need more info. Please post boot dmesg and the result of 'lspci -nn'
>>>> and 'hdparm -I /dev/srX' and when such errors occur.
>> Your log looks ok. It's normal for TEST_UNIT_READY to return ATA_ERR when no disc
>> inside and libata EH triggered to request sense.
>
> It's a bit strange for me, IMHO other scsi drivers requests sense buffer without
> EH thread assistance.
> Currently we know that ATA_ERR can be returned; it is not error, but one of
> expected responses. Why we cannot request sense without EH? I would like to
> understand is it implementation drawback or I missed something probably?
That was a design choice. It's easier to implement that way.
--
tejun
next prev parent reply other threads:[~2007-07-25 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 12:02 unexpected scsi timeout Vasily Averin
2007-07-24 8:20 ` Tejun Heo
2007-07-24 10:07 ` Vasily Averin
2007-07-25 5:50 ` Albert Lee
2007-07-25 7:36 ` Vasily Averin
2007-07-25 7:42 ` Tejun Heo [this message]
2007-07-25 13:06 ` James Bottomley
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=46A6FEED.2050403@gmail.com \
--to=htejun@gmail.com \
--cc=albertl@mail.com \
--cc=devel@openvz.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vvs@sw.ru \
/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;
as well as URLs for NNTP newsgroup(s).