From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, torvalds@linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.32-rc not booting with Xen-3.2 (bisected)
Date: Tue, 27 Oct 2009 11:18:27 -0700 [thread overview]
Message-ID: <4AE73973.3070709@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.01.0910262154410.9408@bogon.housecafe.de>
On 10/26/09 22:01, Christian Kujau wrote:
> On Mon, 26 Oct 2009 at 21:20, Jeremy Fitzhardinge wrote:
>
>> What does this map to in the kernel symbol table?
>>
> Hm, I'm not sure how to answer this? Got a hint, please?
>
$ gdb vmlinux
(gdb) x/i 0xffffffff812c50ad
>>> Also, "xm list" takes very long to complete now:
>>>
>>> $ time xm list sid
>>> Name ID Mem VCPUs State Time(s)
>>> sid 906 512 1 --p--- 0.0
>>> real 0m10.677s user 0m0.108s sys 0m0.028s
>>>
>> Hm, that's odd. Never seen that.
>>
> The load of the Dom0 with the panicked DomU "running" higher than
> usual (3-4 instead of ~0) and xenstored is spinning and waiting for
> (causing?) disk I/O. This is not the case when the DomU is runing just
> fine. I didn't strace xenstored yet, because I don't want to risk
> killing the whole Xen box.
>
Hm, sounds like a xenstored bug, or something is just pounding on it.
Are there any other domains running, or other busy processes?
J
next prev parent reply other threads:[~2009-10-27 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 22:02 2.6.32-rc not booting with Xen-3.2 (bisected) Christian Kujau
2009-10-26 22:17 ` Christian Kujau
2009-10-26 22:55 ` Jeremy Fitzhardinge
2009-10-27 1:14 ` Christian Kujau
2009-10-27 1:26 ` Christian Kujau
2009-10-27 4:20 ` Jeremy Fitzhardinge
2009-10-27 5:01 ` Christian Kujau
2009-10-27 18:18 ` Jeremy Fitzhardinge [this message]
2009-10-27 19:01 ` Christian Kujau
2009-10-27 19:12 ` Jeremy Fitzhardinge
2009-10-28 2:10 ` Jeremy Fitzhardinge
2009-11-02 6:53 ` Christian Kujau
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=4AE73973.3070709@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 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.