Re: [Xen-devel] xen kernel crash at boot since 23598:b24018319772

[Keir Fraser <keir.xen@xxxxxxxxx>]

On 30/06/2011 13:43, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>>>> On 30.06.11 at 14:06, Christoph Egger <Christoph.Egger@xxxxxxx> wrote:
> 
>> Changeset 23598:b24018319772 causes the xen kernel crash at boot:
> 
> That's likely not the one, but rather 23573:584c2e5e03d9. And
> indeed it seems like the assertion is a stale leftover from the
> original non-RCU version of the patch. There are a few more
> similar ones which may similarly be candidates fro removal.
> 
> Keir, what's your take on this?

Not sure, pirq_spin_lock_irq_desc() has a comment about the event_lock
preventing the PIRQ-IRQ mapping from changing under its feet. Why would the
radix-tree patch change what code is protected by event_lock, anyway?

 -- Keir

> Jan
> 
>> (XEN) Assertion 'spin_is_locked(&d->event_lock)' failed at irq.c:965
>> (XEN) ----[ Xen-4.2-unstable  x86_64  debug=y  Tainted:    C ]----
>> (XEN) CPU:    0
>> (XEN) RIP:    e008:[<ffff82c480160766>] pirq_spin_lock_irq_desc+0x2e/0xfb
>> (XEN) RFLAGS: 0000000000010246   CONTEXT: hypervisor
>> (XEN) rax: 0000000000000000   rbx: ffff830421db3e80   rcx: 0000000000000000
>> (XEN) rdx: 0000000000000292   rsi: ffff830421db3e80   rdi: ffff830421de9194
>> (XEN) rbp: ffff82c48029fd28   rsp: ffff82c48029fcf8   r8:  ffff82c48029fd18
>> (XEN) r9:  0000000000000000   r10: 0000000000001000   r11: ffffffffffffffc0
>> (XEN) r12: ffff830421de9000   r13: 000000000000002c   r14: ffff830421db3e80
>> (XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000406f0
>> (XEN) cr3: 0000000420f2b000   cr2: 0000000000000000
>> (XEN) ds: 0013   es: 0013   fs: 0000   gs: 0000   ss: e010   cs: e008
>> (XEN) Xen stack trace from rsp=ffff82c48029fcf8:
>> (XEN)    ffff82c480134dfb ffff830421db3e80 ffff830421de9000 ffff830421de9000
>> (XEN)    00000000000000c7 ffff830421de91a8 ffff82c48029fd48 ffff82c48016351b
>> (XEN)    000000000000000a 000000000000000c ffff82c48029fe18 ffff82c4801635dc
>> (XEN)    ffff82c48029ff18 ffff82c48029fd68 ffff830421db3d00 ffff830421dc2e80
>> (XEN)    ffff830421db1980 ffff830421db1b00 ffff830421db1c00 ffff830421db1880
>> (XEN)    ffff830421db1700 ffff830421db1600 ffff830421db1500 ffff830421db3f80
>> (XEN)    ffff830421db3e80 ffff830421db3e00 ffffffff8020d2df ffff82c48029ff18
>> (XEN)    ffff82c48029ff08 ffff82c4801812a2 000000000000f800 ffff8300cfd92000
>> (XEN)    ffffffff80bd85c8 0000000000000001 0000000000000000 0000000000000001
>> (XEN)    ffff82c48029feb8 ffff82c480174a63 ffff82c48029fe88 0000000000000092
>> (XEN)    ffff8300cfd92000 000000005f129b56 0000001300000001 000082c400000000
>> (XEN)    ffff82c480123806 00ff830421db3ee8 ffff82c48029feb8 ffff82c480126453
>> (XEN)    0000000800000008 ffffffff8020d2df ffff82c48029feb8 ffff82c480182e4e
>> (XEN)    ffffffff80bd85c0 0000000000002480 0000000000000001 0000000000000000
>> (XEN)    ffff82c48029fef8 ffff82c48014e671 0000000000000004 0000000000000000
>> (XEN)    0000000000000000 ffffffff80c7e870 00000000deadbeef ffff8300cfd92000
>> (XEN)    00007d3b7fd600c7 ffff82c480216d78 ffffffff8010126a 0000000000000013
>> (XEN)    0000000000000001 0000000000000000 0000000000000001 0000000000002480
>> (XEN)    ffffffff80f3cd48 0000000000000005 0000000000000202 0000000000000000
>> (XEN)    ffffffff80993d23 0000000000000004 0000000000000013 ffffffff8010126a
>> (XEN) Xen call trace:
>> (XEN)    [<ffff82c480160766>] pirq_spin_lock_irq_desc+0x2e/0xfb
>> (XEN)    [<ffff82c48016351b>] pirq_guest_eoi+0x33/0x4b
>> (XEN)    [<ffff82c4801635dc>] pirq_guest_unmask+0xa9/0xdf
>> (XEN)    [<ffff82c480174a63>] do_physdev_op+0x403/0x1388
>> (XEN)    [<ffff82c48014e671>] do_physdev_op_compat+0x6c/0x7b
>> (XEN)    [<ffff82c480216d78>] syscall_enter+0xc8/0x122
>> (XEN)
>> (XEN)
>> (XEN) ****************************************
>> (XEN) Panic on CPU 0:
>> (XEN) Assertion 'spin_is_locked(&d->event_lock)' failed at irq.c:965
>> (XEN) ****************************************
>> (XEN)
>> (XEN) Reboot in five seconds...
>> 
>> 
> 
> 
> 
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel