From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Pitcock <nenolod@dereferenced.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Crash with paravirt-ops 2.6.31.6 kernel
Date: Wed, 18 Nov 2009 09:45:18 -0500 [thread overview]
Message-ID: <20091118144518.GD15585@phenom.dumpdata.com> (raw)
In-Reply-To: <28846609.721258484676784.JavaMail.root@ifrit.dereferenced.org>
> [ 1.254927] init[1] general protection ip:f779042f sp:ff9b0340 error:0
That is what caused it. It would be of interest if you could disassemble init
and see what is the offending instruction (and around a couple of lines before it).
Use objdump for that purpose.
Also, please add these to your bootline to get more debug information (obviously
change your com1 and root line):
root (hd0,0)
kernel /xen-3.5-unstable.4.gz com1=115200,8n1,0xd800,0 console=com1,vga guest_loglvl=all loglvl=all sync_console console_to_ring dom0_mem=2GB
module /bzImage ro root=UUID=d6d08653-4a4f-4d41-87f2-f42fb7fe3ad5 initrd_ignore_loglevel sysrq_always_enable earlyprintk=xen console=tty console=hvc0 loglevel=10 debug
module /initrd-2.6.31-5.img
next prev parent reply other threads:[~2009-11-18 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 19:04 Crash with paravirt-ops 2.6.31.6 kernel William Pitcock
2009-11-18 14:45 ` Konrad Rzeszutek Wilk [this message]
2009-11-19 8:21 ` William Pitcock
2009-11-19 17:31 ` Konrad Rzeszutek Wilk
2009-11-20 4:12 ` Jeremy Fitzhardinge
2009-11-22 9:54 ` Bastian Blank
2009-11-23 15:25 ` Ian Campbell
2009-11-23 16:31 ` Bug#544145: [Xen-devel] " Bastian Blank
2009-11-23 16:42 ` Bug#544145: " Ian Campbell
2009-11-23 17:23 ` Bug#544145: [Xen-devel] " Bastian Blank
2009-11-24 0:52 ` Bug#544145: " Jeremy Fitzhardinge
2009-11-23 16:31 ` Jan Beulich
2009-11-23 16:44 ` Ian Campbell
2009-11-23 17:13 ` Keir Fraser
2009-11-23 17:17 ` Ian Campbell
2009-11-25 10:22 ` Jan Beulich
2009-11-25 21:24 ` Jeremy Fitzhardinge
2009-11-26 7:35 ` Jan Beulich
2009-11-26 9:57 ` Ian Campbell
2009-11-24 0:39 ` Jeremy Fitzhardinge
2009-11-24 9:48 ` Ian Campbell
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=20091118144518.GD15585@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=nenolod@dereferenced.org \
--cc=xen-devel@lists.xensource.com \
/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.