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

To:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] hypervisor crash with latest xen-unstable
From:	Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date:	Thu, 25 Nov 2010 11:27:07 +0100
Delivery-date:	Thu, 25 Nov 2010 02:27:55 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1290680830; x=1322216830; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; z=Message-ID:=20<4CEE39FB.2080301@xxxxxxxxxxxxxx>\|Date:=20 Thu,=2025=20Nov=202010=2011:27:07=20+0100\|From:=20Juergen =20Gross=20<juergen.gross@xxxxxxxxxxxxxx>\|MIME-Version: =201.0\|To:=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-devel @lists.xensource.com>\|Subject:=20hypervisor=20crash=20wit h=20latest=20xen-unstable\|Content-Transfer-Encoding:=207b it; bh=194XoeKvbDunemR+JVi9cLAX0bdnElSBBeY05gyFz0o=; b=o6CVWvVIE1H3w5MB5vIIePkXHsi84F6KJc2nkq5QEB8x06P20FHVodoV iLhebfDm3/VRyzbQdWstknUGMMwDX5aLcavzHf7le4ThZMc0oN12K0Q3x 9cK0rvd6hVZXSxL3y8JMv5PviDO07v+BZ19JZcnm7JrG2fRLiDp/q+dNw C3Ce15tB8oqkpEtx+WFWgdCF+kJkTu52lhU8CAmLZpN9atupehVIlTrSc /nAnBwn/e3E77OSXWy8aGHX5Wusbn;
Domainkey-signature:	s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=e7sDHCN3hMvqDSaLQzsleCF2/TIJ1zkcYf4atkBjj/PqMuc8I3SU9Xiy pU0z7cd/mjoO6lRMpaj2ZsiP2LDofdi46/gZi3ZkZ+G8YVik8j/+30z1X HUb5TkFv7nudM1vbhEoTHu1xledKsSCil1gwx/YIqU76+xMYs3aQkJCnP VnFT/kAZikCZtIiQK9ojjMXivfbUS7HBwqn5mOFLY53H0W2dD7QQMolvv dztznZnrCDrUoA7rWDYTFlyiU1PQu;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Organization:	Fujitsu Technology Solutions
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101030 Iceowl/1.0b1 Icedove/3.0.10

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

--
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

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

WARNING - OLD ARCHIVES

xen-devel

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