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-bugs

[Xen-bugs] [Bug 1730] New: "xl vcpu-set" causes dom0 crash or panic

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1730] New: "xl vcpu-set" causes dom0 crash or panic
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 27 Jan 2011 01:25:55 -0800
Delivery-date: Thu, 27 Jan 2011 01:26:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730

           Summary: "xl vcpu-set" causes dom0 crash or panic
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: shaohui.zheng@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): 
Guest Arch (ia32/ia32e/IA64): 
Guest OS Type (Linux/Windows):
Change Set: 22812:73b3debb90cf
Hardware: Westmere-EP, Westmere-EX
Other:


Bug detailed description:
--------------------------

I try to set dom0 vcpu number with command "xl vcpu-set", but after I run this
command, it cause dom0 crash immediately.

If set 2 vcpus to dom0, it print only a few call trace. 
If set 16 vcpus to dom0, it can print a lot of information.


Reproduce steps:
----------------
1. run command "xl vcpu-set 0 16" to set dom0 vcpu number 
2.
3.

Current result:
----------------


Expected result:
----------------


Basic root-causing log:
----------------------
[root@vt-nhm7 ~]# xl vcpu-set 0 16
[root@vt-nhm7 ~]# [  260.278387] Cannot set affinity for irq 4206
[  260.278817] Broke affinity for irq 4506
[  260.278825] Broke affinity for irq 4507
[  260.278833] Broke affinity for irq 4508
[  260.278840] Broke affinity for irq 4509
[  260.278848] Broke affinity for irq 4510
[  260.278855] Broke affinity for irq 4511
[  260.280137] ------------[ cut here ]------------
[  260.280193] kernel BUG at
/home/nightly/builds_xen_unstable/xen-3.x-hg-xen_unstable-22799-20110125/linux-2.6-pvops.git/arch/x86/xen/spinlock.c:343!
[  260.280269] invalid opcode: 0000 [#1] SMP 
[  260.280565] last sysfs file:
/sys/devices/system/cpu/cpu63/cache/index2/shared_cpu_map
[  260.280604] CPU 3 
[  260.280666] Modules linked in: nfs nfs_acl auth_rpcgss lockd sunrpc igbvf
cxgb3i cxgb3 mdio libiscsi_tcp libiscsi scsi_transport_iscsi sg sr_mod cdrom
tpm_tis tpm tpm_bios igb ata_piix ide_gd_mod ide_core usb_storage ahci libata
sd_mod scsi_mod uhci_hcd ohci_hcd ehci_hcd
[  260.280835] Pid: 11109, comm: kstop/3 Not tainted 2.6.32.27 #2 QSSC-S4R
[  260.280842] RIP: e030:[<ffffffff81039f6c>]  [<ffffffff81039f6c>]
dummy_handler+0x4/0x8
[  260.280862] RSP: e02b:ffff88003105ded8  EFLAGS: 00010046
[  260.280867] RAX: 00000000000011ed RBX: ffff88003fc05720 RCX:
ffff88003fc40600
[  260.280874] RDX: ffff88003fc30000 RSI: 0000000000000000 RDI:
00000000000011ec
[  260.280881] RBP: ffff88003105ded8 R08: ffff880031066640 R09:
0000000000000000
[  260.280887] R10: ffff88003105dcb8 R11: ffff88003105dd18 R12:
00000000000011ec
[  260.280894] R13: 0000000000000001 R14: 00000000000011ec R15:
0000000000000000
[  260.280905] FS:  00007fb89d079710(0000) GS:ffff88003105a000(0000)
knlGS:0000000000000000
[  260.280912] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[  260.280918] CR2: 0000000000455e40 CR3: 000000003ecc9000 CR4:
0000000000002660
[  260.280926] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[  260.280933] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[  260.280940] Process kstop/3 (pid: 11109, threadinfo ffff8800059b6000, task
ffff8800059b8f20)
[  260.280946] Stack:
[  260.280950]  ffff88003105df18 ffffffff810be9e4 000000003105df18
ffff88003fe39380
[  260.280964] <0> 00000000000011ec 0000000000000001 0000000000000000
0000000000000600
[  260.280980] <0> ffff88003105df38 ffffffff810c02a2 00000000000011ec
ffff880031065080
[  260.280999] Call Trace:
[  260.281003]  <IRQ> 
[  260.281015]  [<ffffffff810be9e4>] handle_IRQ_event+0x6f/0x137
[  260.281023]  [<ffffffff810c02a2>] handle_percpu_irq+0x3c/0x69
[  260.281034]  [<ffffffff8125345e>] __xen_evtchn_do_upcall+0xe1/0x166
[  260.281045]  [<ffffffff810b4a03>] ? stop_cpu+0x0/0xe9
[  260.281053]  [<ffffffff81254efa>] xen_evtchn_do_upcall+0x2e/0x44
[  260.281064]  [<ffffffff8103de3e>] xen_do_hypervisor_callback+0x1e/0x30
[  260.281075]  <EOI> 
[  260.281082]  [<ffffffff810b4a03>] ? stop_cpu+0x0/0xe9
[  260.281094]  [<ffffffff8100922a>] ? hypercall_page+0x22a/0x1000
[  260.281104]  [<ffffffff8100922a>] ? hypercall_page+0x22a/0x1000
[  260.281116]  [<ffffffff81038ec1>] ? xen_force_evtchn_callback+0xd/0xf
[  260.281127]  [<ffffffff81039632>] ? check_events+0x12/0x20
[  260.281137]  [<ffffffff810395d9>] ? xen_irq_enable_direct_end+0x0/0x7
[  260.281146]  [<ffffffff810b4ae7>] ? stop_cpu+0xe4/0xe9
[  260.281158]  [<ffffffff8108e0a5>] ? worker_thread+0x144/0x1e0
[  260.281167]  [<ffffffff810916c6>] ? autoremove_wake_function+0x0/0x38
[  260.281180]  [<ffffffff8108df61>] ? worker_thread+0x0/0x1e0
[  260.281188]  [<ffffffff81091475>] ? kthread+0x69/0x71
[  260.281199]  [<ffffffff8103dcea>] ? child_rip+0xa/0x20
[  260.281215]  [<ffffffff8103cea1>] ? int_ret_from_sys_call+0x7/0x1b
[  260.281226]  [<ffffffff8103d65d>] ? retint_restore_args+0x5/0x6
[  260.281239]  [<ffffffff8103dce0>] ? child_rip+0x0/0x20
[  260.281248] Code: c9 0f 95 c0 c3 55 31 c0 66 83 7f 02 00 48 89 e5 c9 0f 95
c0 c3 55 b0 01 86 07 48 89 e5 84 c0 c9 0f 94 c0 0f b6 c0 c3 55 48 89 e5 <0f> 0b
eb fe 80 3d 29 86 8d 00 00 55 48 89 e5 74 1a ba c0 01 00 
[  260.281450] RIP  [<ffffffff81039f6c>] dummy_handler+0x4/0x8
[  260.281460]  RSP <ffff88003105ded8>
[  260.281473] ---[ end trace 4041652f6c78f4b6 ]---
[  260.281481] Kernel panic - not syncing: Fatal exception in interrupt


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>