From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Xen panics with 2.6.32.11
Date: Tue, 06 Apr 2010 15:33:36 -0700
Message-ID: <4BBBB6C0.6050006@goop.org>
References: <4BBBB1EC.1030403@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4BBBB1EC.1030403@goop.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
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>
List-Id: xen-devel@lists.xenproject.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