From: Vojtech Pavlik <vojtech@suse.cz>
To: Thomas Molina <tmolina@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: VIA IDE corruption - anyone experiencing it with 2.4.0?
Date: Sat, 13 Jan 2001 15:22:38 +0100 [thread overview]
Message-ID: <20010113152238.G1155@suse.cz> (raw)
In-Reply-To: <20010112212427.A2829@suse.cz> <Pine.LNX.4.30.0101130559060.19743-100000@wr5z.localdomain>
In-Reply-To: <Pine.LNX.4.30.0101130559060.19743-100000@wr5z.localdomain>; from tmolina@home.com on Sat, Jan 13, 2001 at 06:03:11AM -0600
On Sat, Jan 13, 2001 at 06:03:11AM -0600, Thomas Molina wrote:
> Are you looking for specific chipsets or configurations? Following is
> my VP3/MVP3 chipset lspci output if you are gathering a group of
> testers. I've enabled autoDMA at various points in the testing cycle
> (not consistently) but haven't noticed any fs corruption.
Ok. So what I'm exactly looking for:
Cases of harddrive corruption (that is, trashing your fs,
reading/writing bad data) on VIA chipsets. UDMA-caused CRC errors don't
fall into this category, they're harmless to the data.
Preferably with the driver from the 2.4.0 kernel. If possible, try also
the VIA 3.11 driver posted to the list earlier. If you don't have it, I
can e-mail it to you.
Don't use any hdparm command in your init scripts (this is important)
with the VIA driver and 2.4.0, setting the speed or dma usage with
hdparm would interfere with the driver autotuning.
If you fear to test, you can mount your fs readonly (no corruption can
happen) and use your swap partition for read-write test. You can even
mke2fs the swap for a while.
Anyone who experienced this kind of problems with 2.4 and the VIA
driver, please speak up, so I can fix it.
I'm not currently looking for success reports, I've already got success
reports for every type VIA IDE chip out there.
I'll need the motherboard type and revision, lspci -vvxxx, dmesg,
hdparm -i and /proc/ide/via listings ...
Thanks.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-13 18:28 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 8:44 ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-12 8:55 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-12 17:51 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-12 18:13 ` ide.2.4.1-p3.01112001.patch Alan Cox
2001-01-12 18:37 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-12 21:26 ` ide.2.4.1-p3.01112001.patch Adrian Bunk
2001-01-12 18:17 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-12 18:55 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-12 19:46 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-12 19:57 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-12 20:24 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-12 23:47 ` ide.2.4.1-p3.01112001.patch Alan Cox
2001-01-13 13:45 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-13 17:09 ` ide.2.4.1-p3.01112001.patch Bryan O'Sullivan
2001-01-13 17:19 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-13 0:09 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-13 0:25 ` ide.2.4.1-p3.01112001.patch Alan Cox
2001-01-12 16:43 ` ide.2.4.1-p3.01112001.patch John Heil
2001-01-13 0:52 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-12 17:09 ` ide.2.4.1-p3.01112001.patch John Heil
2001-01-13 1:16 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-15 10:15 ` ide.2.4.1-p3.01112001.patch Matthias Andree
2001-01-13 1:12 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-13 1:18 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-13 1:24 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-13 1:31 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-13 1:48 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-13 1:51 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-13 14:02 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-13 14:00 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-13 19:46 ` ide.2.4.1-p3.01112001.patch Alan Cox
2001-01-13 20:00 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-14 3:41 ` ide.2.4.1-p3.01112001.patch TimO
2001-01-14 8:55 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-15 13:06 ` ide.2.4.1-p3.01112001.patch Stephen Clark
[not found] ` <Pine.LNX.4.30.0101130559060.19743-100000@wr5z.localdomain>
2001-01-13 14:22 ` Vojtech Pavlik [this message]
2001-01-12 23:43 ` ide.2.4.1-p3.01112001.patch Alan Cox
2001-01-13 2:43 ` ide.2.4.1-p3.01112001.patch davej
2001-01-13 13:42 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-13 3:03 ` ide.2.4.1-p3.01112001.patch Tkil
2001-01-13 13:44 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-13 13:35 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-14 19:38 ` ide.2.4.1-p3.01112001.patch Jamie Lokier
2001-01-14 22:39 ` ide.2.4.1-p3.01112001.patch Vojtech Pavlik
2001-01-15 0:06 ` ide.2.4.1-p3.01112001.patch Albert Cranford
2001-01-15 23:47 ` ide.2.4.1-p3.01112001.patch Henrique de Moraes Holschuh
2001-01-15 1:13 ` ide.2.4.1-p3.01112001.patch Jamie Lokier
2001-01-13 22:06 ` ide.2.4.1-p3.01112001.patch junio
2001-01-13 7:12 ` ide.2.4.1-p3.01112001.patch Andre Hedrick
2001-01-13 16:42 ` ide.2.4.1-p3.01112001.patch David Woodhouse
2001-01-13 17:04 ` ide.2.4.1-p3.01112001.patch Linus Torvalds
2001-01-14 17:22 ` ide.2.4.1-p3.01112001.patch David Woodhouse
2001-01-13 18:54 ` ide.2.4.1-p3.01112001.patch Russell King
2001-01-12 8:56 ` ide.2.4.1-p3.01112001.patch Craig Schlenter
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=20010113152238.G1155@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@home.com \
/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