From: Ross Vandegrift <ross@willow.seitz.com>
To: linux-kernel@vger.kernel.org
Subject: FPU emulation problems in 2.4
Date: Tue, 24 Jul 2001 17:23:40 -0400 [thread overview]
Message-ID: <20010724172340.A476@willow.seitz.com> (raw)
Hello everyone,
In my quest to get 2.4 and netfilter running on my machines
I have been having tons of problems on some [34]86sx machines that
we use. On all of them the kernel freezes hard right after saying
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 196k freed
No keyboard, no SysRq, need a hard reset. I also tried this on an
AMD K6-2. With hardware FPU it works fine, but loading with no387
gives an error:
FPU Emulator: Unknown prefix byte 0x00, probably due to
FPU Emulator: self-modifying code! (emulation impossible)
FPU Emulator: Internet error type 0x0126
At 00000023:0286
SW: b=1 st=0 es=1 sf=1 cc=0010 ef=111111
CW: ic=0 rc=00 pc=11 iem=0 ef=111111
Searching the archives showed a bug report against 2.1.5 that said
basically the same thing. Unfortunately there were no more messages
in the thread.
Ross Vandegrift
coolio@tmbg.org
ross@willow.seitz.com
reply other threads:[~2001-07-24 21:23 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=20010724172340.A476@willow.seitz.com \
--to=ross@willow.seitz.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