From: Ron Flory <ron.flory@adtran.com>
To: "Dr. Kelsey Hudson" <kernel@blackhole.compendium-tech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is this a bug?
Date: Wed, 08 Aug 2001 07:59:33 -0500 [thread overview]
Message-ID: <3B7137B5.71C35982@adtran.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108071916100.23797-100000@sol.compendium-tech.com>
"Dr. Kelsey Hudson" wrote:
>
> On Tue, 7 Aug 2001, Thodoris Pitikaris wrote:
>
> > As you will see in the attached file (it's a dmesg from the boot)
> > I have an 1Ghz athlon cpu with a VIA KT133 on a gigabyte GA-7ZX
> > motherboard with 100mhz SDRAM.When I compiled the kernel with
> > cputype=Athlon I continiusly experienced this crash.When I compiled with
> > cputype=i686 everything went smooth (OS is Redhat 7.1)
>
> It's a bug in that screwed up compiler redhat shipped with 7.1. AFAIK, the
> only difference between an athlon-specific kernel and an i686-specific
> kernel are the options in the compiler command line when compiling the
> kernel.
RH has posted updates to many of the gcc-xxx tools, have you installed
the updated compilers and libraries ?
ron
next prev parent reply other threads:[~2001-08-08 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 11:51 is this a bug? Thodoris Pitikaris
2001-08-07 13:51 ` Andrzej Krzysztofowicz
2001-08-08 2:19 ` Dr. Kelsey Hudson
2001-08-08 3:15 ` J Sloan
2001-08-08 3:45 ` Dr. Kelsey Hudson
2001-08-08 10:53 ` David Weinehall
2001-08-08 11:05 ` Alan Cox
2001-08-08 12:59 ` Ron Flory [this message]
2001-08-08 16:51 ` jury gerold
2001-08-10 9:12 ` Eric W. Biederman
2001-08-10 12:22 ` jury gerold
2001-08-10 16:22 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2011-03-24 0:46 Jay
2011-03-25 15:18 ` Steven Rostedt
2017-06-21 3:08 Is " Peter Teoh
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=3B7137B5.71C35982@adtran.com \
--to=ron.flory@adtran.com \
--cc=kernel@blackhole.compendium-tech.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