From: Michael <leahcim@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [Oops] 2.4.5-ac14/2.4.6-pre3+Athlon+gcc3-prerelease+VIAKT133A
Date: Sat, 16 Jun 2001 19:29:57 +0100 [thread overview]
Message-ID: <20010616192957.A2713@debian> (raw)
In-Reply-To: <20010616161801.A1821@caesar>
In-Reply-To: <20010616161801.A1821@caesar>
On Sat, Jun 16, 2001 at 04:18:01PM +0800, Richard Chan wrote:
> Here's an oops from
>
> 1. Athlon kernel, gcc3 prerelease 14 June compiled
> 2. Kernel version 2.4.5-ac14
> 3. Mobo: Soltek 75KAV (VT133A disaster??) with Athlon 1.2G C
>
> Any ideas? Bad compiler or bad kernel?
> The problems occur in kmem_cache_????.
>
> On this mobo and chipset I have had no luck with locally compiled
> Athlon kernels at all (whether stock or -ac, RedHat gcc or gcc3-prerelease).
> Me thinks something is seriously wrong with this mobo/chipset or is it
> the Athlon code in gcc?
FWIW, I've got 2 of these boards (with duron 800 chips)
I use gcc2.95.4 in debian sid.
Got it about the same time the 686b patch went
into ac1 and its run flawlessly with every ac version I've used since.
Didn't compile ac14, went straight to 15.
--
Michael.
prev parent reply other threads:[~2001-06-16 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-16 8:18 [Oops] 2.4.5-ac14/2.4.6-pre3+Athlon+gcc3-prerelease+VIAKT133A Richard Chan
2001-06-16 18:29 ` Michael [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=20010616192957.A2713@debian \
--to=leahcim@ntlworld.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