[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] hypervisor crash with latest xen-unstable


  • To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Fri, 26 Nov 2010 10:12:55 +0000
  • Cc:
  • Delivery-date: Fri, 26 Nov 2010 02:14:21 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=qR0yI5RxWV+NDHtnHR5e7I8ih0/n492npjNxOG4tc+EOfagqsSBAjLa0k+1IAx0msA xVdBFTdKMf3ZY/bKvLmzo8qV9Q5i9aRAplS9srTFyW2D3G514xwgC2F5VIpSc4r+Rn5w DTtXPWK+hI8eNy5EUOVKop9H8BTVQbv7ctZU0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcuNUn3xe3FLS14Iu0q6VRBv5K1iAQ==
  • Thread-topic: [Xen-devel] hypervisor crash with latest xen-unstable

Fixed by xen-unstable:22342.

 K.

On 25/11/2010 10:27, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxx> wrote:

> Hi,
> 
> latest xen-unstable crashed when I tried to remove a cpu from a cpupool via
> 
> xl cpupool-cpu-remove
> 
> Serial log shows:
> 
> (XEN) Assertion '!(((*({ unsigned long __ptr; __asm__ ("" : "=r"(__ptr) :
> "0"(&per_cpu____preempt_count)); (typeof(&per_cpu____preempt_count)) (__ptr +
> (get_cpu_info()->per_cpu_offset)); }))) ||
> ((irq_stat[(((get_cpu_info()->processor_id)))].__local_irq_count) != 0) ||
> !local_irq_is_enabled())' failed at softirq.c:61
> (XEN) ----[ Xen-4.1-unstable  x86_64  debug=y  Tainted:    C ]----
> (XEN) CPU:    5
> (XEN) RIP:    e008:[<ffff82c4801212f9>] do_softirq+0x51/0x7a
> (XEN) RFLAGS: 0000000000010202   CONTEXT: hypervisor
> (XEN) rax: ffff82c4802ca2a0   rbx: ffff8300780da000   rcx: ffff82c4802a7080
> (XEN) rdx: 00000043b9aefd80   rsi: ffff830839db7ec0   rdi: ffff82c48024d0e0
> (XEN) rbp: ffff830839db7f08   rsp: ffff830839db7f08   r8:  0000000000000005
> (XEN) r9:  0000ffff0000ffff   r10: 00000000deadbeef   r11: 0f0f0f0f0f0f0f0f
> (XEN) r12: ffff8803f8f61440   r13: ffff8803fdf4fe58   r14: 0000000000000000
> (XEN) r15: 00007fff335d7150   cr0: 0000000080050033   cr4: 00000000000026f0
> (XEN) cr3: 0000000846990000   cr2: 0000000000627048
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff830839db7f08:
> (XEN)    00007cf7c62480c7 ffff82c480202736 00007fff335d7150 0000000000000000
> (XEN)    ffff8803fdf4fe58 ffff8803f8f61440 ffffffffffffffda ffff8803fd491438
> (XEN)    0000000000000216 000000000061e004 000000000061d050 00007f6d701d9f6c
> (XEN)    0000000000000000 ffffffff8000346a 000000000061c2e0 0000000000624004
> (XEN)    00000000deadbeef 0000010000000000 ffffffff8000346a 000000000000e033
> (XEN)    0000000000000216 ffff8803fdf4fd80 000000000000e02b 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000005
> (XEN)    ffff8300780da000 00000043b9aefd80 0000000000000000
> (XEN) Xen call trace:
> (XEN)    [<ffff82c4801212f9>] do_softirq+0x51/0x7a
> (XEN)
> 
> I suspect the waitqueue stuff broke the continue_hypercall_on_cpu() stuff.
> 
> 
> Juergen



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.