From: Doug Ledford <dledford@redhat.com>
To: k.hindenburg@gte.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: __buggy_fxsr_alignment error 2.4.1 and 2.4.2
Date: Thu, 22 Feb 2001 23:14:44 -0500 [thread overview]
Message-ID: <3A95E3B4.9F6E8022@redhat.com> (raw)
In-Reply-To: <20010222224322.A15511@amdk7.gte.net>
"Kurt V. Hindenburg" wrote:
>
> asm-i386:
> init/main.o(.text.init+0x63): undefined reference to `__buggy_fxsr_alignment'
>
> I don't recall this error in 2.4.0, but it is present in 2.4.1 and was not
> fixed in 2.4.2.
>
> >sh scripts/ver_linux
> -- Versions installed: (if some fields are empty or look
> -- unusual then possibly you have very old versions)
> Linux amdk7 2.4.1 #3 Sat Feb 3 18:50:44 EST 2001 i686 unknown
> Kernel modules 2.4.1
> Gnu C pgcc-2.95.2.1
> Gnu Make 3.79.1
> Binutils 2.10.1
> Linux C Library 2.1.3
> Dynamic linker ldd: version 1.9.9
> Procps 2.0.7
> Mount 2.10q
> Net-tools 1.57
> Console-tools 0.2.3
> Sh-utils 2.0
> Modules Loaded ppp_deflate bsd_comp ppp_async
>
> Fix: Comment out line 217 in include/asm-i386/bugs.h
> /* __buggy_fxsr_alignment(); */
>
> It compiles after this change.
That "bug" is there for a reason. Get a real compiler, then it will work OK.
Compile that kernel with your compiler, your fix in place, and then try to run
it on a PIII or later CPU and it will Oops all over the place. Run it on any
CPU that supports FXSAVE and it will likely blow chunks (all the Intel CPUs
will, but I don't know for sure about the AMD CPUs that support FXSAVE).
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
next prev parent reply other threads:[~2001-02-23 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 3:43 PROBLEM: __buggy_fxsr_alignment error 2.4.1 and 2.4.2 Kurt V. Hindenburg
2001-02-23 4:14 ` Doug Ledford [this message]
2001-02-23 9:09 ` J . A . Magallon
[not found] <fa.f823oav.g0oe3a@ifi.uio.no>
2001-02-26 6:49 ` Marc D. Williams
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=3A95E3B4.9F6E8022@redhat.com \
--to=dledford@redhat.com \
--cc=k.hindenburg@gte.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