WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [Xen-devel] RE: odd IRQ behavior

from [Cihula, Joseph] [Permanent Link][Original]
To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] RE: odd IRQ behavior
From: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>
Date: Fri, 27 Feb 2009 06:35:22 -0800
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Fri, 27 Feb 2009 06:35:52 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5CD63E5.36D1%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4F65016F6CB04E49BFFA15D4F7B798D98D4BA3B7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C5CD63E5.36D1%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmYft/BQyNL3H4qSR26RJ7HKdFeNQAD2HZgAAwLpTwACmr6QA==
Thread-topic: [Xen-devel] RE: odd IRQ behavior 
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Friday, February 27, 2009 1:33 AM
>
> On 27/02/2009 03:52, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx> wrote:
>
> >> But why are these necessary?  Even if we say that something has caused the
> >> irq_count to go
> >> positive before shutdown (but what-it wasn't like this before pulling a 
> >> more
> >> recent tree), the
> >> irq_exit() that gets rid of the assertion means that the count has gone to
> >> 0-so why is it
> >> negative on resume?
> >
> > As an additional data point/issue, if I build with debug=y, the
> > map_pages_to_xen() call (on a reboot) generates a BUG_ON(seen == !irq_safe) 
> > in
> > check_lock().  But prior to the map_pages_to_xen() call, we call
> > local_irq_disable(), so it should be called as irq_safe.  I'm not sure how 
> > to
> > fix this.
>
> Please provide some backtraces.
>
>  -- Keir

Trace of assertion at shutdown entry:
====================================
Restarting system.
(XEN) Domain 0 shutdown: rebooting machine.
(XEN) Assertion '!((irq_stat[(((get_cpu_info()->processor_id)))].__local_irq_cou
nt) != 0)' failed at page_alloc.c:843
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff828c8011305e>] alloc_domheap_pages+0x5e/0x171
(XEN) RFLAGS: 0000000000010002   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: ffff830078ce0020   rcx: 0000000000000000
(XEN) rdx: ffff828c8028e900   rsi: 0000000000000000   rdi: 0000000000000000
(XEN) rbp: ffff828c80277d18   rsp: ffff828c80277ce8   r8:  0000000000000010
(XEN) r9:  0000000000000700   r10: ffff828c80156e68   r11: 000000099b1d6973
(XEN) r12: 0000000000000063   r13: 00000000000000ff   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 0000000080050033   cr4: 00000000000026f0
(XEN) cr3: 0000000072ca7000   cr2: 0000003801031320
(XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff828c80277ce8:
(XEN)    0000000000000000 ffff830078ce0020 0000000000000063 0000000000000063
(XEN)    0000000000000803 0000000000803000 ffff828c80277d28 ffff828c801cecd0
(XEN)    ffff828c80277d98 ffff828c8014a465 00000000000000e3 000000000000004c
(XEN)    0000000000000803 0000000000000000 0000000000000063 ffff830078ce1000
(XEN)    0000000000000063 0000000000000803 000000000000004c 0000000000000000
(XEN)    ffff828c80210660 ffff828c8028ad60 ffff828c80277dc8 ffff828c801734a3
(XEN)    ffff828c80277dc8 0000000000000000 ffff828c80277f28 ffff828c8028e900
(XEN)    ffff828c80277e08 ffff828c80156aac 00000000000004e8 00000000802a0824
(XEN)    ffff828c80277f28 ffff828c80277f28 ffff828c8028e900 ffff828c80210660
(XEN)    ffff828c80277e18 ffff828c80156b40 ffff828c80277e28 ffff828c80156e03
(XEN)    00007d737fd881a7 ffff828c80141450 ffff828c8028ad60 ffff828c80210660
(XEN)    ffff828c8028e900 ffff828c80277f28 ffff828c80277ee0 ffff828c80277f28
(XEN)    000000099b1d6973 ffff828c802bdaa0 0000000000000005 0000000000000001
(XEN)    0000000000000000 0000000000000001 ffff828c8028e900 ffff828c802305c0
(XEN)    0000000000000000 000000fb00000000 ffff828c8013a4ce 000000000000e008
(XEN)    0000000000000246 ffff828c80277ee0 000000000000e010 ffff828c80277f20
(XEN)    ffff828c8013c60a ffff830077598000 ffff828c80230120 ffff830079ede000
(XEN)    ffff830079ede000 0000000001c9c380 ffff828c80230100 ffff828c80277e10
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000001 0000000000000246 00000000000014e6
(XEN) Xen call trace:
(XEN)    [<ffff828c8011305e>] alloc_domheap_pages+0x5e/0x171
(XEN)    [<ffff828c801cecd0>] alloc_xen_pagetable+0x21/0x8d
(XEN)    [<ffff828c8014a465>] map_pages_to_xen+0x676/0xc67
(XEN)    [<ffff828c801734a3>] tboot_shutdown+0x50/0x9ad
(XEN)    [<ffff828c80156aac>] machine_restart+0xa4/0x12d
(XEN)    [<ffff828c80156b40>] __machine_restart+0xb/0xd
(XEN)    [<ffff828c80156e03>] smp_call_function_interrupt+0xc0/0xe8
(XEN)    [<ffff828c80141450>] call_function_interrupt+0x30/0x40
(XEN)    [<ffff828c8013a4ce>] default_idle+0x2f/0x34
(XEN)    [<ffff828c8013c60a>] idle_loop+0xc8/0xe2
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion '!((irq_stat[(((get_cpu_info()->processor_id)))].__local_irq_cou
nt) != 0)' failed at page_alloc.c:843
(XEN) ****************************************

Assertion at S3 resume:
======================
(XEN) Finishing wakeup from ACPI S3 state.
(XEN) Thawing cpus ...
(XEN) Booting processor 1/1 eip 8c000
TBOOT: cpu 1 waking up, SIPI vector=8c000
(XEN) CPU1: Intel Genuine Intel(R) CPU                  @ 2.40GHz stepping 04
(XEN) CPU1 is up
(XEN) ioapic_guest_write: apic=0, pin=9, old_irq=9, new_irq=9
(XEN) ioapic_guest_write: old_entry=0000d950, new_entry=00008950
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) Xen BUG at mm.c:467
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff828c8014984f>] invalidate_shadow_ldt+0x3f/0x110
(XEN) RFLAGS: 0000000000010286   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: 0000000000000005   rcx: 8000000000000000
(XEN) rdx: ffff828c8027e900   rsi: 0000000000000000   rdi: ffff8300775ea000
(XEN) rbp: ffff8300775ea000   rsp: ffff828c80267de8   r8:  ffff8284000f8150
(XEN) r9:  8000000000000000   r10: 9800000000000002   r11: 0000000000000000
(XEN) r12: ffff8300775ea000   r13: 00000000ffffffff   r14: ffff88006f3f1dc8
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 000000000af66000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff828c80267de8:
(XEN)    ffffffff00000200 0000000000000005 ffff8300775ea000 ffff830079e50000
(XEN)    0000000000007c0a ffff88006f3f1dc8 ffffffffffff8000 ffff828c8014d0ea
(XEN)    0000000000000000 0000000000000005 0000000000007c0a 0000000000000000
(XEN)    ffff8284000f8140 ffff828c8014d8e8 ffffffff804d593c ffff828c8021d740
(XEN)    ffff828c8021d5a0 ffff828c8021d5a8 ffff828c8021d540 ffff828c80267f28
(XEN)    ffff828c80267f28 00007ff079e50000 0000000000000000 0000000000000002
(XEN)    ffff8300775ea000 ffff830079e50000 0000000000000005 0000000000007c0a
(XEN)    ffff88006f3f1df8 0000000000000050 ffff828c00000001 000000008027e900
(XEN)    ffff828c8028fc80 ffff8300775ea000 ffff88006f3f1e58 ffff88006e017080
(XEN)    ffff8800010044c0 0000000000000000 0000000944d77c74 ffff828c801c0169
(XEN)    0000000944d77c74 0000000000000000 ffff8800010044c0 ffff88006e017080
(XEN)    ffff88006f3f1e58 ffff88006ef12080 0000000000000a07 0000000000007ff0
(XEN)    ffff8800710d0168 ffff88006f3f0000 000000000000001a ffffffff8020634a
(XEN)    0000000000000000 0000000000000002 ffff88006f3f1dc8 0000010000000000
(XEN)    ffffffff8020634a 000000000000e033 0000000000000a07 ffff88006f3f1d70
(XEN)    000000000000e02b 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 ffff8300775ea000
(XEN) Xen call trace:
(XEN)    [<ffff828c8014984f>] invalidate_shadow_ldt+0x3f/0x110
(XEN)    [<ffff828c8014d0ea>] new_guest_cr3+0x12a/0x1f0
(XEN)    [<ffff828c8014d8e8>] do_mmuext_op+0x738/0x10d0
(XEN)    [<ffff828c801c0169>] syscall_enter+0xa9/0xae
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at mm.c:467
(XEN) ****************************************

Debug build shutdown BUG_ON:
===========================
(XEN) Xen BUG at spinlock.c:23
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff828c8011b414>] check_lock+0x44/0x55
(XEN) RFLAGS: 0000000000010046   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: ffff828c801fc6d4   rcx: 0000000000000001
(XEN) rdx: 0000000000000000   rsi: 0000000000000001   rdi: ffff828c801fc6d8
(XEN) rbp: ffff828c8027fc50   rsp: ffff828c8027fc50   r8:  0000000000000001
(XEN) r9:  0000ffff0000ffff   r10: 00ff00ff00ff00ff   r11: 0f0f0f0f0f0f0f0f
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000027
(XEN) r15: 0000000000000001   cr0: 0000000080050033   cr4: 00000000000026f0
(XEN) cr3: 0000000079e84000   cr2: 0000003801031320
(XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff828c8027fc50:
(XEN)    ffff828c8027fc68 ffff828c8011b456 0000000000000000 ffff828c8027fcd8
(XEN)    ffff828c80112afd ffff828c8027fc88 ffff828c8011b69f 000000018027fd98
(XEN)    0000000100000000 0000000000000000 ffff828c80297e8e 0000003000000010
(XEN)    0000000000000027 0000000000000063 00000000000000ff 0000000000000000
(XEN)    0000000000000000 ffff828c8027fd18 ffff828c801131e1 0000000000000000
(XEN)    ffff830078ce0020 0000000000000063 0000000000000063 0000000000000803
(XEN)    0000000000803000 ffff828c8027fd28 ffff828c801d0cd0 ffff828c8027fd98
(XEN)    ffff828c8014b5a5 00000000000000e3 000000000000004c 0000000000000803
(XEN)    0000000000000000 0000000000000063 ffff830078ce1000 0000000000000063
(XEN)    0000000000000803 000000000000004c 0000000000000000 ffff828c80212860
(XEN)    ffff828c80292d60 ffff828c8027fdc8 ffff828c801747a4 ffff828c8027fdc8
(XEN)    0000000000000000 ffff828c8027ff28 ffff828c80296900 ffff828c8027fe08
(XEN)    ffff828c80157c6c 00000000000004e8 00000000802a88a4 ffff828c8027ff28
(XEN)    ffff828c8027ff28 ffff828c80296900 ffff828c80212860 ffff828c8027fe18
(XEN)    ffff828c80157d00 ffff828c8027fe28 ffff828c80157fc3 00007d737fd801a7
(XEN)    ffff828c801424b0 ffff828c80292d60 ffff828c80212860 ffff828c80296900
(XEN)    ffff828c8027ff28 ffff828c8027fee0 ffff828c8027ff28 000000161034d8e8
(XEN)    ffff830077590060 0000000000000005 0000000000000001 0000000000000000
(XEN)    0000000000000001 ffff828c80296900 ffff828c802325c0 0000000000000000
(XEN)    000000fb00000000 ffff828c8013b4fe 000000000000e008 0000000000000246
(XEN) Xen call trace:
(XEN)    [<ffff828c8011b414>] check_lock+0x44/0x55
(XEN)    [<ffff828c8011b456>] _spin_lock+0x11/0x24
(XEN)    [<ffff828c80112afd>] alloc_heap_pages+0xe6/0x3d9
(XEN)    [<ffff828c801131e1>] alloc_domheap_pages+0x11c/0x171
(XEN)    [<ffff828c801d0cd0>] alloc_xen_pagetable+0x21/0x8d
(XEN)    [<ffff828c8014b5a5>] map_pages_to_xen+0x676/0xc67
(XEN)    [<ffff828c801747a4>] tboot_shutdown+0xb8/0xa14
(XEN)    [<ffff828c80157c6c>] machine_restart+0xa4/0x12d
(XEN)    [<ffff828c80157d00>] __machine_restart+0xb/0xd
(XEN)    [<ffff828c80157fc3>] smp_call_function_interrupt+0xc0/0xe8
(XEN)    [<ffff828c801424b0>] call_function_interrupt+0x30/0x40
(XEN)    [<ffff828c8013b4fe>] default_idle+0x2f/0x34
(XEN)    [<ffff828c8013d63a>] idle_loop+0xc8/0xe2
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at spinlock.c:23
(XEN) ****************************************


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] RCU locks in Xen!, Keir Fraser
Next by Date:  [Xen-devel] QEMU for IA 64, Suraj B
Previous by Thread:  Re: [Xen-devel] RE: odd IRQ behavior, Keir Fraser
Next by Thread:  Re: [Xen-devel] RE: odd IRQ behavior, Keir Fraser
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy