From: MisterE <MisterE2002@zonnet.nl>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
benh@kernel.crashing.org
Subject: Re[2]: Sata Sil3512 bug?
Date: Tue, 2 Oct 2007 21:20:23 +0200 [thread overview]
Message-ID: <1128907118.20071002212023@zonnet.nl> (raw)
In-Reply-To: <46FD3213.6050204@gmail.com>
Hello Tejun,
I build another setup with almost the same hardware.
This motherboard had already the latest bios.
I notice that the computer does almost never find the hard drive
although the controller is found every time (with lspci). So i get no
drive (sda) assigned. I don't always see the "bios" screen from the
controller at startup. And in the past it showed the hard drive.
So i could not experiment with this motherboard.
After that i installed Windows XP and used the orginal (sweex)
drivers with the first motherboard. This also makes the data corrupt.
So it seems not to be an linux problem. So there is something wrong with
the motherboard or the 3512 controller.
After that i plugged both hard drives (ide with windows and sata disk)
to the Asus board. No data corruption. So the hard disks are'nt the
problem either.
I'm thinking of replacing both 3512 controllers with a Promise SATA300
TX4. Do you know if there are problems with this device?
Friday, September 28, 2007, 6:55:47 PM, you wrote:
> Alan Cox wrote:
>>> sda1 are corrupted (2 to 4 blocks missing). Copying that data back to
>>> Windows and it give the same results in Quickpar. So reading does not
>>> have problems. The data written to hda1 is correct.
>>
>> We've got a whole pile of reports like this with the 3512 and almost
>> always Nvidia chipset, plus reports of BIOS updates fixing it. That you
>> see something similar on intel boards is a bit worrying.
> Multiple sil3112/3512 + nvidia chipset problem doesn't usually involve
> device errors or timeouts. It usually corrupts data silently. And,
> yeah, data corruption on intel board is really disturbing.
> MisterE, do you have any processor powersaving mechanism enabled? If
> so, can you disable all and see whether that changes anything?
--
Best regards,
MisterE mailto:MisterE2002@zonnet.nl
next prev parent reply other threads:[~2007-10-02 19:17 UTC|newest]
Thread overview: 13+ 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 ` MisterE [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 7:26 Re[2]: " Mikael Pettersson
2007-10-03 8:31 ` Alexander Sabourenkov
2007-10-03 14:45 ` Re[2]: " MisterE
2007-10-14 12:07 ` MisterE
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=1128907118.20071002212023@zonnet.nl \
--to=mistere2002@zonnet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=htejun@gmail.com \
--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).