From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}
Date: Mon, 1 Jan 2007 19:13:29 +0000 [thread overview]
Message-ID: <20070101191329.GA29826@deepthought> (raw)
In-Reply-To: <20070101170758.GA28015@deepthought>
On Mon, Jan 01, 2007 at 05:07:58PM +0000, Ken Moffat wrote:
> On Mon, Jan 01, 2007 at 04:48:55PM +0000, Alistair John Strachan wrote:
> >
> > Obviously papering over a severe bug, but why is it necessary for you to run a
> > 32bit kernel to test 32bit userspace? If your 64bit kernel is stable, use the
> > IA32 emulation surely?
> >
> My 64-bit is pure64 on this machine, so it doesn't have any
> suitable libs or tools. Anyway, I really do need a 32-bit kernel
> to test some linuxfromscratch build instructions.
>
Sorry, I think last night is still interfering with my own logic
circuits. Yes, I could use 'linux32' to change the personality as a
work-around now that I've built the system. Mainly, I was hoping
somebody would notice something bad in the config, but I might use
the work-around in the meantime. Thanks for reminding me about it.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2007-01-01 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 16:01 x86 instability with 2.6.1{8,9} Ken Moffat
2007-01-01 16:48 ` Alistair John Strachan
2007-01-01 17:07 ` Ken Moffat
2007-01-01 19:13 ` Ken Moffat [this message]
2007-01-01 19:45 ` Alistair John Strachan
2007-01-02 17:25 ` Len Brown
2007-01-02 18:04 ` Ken Moffat
2007-01-02 18:42 ` Len Brown
2007-01-02 19:34 ` Ken Moffat
2007-01-06 22:04 ` Randy Dunlap
2007-01-07 14:26 ` Ken Moffat
2007-01-15 16:29 ` Ken Moffat
2007-01-25 23:56 ` Ken Moffat
2007-01-31 21:36 ` Chuck Ebbert
2007-01-31 23:26 ` Ken Moffat
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=20070101191329.GA29826@deepthought \
--to=zarniwhoop@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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