From: Tejun Heo <htejun@gmail.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: linux-ide@vger.kernel.org, ballen@gravity.phys.uwm.edu
Subject: Re: 2.6.22.6 sata_sil device errors & timeouts
Date: Mon, 17 Sep 2007 19:07:21 +0200 [thread overview]
Message-ID: <46EEB449.8010305@gmail.com> (raw)
In-Reply-To: <76366b180709170904i7b2f5ab0o8605eb899d20f921@mail.gmail.com>
[cc'ing Bruce Allen]
Andrew Paprocki wrote:
> I didn't mention it before, but I'm also getting these errors every
> time I boot. I'm thinking they're related to the drive not supporting
> cmds that smartd is sending it. If so, is there any way that
> libata/smartd can handle this more gracefully? This stuff spews into
> dmesg and gives a scare that there is a real hardware problem that may
> cause data corruption. I get exactly 6 instances of each of these two
> blocks of output prior to reaching the login prompt:
>
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
> res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> ata1.00: configured for UDMA/100
> ata1: EH complete
>
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
> res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> ata2.00: configured for UDMA/100
> ata2: EH complete
Upgrading smartd should fix it. Which version are you using?
--
tejun
next prev parent reply other threads:[~2007-09-17 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 8:35 2.6.22.6 sata_sil device errors & timeouts Andrew Paprocki
2007-09-17 9:18 ` Tejun Heo
2007-09-17 16:04 ` Andrew Paprocki
2007-09-17 17:07 ` Tejun Heo [this message]
2007-09-17 19:05 ` Andrew Paprocki
2007-09-17 19:26 ` Andrew Paprocki
2007-09-17 19:35 ` Bruce Allen
2007-09-17 21:06 ` Andrew Paprocki
2007-09-18 5:29 ` Bruce Allen
2007-09-18 14:36 ` Andrew Paprocki
2007-09-18 15:34 ` Bruce Allen
2007-09-27 7:15 ` Tejun Heo
2007-09-28 3:59 ` Bruce Allen
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=46EEB449.8010305@gmail.com \
--to=htejun@gmail.com \
--cc=andrew@ishiboo.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).