From: Oliver Bausinger <bausi@bausi.org>
To: linux-ide@vger.kernel.org
Subject: Re: sata_sil problems (lockup at boottime)
Date: Tue, 7 Dec 2004 09:40:30 +0100 [thread overview]
Message-ID: <200412070940.30361.bausi@bausi.org> (raw)
In-Reply-To: <41B4DA37.5060209@nv-systems.net>
Am Montag 06 Dezember 2004 23:16 schrieb Gerald Hopf:
>
> I also tried the depreciated siimage driver (thanks to the
> CONFIG_BLK_DEV_IDE_SATA tip, i didn't notice this before and had the
> same problems) with kernel 2.6.9,
> works flawless (as far as i can tell from such a short test, hdparm -t =
> 60MB/s). No strange IRQ disabled errors during bootup. Flawless of
> course only if you ignore that it takes AGES until it finally gives up
> probing the second SATA port. I know someone who bought a second SATA
> harddrive just because booting took so long!
>
After some tests, I'm quite sure that the siimage is broken too with this
drive although it boots and works like Gerald describes.
When md5sum a file, read bigger amounts of data from the disk and
md5sum it again, the checksum changed. I can reproduce this permanently with a
number of files.
When I e2fsck the partition, I get bitmap differences. There's an error at
bootup which says something about a Drive Error when booting. I'll post the
exact error when I get back to the machine.
Greetings
Bausi
prev parent reply other threads:[~2004-12-07 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 23:34 sata_sil problems (lockup at boottime) Gerald Hopf
2004-12-05 8:08 ` Oliver Bausinger
2004-12-05 14:15 ` siimage annoyance (was: ata_sil problems (lockup at boottime)) Oliver Bausinger
2004-12-05 16:10 ` sata_sil problems (lockup at boottime) Bartlomiej Zolnierkiewicz
2004-12-05 16:38 ` Oliver Bausinger
2004-12-06 22:16 ` Gerald Hopf
2004-12-07 8:40 ` Oliver Bausinger [this message]
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=200412070940.30361.bausi@bausi.org \
--to=bausi@bausi.org \
--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).