From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Bastian Blank <waldi@debian.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Xen panics with 2.6.32.11
Date: Tue, 06 Apr 2010 15:33:36 -0700 [thread overview]
Message-ID: <4BBBB6C0.6050006@goop.org> (raw)
In-Reply-To: <4BBBB1EC.1030403@goop.org>
On 04/06/2010 03:13 PM, Jeremy Fitzhardinge wrote:
> Current xen-unstable crashes when booting xen/stable-2.6.32.x
> (2.6.32.11). I haven't
> verified it yet, but I guess this is Bastian's patch (537451477469).
> Or could it be Jan's 4f796e29987c?
Looks like 4f796e29987c is the culprit; reverting it lets the kernel
boot again.
Before the crash, I also see lots of complaints from Xen while setting
up interrupts:
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) io_apic.c:2296:
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2296:
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=000009f0 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped
(XEN) io_apic.c:2296:
(XEN) ioapic_guest_write: apic=0, pin=5, irq=5
(XEN) ioapic_guest_write: new_entry=000109f2
(XEN) ioapic_guest_write: old_entry=000009f2 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 13 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 14 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 15 already mapped
(XEN) allocated vector 21 for irq 16
(XEN) irq.c:1445: dom0: pirq 0 or irq 16 already mapped
(XEN) allocated vector 29 for irq 17
(XEN) irq.c:1445: dom0: pirq 0 or irq 17 already mapped
(XEN) allocated vector 31 for irq 18
(XEN) irq.c:1445: dom0: pirq 0 or irq 18 already mapped
(XEN) allocated vector 39 for irq 19
(XEN) irq.c:1445: dom0: pirq 0 or irq 19 already mapped
(XEN) allocated vector 41 for irq 20
(XEN) irq.c:1445: dom0: pirq 0 or irq 20 already mapped
(XEN) allocated vector 49 for irq 21
(XEN) irq.c:1445: dom0: pirq 0 or irq 21 already mapped
(XEN) allocated vector 51 for irq 22
(XEN) irq.c:1445: dom0: pirq 0 or irq 22 already mapped
(XEN) allocated vector 59 for irq 23
(XEN) irq.c:1445: dom0: pirq 0 or irq 23 already mapped
(XEN) io_apic.c:2296:
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000009f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
Initializing cgroup subsys cpuset
J
next prev parent reply other threads:[~2010-04-06 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:13 Xen panics with 2.6.32.11 Jeremy Fitzhardinge
2010-04-06 22:33 ` Jeremy Fitzhardinge [this message]
2010-04-12 10:04 ` Jan Beulich
2010-04-12 14:07 ` [PATCH] " Jan Beulich
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=4BBBB6C0.6050006@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=waldi@debian.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.