From: Mikael Pettersson <mikpe@csd.uu.se>
To: ak@muc.de
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: [BUG] 2.4.22-rc3 broke x86-64 ia32 emulation?
Date: Sun, 24 Aug 2003 14:11:52 +0200 (MEST) [thread overview]
Message-ID: <200308241211.h7OCBq7T014859@harpo.it.uu.se> (raw)
2.4.22-rc3 appears to have broken x86-64's ia32-emulation.
Now, whenever I run a 32-bit binary I get general protection
and a core dump:
strace32[371] general protection rip:4000e8fb rsp:ffffd8bc error:400
strace32[374] general protection rip:4000e8fb rsp:ffffd8ec error:400
lilo[376] general protection rip:4000e8fb rsp:ffffd8ec error:400
self[383] general protection rip:4000e8fb rsp:ffffd8ec error:400
2.4.22-rc2 and 2.6.0-test4 work fine.
My user-space is GinGin64 (RH 8.0.95 for x86-64) with 32-bit glibc
and lilo from RH8.0. 'strace32' above is a copy of RH9's strace;
I tried it since I could never get the 64-bit strace to work with
32-bit binaries.
/Mikael
reply other threads:[~2003-08-24 12:12 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=200308241211.h7OCBq7T014859@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--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;
as well as URLs for NNTP newsgroup(s).