From: Jeff Dike <jdike@addtoit.com>
To: Andi Kleen <ak@muc.de>
Cc: Antoine Martin <antoine@nagafix.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11.8 + UML/x86_64 (2.6.12-rc3+) = oops
Date: Sun, 8 May 2005 12:38:53 -0400 [thread overview]
Message-ID: <20050508163853.GB25130@ccure.user-mode-linux.org> (raw)
In-Reply-To: <m1ekchvmb0.fsf@muc.de>
> Are you sure you did not apply any strange UML related patches
> to the host kernel? Maybe those are buggy.
No, stock x86_64 kernel is horribly unstable running UML. I haven't seen
anything but output-free hangs, so I haven't had much information to
contribute. Antoine is actually getting capturable oopses.
I've tried every recent FC3 kernel, plus stock 2.6.10, and none of them
survive very long with UML running. Haven't tried stock 2.6.11 or anything
later yet.
Jeff
prev parent reply other threads:[~2005-05-08 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050504191828.620C812EE7@sc8-sf-spam2.sourceforge.net>
[not found] ` <1115248927.12088.52.camel@cobra>
[not found] ` <1115392141.12197.3.camel@cobra>
2005-05-07 16:31 ` 2.6.11.8 + UML/x86_64 (2.6.12-rc3+) = oops Antoine Martin
2005-05-07 15:57 ` Alexander Nyberg
2005-05-07 18:03 ` Jeff Dike
2005-05-08 0:18 ` Al Viro
2005-05-08 6:10 ` Al Viro
2005-05-09 21:07 ` Al Viro
2005-05-10 2:26 ` Al Viro
2005-05-10 3:50 ` Jeff Dike
2005-05-10 10:02 ` Al Viro
2005-05-08 16:28 ` Jeff Dike
2005-05-07 18:06 ` Antoine Martin
2005-05-08 14:12 ` Andi Kleen
2005-05-08 16:35 ` Antoine Martin
2005-05-08 15:15 ` Andi Kleen
2005-05-08 16:42 ` Jeff Dike
2005-05-08 17:38 ` Antoine Martin
2005-05-08 16:45 ` Jeff Dike
2005-05-08 19:51 ` Antoine Martin
2005-05-08 16:38 ` Jeff Dike [this message]
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=20050508163853.GB25130@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=ak@muc.de \
--cc=antoine@nagafix.co.uk \
--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