From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: Parag Warudkar <kernel-stuff@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: RT patch breaks X86_64 build
Date: Fri, 03 Jun 2005 00:45:20 +0200 [thread overview]
Message-ID: <429F8C00.3070803@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20050602183343.GB30309@elte.hu>
Ingo Molnar wrote:
> hm, one difference is that i'm running a 64-bit kernel but 32-bit
> userspace (FC3-ish).
Yes, that's it! I've just successfully booted into 32-bit userspace (I
have a separate partition with old 32-bit Debian) with x86_64 kernel and
LATENCY_TRACE enabled. Everything seemed to work.
Then I mounted my normal root partition under /mnt/64 and tried
chroot /mnt/64
I got a SIGSEGV. Then I copied some simple binaries from /mnt/64/bin to
/root/test/bin and some necessary libraries to /root/test/lib and did
chroot /root/test
I could run 64-bit sash, ls, cat, date, mkdir - it worked. 64-bit bash
however segfaulted.
Michal
next prev parent reply other threads:[~2005-06-02 22:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 1:41 RT patch breaks X86_64 build Parag Warudkar
2005-05-31 2:01 ` Parag Warudkar
2005-05-31 6:08 ` Michal Schmidt
2005-05-31 11:53 ` Parag Warudkar
2005-05-31 12:05 ` Michal Schmidt
2005-06-01 9:13 ` Ingo Molnar
2005-06-02 12:28 ` Michal Schmidt
2005-06-02 12:39 ` Ingo Molnar
2005-06-02 14:13 ` Michal Schmidt
2005-06-02 15:55 ` Michal Schmidt
2005-06-02 16:17 ` Ingo Molnar
2005-06-02 16:37 ` Michal Schmidt
2005-06-02 18:04 ` Michal Schmidt
2005-06-02 18:33 ` Ingo Molnar
2005-06-02 22:45 ` Michal Schmidt [this message]
2005-06-03 5:18 ` Ingo Molnar
2005-06-03 11:03 ` Michal Schmidt
2005-06-02 12:31 ` Michal Schmidt
2005-06-02 12:37 ` Ingo Molnar
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=429F8C00.3070803@stud.feec.vutbr.cz \
--to=xschmi00@stud.feec.vutbr.cz \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.