From: "Nicholas Knight" <tegeran@home.com>
To: <linux-kernel@vger.kernel.org>
Subject: VT82C686A corruption with 2.4.x
Date: Tue, 30 Jan 2001 05:40:32 -0800 [thread overview]
Message-ID: <03b101c08ac2$377e3380$8d19b018@c779218a> (raw)
I have a Soyo K7VIA motherboard which uses VT82C686A, with an 800mhz Athlon
CPU in it.
So far I've never run a 2.3* or 2.4* kernel on it, I've only done that on my
P3 using a propriatory micron motherboard that uses an intel BX2 chipset.
However, I recently trashed my linux installation (doing things totaly
unrelated to the kernel) and now would be more than happy to assist in
trying to figure out what the heck is causing the filesystem corruption on
VIA chipsets, but so far I've only found bits and peices of information on
it, and have been unable to locate a compiliation of information avalible on
the problem, so I'd know just where to start.
If anyone could point me to a good place to start looking, besides the
thousands of messages containing just bits and peices of information, I
could get to work on some testing.
-NK
-
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 reply other threads:[~2001-01-30 13:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 13:40 Nicholas Knight [this message]
2001-01-30 15:03 ` VT82C686A corruption with 2.4.x Tobias Ringstrom
2001-01-30 19:51 ` David D.W. Downey
2001-01-30 20:53 ` David Raufeisen
[not found] <Pine.LNX.4.10.10101301743180.30535-100000@coffee.psychology.mcmaster.ca>
2001-01-31 1:18 ` David D.W. Downey
2001-01-31 2:04 ` David D.W. Downey
2001-01-31 7:36 ` Vojtech Pavlik
2001-01-31 7:55 ` David Raufeisen
2001-01-31 9:48 ` safemode
2001-01-31 11:43 ` Vojtech Pavlik
2001-01-31 12:54 ` Mark Hahn
2001-01-31 19:58 ` David Riley
2001-02-01 12:51 ` David D.W. Downey
2001-01-31 20:01 ` safemode
2001-01-31 22:04 ` Tobias Ringstrom
2001-01-31 22:40 ` safemode
2001-01-31 22:46 ` Alan Cox
2001-01-31 22:57 ` safemode
2001-02-01 6:31 ` Vojtech Pavlik
2001-02-01 0:46 ` Byron Stanoszek
2001-02-01 1:52 ` safemode
2001-02-01 6:52 ` Vojtech Pavlik
2001-02-01 11:32 ` safemode
2001-02-01 16:46 ` Byron Stanoszek
2001-02-01 18:06 ` Vojtech Pavlik
2001-02-01 18:20 ` Byron Stanoszek
2001-02-01 20:51 ` Vojtech Pavlik
2001-02-01 21:51 ` safemode
2001-02-01 21:56 ` Alan Chandler
2001-02-01 6:39 ` Vojtech Pavlik
2001-01-31 11:39 ` Vojtech Pavlik
2001-01-31 15:41 ` David D.W. Downey
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='03b101c08ac2$377e3380$8d19b018@c779218a' \
--to=tegeran@home.com \
--cc=linux-kernel@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