From: Tejun Heo <htejun@gmail.com>
To: MisterE <MisterE2002@zonnet.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
benh@kernel.crashing.org
Subject: Re: Sata Sil3512 bug?
Date: Thu, 18 Oct 2007 12:29:48 +0900 [thread overview]
Message-ID: <4716D32C.5090408@gmail.com> (raw)
In-Reply-To: <193014791.20071013183617@zonnet.nl>
MisterE wrote:
> Oct 13 13:01:26 fileserver kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
> Oct 13 13:01:26 fileserver kernel: ata4.00: (BMDMA2 stat 0x650001)
> Oct 13 13:01:26 fileserver kernel: ata4.00: cmd ca/00:f8:47:e1:5e/00:00:00:00:00/e4 tag 0 cdb 0x0 data 126976 out
> Oct 13 13:01:26 fileserver kernel: res 51/04:98:a7:e1:5e/00:00:00:00:00/e4 Emask 0x1 (device error)
> Oct 13 13:01:26 fileserver kernel: ata4.00: configured for UDMA/100
> Oct 13 13:01:26 fileserver kernel: ata4: EH complete
> Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
> Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off
> Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
> Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> I'm not sure if it will result in corrupt data? But i don't trust it
> anymore.
That looks like a data transmission error. When you're transferring
massive amount of data, things like that can happen and it won't cause
data corruption.
> You people advise me to not buy the Promise SATA300 TX4 controller and
> this Sweex PU102 (3512) seems to have problems. Not much choices left
> except the really expensive solutions.
>
> Is it really so hard to build a controller without problems?!? :(
It seems so. :-(
--
tejun
next prev parent reply other threads:[~2007-10-18 3:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 13:51 Sata Sil3512 bug? MisterE
2007-09-28 12:25 ` Tejun Heo
2007-09-28 15:25 ` Re[2]: " MisterE
2007-09-28 15:51 ` Alan Cox
2007-09-28 16:55 ` Tejun Heo
2007-10-02 19:20 ` Re[2]: " MisterE
2007-10-04 1:27 ` Tejun Heo
2007-10-04 19:03 ` Re[2]: " MisterE
2007-10-13 16:36 ` MisterE
2007-10-18 3:29 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 7:26 Mikael Pettersson
2007-10-03 8:31 ` Alexander Sabourenkov
2007-10-03 14:45 ` Re[2]: " MisterE
2007-10-03 14:50 ` Alan Cox
2007-10-14 12:07 ` Re[2]: " MisterE
2007-10-15 8:44 ` Alexander Sabourenkov
2007-10-04 0:46 Richard Scobie
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=4716D32C.5090408@gmail.com \
--to=htejun@gmail.com \
--cc=MisterE2002@zonnet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.