From: Mark Lord <lkml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: auxsvr@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: ata command timeout
Date: Tue, 20 Feb 2007 10:18:35 -0500 [thread overview]
Message-ID: <45DB114B.4020903@rtr.ca> (raw)
In-Reply-To: <45DA7416.4040101@gmail.com>
Tejun Heo wrote:
> auxsvr@gmail.com wrote:
..
>> ata1: command timeout
>> Feb 19 20:39:31 linux kernel: ata1: no sense translation for status: 0x40
>> Feb 19 20:39:31 linux kernel: ata1: translated ATA stat/err 0x40/00 to SCSI
>> SK/ASC/ASCQ 0xb/00/00
>> Feb 19 20:39:31 linux kernel: ata1: status=0x40 { DriveReady }
>> Feb 19 20:39:31 linux kernel: sd 0:0:0:0: SCSI error: return code = 0x08000002
>> Feb 19 20:39:31 linux kernel: sda: Current: sense key: Aborted Command
>> Feb 19 20:39:31 linux kernel: Additional sense: No additional sense
>> information
>> Feb 19 20:39:31 linux kernel: end_request: I/O error, dev sda, sector 89553479
>>
>> without any other ill-effects that I know of(I did smart tests on the drive;
>> all passed successfully).
>> I have read that hddtemp may be the cause of this (I am running version 0.3)
>> so is there any reason
>> to worry and prepare for a HDD replacement?
>
> Not really. If the problem occurs very infrequently, you don't need to
> worry about it too much. Command timeouts do occur on otherwise healthy
> systems from time to time.
I don't believe that. Command timeouts never happen on healthy systems,
unless we have a driver bug. Okay, so I can imagine a pathological case
of a full queue (NCQ) with all 32 commands taking longer than usual due
to ECC retries in the firmware..
But in real life, on a desktop, timeouts never happen as a normal event.
I wonder what's *really* wrong here?
Cheers
next prev parent reply other threads:[~2007-02-20 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 19:19 auxsvr
2007-02-20 4:07 ` Tejun Heo
2007-02-20 4:37 ` Marc Marais
2007-02-20 15:18 ` Mark Lord [this message]
2007-02-20 15:37 ` Jeff Garzik
2007-02-21 7:03 ` Tejun Heo
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=45DB114B.4020903@rtr.ca \
--to=lkml@rtr.ca \
--cc=auxsvr@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome