From: Tejun Heo <htejun@gmail.com>
To: Florian Effenberger <florian@effenberger.org>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: libata interface fatal error
Date: Thu, 24 May 2007 15:45:55 +0200 [thread overview]
Message-ID: <46559713.9070201@gmail.com> (raw)
In-Reply-To: <4655923E.5000409@effenberger.org>
Hello,
Florian Effenberger wrote:
> We installed Debian Etch with the pre-compiled kernel, but when doing
> heavy SATA data transfer, the drives seem to make trouble. Even with the
> latest kernel, 2.6.21.2, we receive:
>
> ===
> ata3.00: exception Emask 0x10 SAct 0x1 SErr 0x400100 action 0x2 frozen
> ata3.00: (irq_stat 0x08000000, interface fatal error)
> ata3.00: cmd 61/80:00:00:91:91/00:00:1d:00:00/40 tag 0 cdb 0x0 data
> 65536 out
> res 40/00:04:00:91:91/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
> ata3: soft resetting port
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.00: configured for UDMA/133
> ata3: EH complete
> SCSI device sdc: 625142448 512-byte hdwr sectors (320073 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> ===
Looks like a genuine transmission/interface error to me. How often does
this occur? Please try to connect the drive to another port using and
possibly different power lane. Also, testing with another drive is a
good way to track down where the problem is.
> MD5 sums of copied files are right and we experience no other problems.
> Is this a driver bug? If so, can I be of any help in debugging it?
Yeah, libata EH is working properly so there shouldn't be any problem
other than the error messages and a bit slower transfer speed.
--
tejun
next prev parent reply other threads:[~2007-05-24 13:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 13:25 libata interface fatal error Florian Effenberger
2007-05-24 13:45 ` Tejun Heo [this message]
2007-05-24 14:08 ` Florian Effenberger
2007-05-24 14:21 ` Tejun Heo
2007-05-24 14:47 ` Florian Effenberger
2007-05-24 14:53 ` Tejun Heo
2007-05-24 15:28 ` Florian Effenberger
2007-05-24 14:55 ` Greg Freemyer
2007-05-24 14:59 ` Tejun Heo
2007-05-24 15:00 ` Florian Effenberger
-- strict thread matches above, loose matches on Subject: below --
2007-05-26 9:43 Florian Effenberger
2007-05-29 9:16 ` Tejun Heo
2007-05-29 14:16 ` Florian Effenberger
2007-06-06 21:23 ` Florian Effenberger
2007-06-07 9:50 ` Tejun Heo
2007-06-07 14:08 ` Florian Effenberger
2007-06-13 10:37 ` Florian Effenberger
2007-06-14 9:43 ` Tejun Heo
2007-06-14 11:12 ` Florian Effenberger
2007-06-14 12:25 ` Tejun Heo
2007-06-14 15:12 ` Florian Effenberger
2007-06-18 3:10 ` Tejun Heo
2007-06-18 6:08 ` Tomi Orava
2007-06-18 6:28 ` Tejun Heo
2007-06-18 10:38 ` Florian Effenberger
2007-06-18 10:44 ` Tejun Heo
2007-06-16 10:23 ` Florian Effenberger
2007-06-18 3:13 ` Tejun Heo
2007-06-18 10:44 ` Florian Effenberger
2007-06-18 10:56 ` Tejun Heo
2007-06-18 11:28 ` Florian Effenberger
2007-06-18 11:30 ` Tejun Heo
2007-06-18 11:32 ` Florian Effenberger
2007-06-24 11:32 ` Florian Effenberger
2007-06-25 2:49 ` Tejun Heo
2007-06-25 8:47 ` Florian Effenberger
2007-06-18 7:05 Mikael Pettersson
2007-06-18 7:13 ` Tejun Heo
2007-06-18 10:47 ` Florian Effenberger
2007-06-18 17:14 ` Ansgar Knappheide
2007-06-18 18:54 ` Tomi Orava
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=46559713.9070201@gmail.com \
--to=htejun@gmail.com \
--cc=florian@effenberger.org \
--cc=jgarzik@pobox.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).