From: Lawrence Gold <gold@shell.aros.net>
To: linux-kernel@vger.kernel.org
Subject: Success using "Athlon bug stomper" on VIA motherboard
Date: Sun, 30 Sep 2001 22:44:27 -0600 [thread overview]
Message-ID: <20010930224427.A42360@shell.aros.net> (raw)
The patch posted here
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0109.1/0817.html
allows my Epox 8kta3 motherboard to run 2.4.10 with Athlon optimizations.
Without this patch, I get immediate oopses on startup. For those who are
curious, it's a Duron 800 and the BIOS is the revision from 18 May 2001.
P.S. Some more information in case it's helpful to anyone:
I used to use this motherboard with my 1.2GHz Athlon. If I used an Athlon
kernel with CONFIG_X86_USE_3DNOW disabled, it would run well most of the
time. However, certain operations, such as rapidly skipping through an
mpeg in MPlayer, could cause an oops. Replacing my PC133 ram with PC166
seemed to have cleared up most of the oopses, but there were occasional
problems such as sig11 errors when running two compile jobs and playing an
mpeg.
I wonder if the PCI fixup could affect these problems as well.
Anyhow, good detective work! IMHO, it should at least make its way in as
an experimental config option.
reply other threads:[~2001-10-01 4:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010930224427.A42360@shell.aros.net \
--to=gold@shell.aros.net \
--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