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

[Xen-devel] BUG while bringing up x86_64 SMP DomU


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
  • Date: Wed, 1 Feb 2006 11:33:13 -0500
  • Delivery-date: Wed, 01 Feb 2006 16:43:25 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcYnTTIcE6etzk89R7mzSgIXXlNe+A==
  • Thread-topic: BUG while bringing up x86_64 SMP DomU

I am seeing the following error when I try to bring up an x86_64 SMP DomU on 
changeset 8723. Is anyone seeing the same issue?

Thanks,
Aravindh Puthiyaparambil 
Unisys, Tredyffrin PA
Phone 610-648-2416
E-Mail:  aravindh.puthiyaparambil@xxxxxxxxxx 

Using config file "dom64_sles9_1".
Started domain sles9.sp2
Linux version 2.6.14-xenU (root@xenbox) (gcc version 3.3.3 (SuSE Linux)) #1 SMP 
Wed Feb 1 10:49:05 EST 2006
kernel direct mapping tables upto 20800000 @ 4d3000-5d9000
Built 1 zonelists
Kernel command line:  root=/dev/sda1 3
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 2992.696 MHz processor.
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 509564k/532480k available (1724k kernel code, 22196k reserved, 581k 
data, 132k init)
Calibrating delay using timer specific routine.. 7485.94 BogoMIPS (lpj=14971898)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
softlockup thread 0 started up.
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at kernel/softlockup.c:110
invalid operand: 0000 [1] SMP 
CPU 0 
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.14-xenU #1
RIP: e030:[<ffffffff8014f3c2>] <ffffffff8014f3c2>{cpu_callback+61}
RSP: e02b:ffff880000005ec8  EFLAGS: 00010286
RAX: ffffffff803c80f8 RBX: 0000000000000001 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffffffff802ff090
RBP: 0000000000000080 R08: 00000000fffffffb R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000000 R12: ffffffff803c80f8
R13: 0000000000000001 R14: 0000ffffffff8010 R15: ffffffff803a7fb0
FS:  0000000000000000(0000) GS:ffffffff80391800(0000) knlGS:ffffffff80391800
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 1, threadinfo ffff880000004000, task ffff8800000254e0)
Stack: ffffffff802ff090 0000000000000001 0000000000000003 ffffffff8013af5f 
       0000000000000001 0000000000000008 ffffffff802feb80 ffffffff801458f5 
       ffffffff802f2300 0000000000000001
Call Trace:<ffffffff8013af5f>{notifier_call_chain+31} 
<ffffffff801458f5>{cpu_up+101}
       <ffffffff8010e151>{init+269} <ffffffff8011164a>{child_rip+8}
       <ffffffff8010e044>{init+0} <ffffffff80111642>{child_rip+0}
       

Code: 0f 0b 68 8a 08 2c 80 c2 6e 00 31 c0 89 d9 48 c7 c2 9e 08 2c 
RIP <ffffffff8014f3c2>{cpu_callback+61} RSP <ffff880000005ec8>
 <0>Kernel panic - not syncing: Attempted to kill init!

_______________________________________________
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®.