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.14/2.6.15-rc amd64 guests
Date: Tue, 29 Nov 2005 23:04:09 -0500 [thread overview]
Message-ID: <20051130040409.GC21268@ccure.user-mode-linux.org> (raw)
In-Reply-To: <1133311286.13162.74.camel@localhost.localdomain>
On Wed, Nov 30, 2005 at 12:41:26AM +0000, Antoine Martin wrote:
> * The same kernel compiled here using hardened GCC:
> gcc (GCC) 3.4.4 (Gentoo Hardened 3.4.4-r1, HTB-3.4.4-1.00, ssp-3.4.4-1.0, pie-8.7.8)
> gives the same error reported earlier for x86 guests:
> the guest exits after spinning for a while on signals:
> rt_sigprocmask(SIG_SETMASK, NULL, [WINCH], 8) = 0
> rt_sigprocmask(SIG_BLOCK, [ALRM VTALRM IO], NULL, 8) = 0
> rt_sigprocmask(SIG_UNBLOCK, [ALRM VTALRM IO], [ALRM VTALRM WINCH IO], 8) = 0
> rt_sigprocmask(SIG_BLOCK, [], NULL, 8) = 0
> (that's in skas mode)
Can you gdb the thing and get a stack trace from the SIGBUS (I'm guessing this
is the same thing as the previous message where you had a strace log showing
SIGBUS happening)?
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
prev parent reply other threads:[~2005-11-30 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 0:41 [uml-devel] testing of 2.6.14/2.6.15-rc amd64 guests Antoine Martin
2005-11-30 4:04 ` 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=20051130040409.GC21268@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 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.