From: Jeff Dike <jdike@addtoit.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] testing of 2.6.15-rc1+patches and 2.6.15-rc3 x86 guests on amd64 host
Date: Tue, 29 Nov 2005 23:01:14 -0500 [thread overview]
Message-ID: <20051130040114.GB21268@ccure.user-mode-linux.org> (raw)
In-Reply-To: <1133307314.13162.50.camel@localhost.localdomain>
On Tue, Nov 29, 2005 at 11:35:14PM +0000, Antoine Martin wrote:
> [42951313.910000] Kernel panic - not syncing: Kernel mode signal 7
Did your /tmp fill up?
> * Now, with 2.6.15-rc3 it does not boot:
> * or in skas0 mode:
> Checking PROT_EXEC mmap in /tmp...OK
> Checking for the skas3 patch in the host:
> - /proc/mm...not found
> - PTRACE_FAULTINFO...not found
> - PTRACE_LDT...not found
> UML running in SKAS0 mode
> (then it exits)
With SIGBUS happening, I'd check that you've got some space in /tmp.
FWIW, I have rc3 running happily here on x86_64.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-30 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 23:35 [uml-devel] testing of 2.6.15-rc1+patches and 2.6.15-rc3 x86 guests on amd64 host Antoine Martin
2005-11-30 4:01 ` Jeff Dike [this message]
2005-12-08 2:24 ` Antoine Martin
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=20051130040114.GB21268@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=antoine@nagafix.co.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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