From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>,
Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen
Date: Thu, 14 Jan 2010 11:26:12 +0000 [thread overview]
Message-ID: <C774AFD4.6600%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <34CA9509B98113kanno.masaki@jp.fujitsu.com>
On 14/01/2010 11:07, "Masaki Kanno" <kanno.masaki@jp.fujitsu.com> wrote:
> Hi Jan,
>
> Thu, 14 Jan 2010 09:05:32 +0000, "Jan Beulich" wrote:
>
>> You forgot to tell us in what way the boot fails.
>
> Oops! Could you refer to the following about a serial log when the
> problem occurred?
>
> http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00338.html
>
> Accurately, the problem is not "Domain-0 kernel boot fails" but "Domain-
> 0 kernel boot does not start".
I don't know how much experience with kernel issues you have, but I would
take the EIP from the CPU0 guest dump in that log file (the EIP is c01edc67)
and look at that code address in a disassembly of the dom0 kernel image
(objdump -d vmlinux). Seeing what function you're in would be a good start.
'addr2line -e vmlinux c01edc67' would also be useful: tells you the source
file and line number.
-- Keir
next prev parent reply other threads:[~2010-01-14 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 1:51 Domain-0 kernel boot failure with xen-unstable and linux-2.6.18-xen Masaki Kanno
2010-01-14 2:57 ` Domain-0 kernel boot failure with xen-unstable andlinux-2.6.18-xen Masaki Kanno
2010-01-14 5:45 ` Domain-0 kernel boot failure with xen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14 6:18 ` Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14 9:05 ` Jan Beulich
2010-01-14 11:07 ` Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14 11:26 ` Keir Fraser [this message]
2010-01-14 11:42 ` Domain-0 kernel bootfailurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-15 12:35 ` Domain-0 kernelbootfailurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14 9:31 ` Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen Keir Fraser
2010-01-14 11:33 ` Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-18 15:18 ` Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen Keir Fraser
2010-01-19 10:14 ` Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
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=C774AFD4.6600%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=kanno.masaki@jp.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).