From: Tejun Heo <htejun@gmail.com>
To: Jon Chelton <jchelton@ffpglobal.com>
Cc: linux-ide@vger.kernel.org, Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: sata_sil24 with port multiplier
Date: Fri, 28 Sep 2007 14:48:09 -0700 [thread overview]
Message-ID: <46FD7699.9010404@gmail.com> (raw)
In-Reply-To: <FD6311B7ED175B4480F31633F6098B4D911D1F@ffpglobal_mail.corp.ffplus.net>
Jon Chelton wrote:
> Tejun,
>
> Below is the kernel log from boot to when error occurred. You can see
> right when the raid5 array was built and started the recovery process
> the exception occurred. Also, its now been 24 hours since I disabled
> smartd and have not seen any other exceptions since. (also included is
> output from smartd -V)
[--snip--]
> ata1.03: exception Emask 0x0 SAct 0x2220897f SErr 0x400000 action 0x2
> ata1.03: irq_stat 0x00020002, device error via SDB FIS
> ata1.03: cmd 61/88:a8:3f:00:00/00:00:00:00:00/40 tag 21 cdb 0x0 data
> 69632 out
> res 41/84:38:8f:00:00/60:00:00:00:00/40 Emask 0x410 (ATA bus
> error) <F>
> ata1.03: soft resetting link
> ata1.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.03: configured for UDMA/100
> ata1: EH complete
> ata1.03: exception Emask 0x0 SAct 0x1ffc SErr 0x400000 action 0x2
> ata1.03: irq_stat 0x00020002, device error via SDB FIS
> ata1.03: cmd 61/88:10:3f:00:00/00:00:00:00:00/40 tag 2 cdb 0x0 data
> 69632 out
> res 41/84:78:4f:00:00/00:00:00:00:00/40 Emask 0x410 (ATA bus
> error) <F>
> ata1.03: soft resetting link
> ata1.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.03: configured for UDMA/100
> ata1: EH complete
> ata1.03: exception Emask 0x0 SAct 0x7ff SErr 0x400000 action 0x2
> ata1.03: irq_stat 0x00020002, device error via SDB FIS
> ata1.03: cmd 61/70:00:57:03:00/01:00:00:00:00/40 tag 0 cdb 0x0 data
> 188416 out
> res 41/84:a0:27:04:00/60:00:00:00:00/40 Emask 0x410 (ATA bus
> error) <F>
> ata1.03: soft resetting link
> ata1.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.03: configured for UDMA/100
> ata1: EH complete
> ata1.03: limiting SATA link speed to 1.5 Gbps
> ata1.03: exception Emask 0x0 SAct 0x7ff SErr 0x400000 action 0x6
> ata1.03: irq_stat 0x00020002, device error via SDB FIS
> ata1.03: cmd 61/88:00:3f:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data
> 69632 out
> res 41/84:38:8f:00:00/00:00:00:00:00/40 Emask 0x410 (ATA bus
> error) <F>
> ata1.03: hard resetting link
> ata1.03: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.03: configured for UDMA/100
> ata1: EH complete
All errors are interface CRC errors reported by device on FPDMA_WRITE.
It doesn't seem to have anything to do with SMART. In all cases, SError
DIAG is reporting handshake error too (R_ERR received). I'm fairly sure
these were actual hardware problems. You don't have to pay too much
attention unless it happens repeatedly. Good cure for the problem is
probably to re-seat the harddrive.
Bruce, I don't think this is SMART related. Sorry about the noise. Thanks.
--
tejun
next prev parent reply other threads:[~2007-09-28 21:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 18:25 sata_sil24 with port multiplier Jon Chelton
2007-09-28 21:48 ` Tejun Heo [this message]
2007-09-29 4:47 ` Bruce Allen
-- strict thread matches above, loose matches on Subject: below --
2007-09-29 19:14 Jon Chelton
2007-10-02 12:07 ` Bruce Allen
2007-09-28 16:08 Jon Chelton
2007-09-28 16:51 ` Tejun Heo
2007-09-27 21:01 Jon Chelton
2007-09-28 10:24 ` Tejun Heo
2007-09-23 3:56 Jon Chelton
2007-09-23 3:34 Jon Chelton
2007-09-23 3:36 ` Tejun Heo
2007-09-22 0:00 Thomas Evans
2007-09-21 17:41 Jon Chelton
2007-09-23 3:25 ` Tejun Heo
[not found] <FD6311B7ED175B4480F31633F6098B4D911C41@ffpglobal_mail.corp.ffplus.net>
2007-09-21 10:55 ` 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=46FD7699.9010404@gmail.com \
--to=htejun@gmail.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=jchelton@ffpglobal.com \
--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).