RE: Xen in a 32 way system

RE: Xen in a 32 way system

[Puthiyaparambil, Aravindh]

[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]

What kind of 32-way system is this? I have been able to run Xen 3.0.2 on
a 64-way Unisys ES7000 without any issues. I am cross-posting on the
xen-devel list in case it is an IBM machine. Could you please send more
serial console output? 

 

Thanks,

Aravindh

 

________________________________

From: Pablo Montesinos [mailto:pablomontesinos@gmail.com] 
Sent: Tuesday, May 30, 2006 5:06 PM
To: Uros Trebec; xen-users@lists.xensource.com
Subject: Re: [Xen-users] Xen in a 32 way system

 

Actually, there is some skew in all the processors.
Pablo

On 5/30/06, Uros Trebec <uros.trebec@gmail.com > wrote:

On 5/30/06, Pablo Montesinos < pablomontesinos@gmail.com
<mailto:pablomontesinos@gmail.com> > wrote:
> yes
>
> (XEN) CPU#31 had -112556 usecs TSC skew, fixed it up

It looks like there's something wrong with processor #31...
Try removing it and see what happens. 

regards,
Uros

 


[-- Attachment #1.2: Type: text/html, Size: 4457 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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

Re: RE: [Xen-users] Xen in a 32 way system

[Ryan Harper]

* Puthiyaparambil, Aravindh <aravindh.puthiyaparambil@unisys.com> [2006-05-31 09:00]:
> What kind of 32-way system is this? I have been able to run Xen 3.0.2 on
> a 64-way Unisys ES7000 without any issues. I am cross-posting on the
> xen-devel list in case it is an IBM machine. Could you please send more
> serial console output? 
> 
>  
> 
> Thanks,
> 
> Aravindh
> 
>  
> 
> ________________________________
> 
> From: Pablo Montesinos [mailto:pablomontesinos@gmail.com] 
> Sent: Tuesday, May 30, 2006 5:06 PM
> To: Uros Trebec; xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Xen in a 32 way system
> 
>  
> 
> Actually, there is some skew in all the processors.
> Pablo
> 
> On 5/30/06, Uros Trebec <uros.trebec@gmail.com > wrote:
> 
> On 5/30/06, Pablo Montesinos < pablomontesinos@gmail.com
> <mailto:pablomontesinos@gmail.com> > wrote:
> > yes
> >
> > (XEN) CPU#31 had -112556 usecs TSC skew, fixed it up

AFAIK, this is harmless.  Our x460 32-way spits out the same
information.  This is part of the TSC synchronization code in Xen during
boot.

(XEN) checking TSC synchronization across 32 CPUs:
(XEN) CPU#0 had -125003 usecs TSC skew, fixed it up.
(XEN) CPU#1 had -125001 usecs TSC skew, fixed it up.
(XEN) CPU#2 had -124997 usecs TSC skew, fixed it up.
(XEN) CPU#3 had -125001 usecs TSC skew, fixed it up.
(XEN) CPU#4 had -125000 usecs TSC skew, fixed it up.
(XEN) CPU#5 had -125000 usecs TSC skew, fixed it up.
(XEN) CPU#6 had -124992 usecs TSC skew, fixed it up.
(XEN) CPU#7 had -124976 usecs TSC skew, fixed it up.
(XEN) CPU#8 had -125022 usecs TSC skew, fixed it up.
(XEN) CPU#9 had -125022 usecs TSC skew, fixed it up.
(XEN) CPU#10 had -125022 usecs TSC skew, fixed it up.
(XEN) CPU#11 had -125022 usecs TSC skew, fixed it up.
(XEN) CPU#12 had -125020 usecs TSC skew, fixed it up.
(XEN) CPU#13 had -125020 usecs TSC skew, fixed it up.
(XEN) CPU#14 had -125019 usecs TSC skew, fixed it up.
(XEN) CPU#15 had -125019 usecs TSC skew, fixed it up.
(XEN) CPU#16 had -124498 usecs TSC skew, fixed it up.
(XEN) CPU#17 had -124498 usecs TSC skew, fixed it up.
(XEN) CPU#18 had -124498 usecs TSC skew, fixed it up.
(XEN) CPU#19 had -124498 usecs TSC skew, fixed it up.
(XEN) CPU#20 had -124498 usecs TSC skew, fixed it up.
(XEN) CPU#21 had -124498 usecs TSC skew, fixed it up.
(XEN) CPU#22 had -124496 usecs TSC skew, fixed it up.
(XEN) CPU#23 had -124496 usecs TSC skew, fixed it up.
(XEN) CPU#24 had 374521 usecs TSC skew, fixed it up.
(XEN) CPU#25 had 374520 usecs TSC skew, fixed it up.
(XEN) CPU#26 had 374511 usecs TSC skew, fixed it up.
(XEN) CPU#27 had 374511 usecs TSC skew, fixed it up.
(XEN) CPU#28 had 374511 usecs TSC skew, fixed it up.
(XEN) CPU#29 had 374511 usecs TSC skew, fixed it up.
(XEN) CPU#30 had 374521 usecs TSC skew, fixed it up.
(XEN) CPU#31 had 374520 usecs TSC skew, fixed it up.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

Re: [Xen-devel] RE: Xen in a 32 way system

[Pablo Montesinos]

[-- Attachment #1: Type: text/plain, Size: 298 bytes --]

Hi all:
I have attached the serial output for the system with 32 procs.
To recap: It does boot with 4,8,16 procs.


I have domains kiking and running if I boot with only 4 processors.
if I use 8 or 16 procs, xend kills the network when I launch it,
so I am also looking into it now.

Thanks,
Pablo

[-- Attachment #2: serialconsole.log --]
[-- Type: text/x-log, Size: 30195 bytes --]

root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
kernel /xen-3.0.2-2.gz dom0_mem=8388608 com1=115200 sync_console noreboot
   [Multiboot-elf, <0x100000:0x844c0:0x30b40>, shtab=0x1b5078, entry=0x100000]
module /vmlinuz-2.6.16-xen0 ro root=/dev/VolGroup00/LogVol00
   [Multiboot-module @ 0x1b6000, 0x6810e0 bytes]
module /initrd-2.6.16-xen0.img
   [Multiboot-module @ 0x838000, 0x342e00 bytes]

 __  __            _____  ___   ____    ____
 \ \/ /___ _ __   |___ / / _ \ |___ \  |___ \
  \  // _ \ '_ \    |_ \| | | |  __) |__ __) |
  /  \  __/ | | |  ___) | |_| | / __/|__/ __/
 /_/\_\___|_| |_| |____(_)___(_)_____| |_____|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory
  Xen version 3.0.2-2 (root@xx.xxx.xxx) (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)) Fri May 26 15:48:15 PDT 2006
 Latest ChangeSet: Thu Apr 13 15:18:37 2006 +0100 9617:5802713c159b

(XEN) Console output is synchronous.
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009ac00 (usable)
(XEN)  000000000009ac00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000009ff49a80 (usable)
(XEN)  000000009ff49a80 - 000000009ff8a880 (ACPI data)
(XEN)  000000009ff8a880 - 00000000a0000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000fe0000000 (usable)
(XEN) System RAM: 63486MB (65010572kB)
(XEN) Xen heap: 12MB (12600kB)
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) found SMP MP-table at 0009ad40
(XEN) DMI 2.3 present.
(XEN) DMI not present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 IBM                                   ) @ 0x00000000000fdcf0
(XEN) ACPI: RSDT (v001 IBM    EXA01ZEU 0x00001000 IBM  0x45444f43) @ 0x000000009ff8a800
(XEN) ACPI: FADT (v001 IBM    EXA01ZEU 0x00001000 IBM  0x45444f43) @ 0x000000009ff8a780
(XEN) ACPI: MADT (v001 IBM    EXA01ZEU 0x00001000 IBM  0x45444f43) @ 0x000000009ff8a480
(XEN) ACPI: SRAT (v001 IBM    EXA01ZEU 0x00001000 IBM  0x45444f43) @ 0x000000009ff8a0c0
(XEN) ACPI: HPET (v001 IBM    EXA01ZEU 0x00001000 IBM  0x45444f43) @ 0x000000009ff8a080
(XEN) ACPI: DSDT (v001 IBM    EXA01ZEU 0x00001000 INTL 0x20030122) @ 0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) Switched to APIC driver `summit'.
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x10] enabled)
(XEN) Processor #16 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x16] enabled)
(XEN) Processor #22 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
(XEN) Processor #32 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x26] enabled)
(XEN) Processor #38 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x30] enabled)
(XEN) Processor #48 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x36] enabled)
(XEN) Processor #54 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] enabled)
(XEN) Processor #64 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x21] lapic_id[0x46] enabled)
(XEN) Processor #70 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x22] lapic_id[0x50] enabled)
(XEN) Processor #80 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x23] lapic_id[0x56] enabled)
(XEN) Processor #86 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] enabled)
(XEN) Processor #96 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x31] lapic_id[0x66] enabled)
(XEN) Processor #102 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x32] lapic_id[0x70] enabled)
(XEN) Processor #112 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x33] lapic_id[0x76] enabled)
(XEN) Processor #118 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x40] lapic_id[0x80] enabled)
(XEN) Processor #128 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x41] lapic_id[0x86] enabled)
(XEN) Processor #134 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x42] lapic_id[0x90] enabled)
(XEN) Processor #144 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x43] lapic_id[0x96] enabled)
(XEN) Processor #150 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x50] lapic_id[0xa0] enabled)
(XEN) Processor #160 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x51] lapic_id[0xa6] enabled)
(XEN) Processor #166 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x52] lapic_id[0xb0] enabled)
(XEN) Processor #176 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x53] lapic_id[0xb6] enabled)
(XEN) Processor #182 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x60] lapic_id[0xc0] enabled)
(XEN) Processor #192 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x61] lapic_id[0xc6] enabled)
(XEN) Processor #198 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x62] lapic_id[0xd0] enabled)
(XEN) Processor #208 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x63] lapic_id[0xd6] enabled)
(XEN) Processor #214 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x70] lapic_id[0xe0] enabled)
(XEN) Processor #224 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x71] lapic_id[0xe6] enabled)
(XEN) Processor #230 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x72] lapic_id[0xf0] enabled)
(XEN) Processor #240 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x73] lapic_id[0xf6] enabled)
(XEN) Processor #246 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x10] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x11] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x12] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x13] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x20] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x21] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x22] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x23] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x30] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x31] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x32] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x33] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x40] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x41] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x42] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x43] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x50] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x51] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x52] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x53] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x60] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x61] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x62] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x63] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x70] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x71] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x72] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x73] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 15, version 17, address 0xfec00000, GSI 0-35
(XEN) ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
(XEN) IOAPIC[1]: apic_id 14, version 17, address 0xfec01000, GSI 36-71
(XEN) ACPI: IOAPIC (id[0x0d] address[0xfec02000] gsi_base[72])
(XEN) IOAPIC[2]: apic_id 13, version 17, address 0xfec02000, GSI 72-107
(XEN) ACPI: IOAPIC (id[0x0c] address[0xfec03000] gsi_base[108])
(XEN) IOAPIC[3]: apic_id 12, version 17, address 0xfec03000, GSI 108-143
(XEN) ACPI: IOAPIC (id[0x0b] address[0xfec04000] gsi_base[144])
(XEN) IOAPIC[4]: apic_id 11, version 17, address 0xfec04000, GSI 144-179
(XEN) ACPI: IOAPIC (id[0x0a] address[0xfec05000] gsi_base[180])
(XEN) IOAPIC[5]: apic_id 10, version 17, address 0xfec05000, GSI 180-215
(XEN) ACPI: IOAPIC (id[0x09] address[0xfec06000] gsi_base[216])
(XEN) IOAPIC[6]: apic_id 9, version 17, address 0xfec06000, GSI 216-251
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec07000] gsi_base[252])
(XEN) IOAPIC[7]: apic_id 8, version 17, address 0xfec07000, GSI 252-287
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec08000] gsi_base[288])
(XEN) IOAPIC[8]: apic_id 7, version 17, address 0xfec08000, GSI 288-323
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec09000] gsi_base[324])
(XEN) IOAPIC[9]: apic_id 6, version 17, address 0xfec09000, GSI 324-359
(XEN) ACPI: IOAPIC (id[0x05] address[0xfec0a000] gsi_base[360])
(XEN) IOAPIC[10]: apic_id 5, version 17, address 0xfec0a000, GSI 360-395
(XEN) ACPI: IOAPIC (id[0x04] address[0xfec0b000] gsi_base[396])
(XEN) IOAPIC[11]: apic_id 4, version 17, address 0xfec0b000, GSI 396-431
(XEN) ACPI: IOAPIC (id[0x03] address[0xfec0c000] gsi_base[432])
(XEN) IOAPIC[12]: apic_id 3, version 17, address 0xfec0c000, GSI 432-467
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec0d000] gsi_base[468])
(XEN) IOAPIC[13]: apic_id 2, version 17, address 0xfec0d000, GSI 468-503
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec0e000] gsi_base[504])
(XEN) IOAPIC[14]: apic_id 1, version 17, address 0xfec0e000, GSI 504-539
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec0f000] gsi_base[540])
(XEN) IOAPIC[15]: apic_id 0, version 17, address 0xfec0f000, GSI 540-575
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ8 used by override.
(XEN) ACPI: IRQ14 used by override.
(XEN) Enabling APIC mode:  Summit.  Using 16 I/O APICs
(XEN) ACPI: HPET id: 0x10142201 base: 0xfde84000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 3336.302 MHz processor.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU0: Thermal monitoring enabled
(XEN) CPU0: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Leaving ESR disabled.
(XEN) Booting processor 1/6 eip 90000
(XEN) Initializing CPU#1
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU1: Thermal monitoring enabled
(XEN) CPU1: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 2/16 eip 90000
(XEN) Initializing CPU#2
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 8
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU2: Thermal monitoring enabled
(XEN) CPU2: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 3/22 eip 90000
(XEN) Initializing CPU#3
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 11
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU3: Thermal monitoring enabled
(XEN) CPU3: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 4/32 eip 90000
(XEN) Initializing CPU#4
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 16
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#4.
(XEN) CPU4: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU4: Thermal monitoring enabled
(XEN) CPU4: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 5/38 eip 90000
(XEN) Initializing CPU#5
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 19
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#5.
(XEN) CPU5: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU5: Thermal monitoring enabled
(XEN) CPU5: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 6/48 eip 90000
(XEN) Initializing CPU#6
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 24
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#6.
(XEN) CPU6: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU6: Thermal monitoring enabled
(XEN) CPU6: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 7/54 eip 90000
(XEN) Initializing CPU#7
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 27
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#7.
(XEN) CPU7: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU7: Thermal monitoring enabled
(XEN) CPU7: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 8/64 eip 90000
(XEN) Initializing CPU#8
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 32
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#8.
(XEN) CPU8: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU8: Thermal monitoring enabled
(XEN) CPU8: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 9/70 eip 90000
(XEN) Initializing CPU#9
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 35
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#9.
(XEN) CPU9: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU9: Thermal monitoring enabled
(XEN) CPU9: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 10/80 eip 90000
(XEN) Initializing CPU#10
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 40
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#10.
(XEN) CPU10: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU10: Thermal monitoring enabled
(XEN) CPU10: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 11/86 eip 90000
(XEN) Initializing CPU#11
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 43
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#11.
(XEN) CPU11: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU11: Thermal monitoring enabled
(XEN) CPU11: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 12/96 eip 90000
(XEN) Initializing CPU#12
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 48
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#12.
(XEN) CPU12: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU12: Thermal monitoring enabled
(XEN) CPU12: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 13/102 eip 90000
(XEN) Initializing CPU#13
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 51
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#13.
(XEN) CPU13: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU13: Thermal monitoring enabled
(XEN) CPU13: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 14/112 eip 90000
(XEN) Initializing CPU#14
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 56
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#14.
(XEN) CPU14: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU14: Thermal monitoring enabled
(XEN) CPU14: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 15/118 eip 90000
(XEN) Initializing CPU#15
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 59
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#15.
(XEN) CPU15: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU15: Thermal monitoring enabled
(XEN) CPU15: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 16/128 eip 90000
(XEN) Initializing CPU#16
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 64
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#16.
(XEN) CPU16: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU16: Thermal monitoring enabled
(XEN) CPU16: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 17/134 eip 90000
(XEN) Initializing CPU#17
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 67
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#17.
(XEN) CPU17: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU17: Thermal monitoring enabled
(XEN) CPU17: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 18/144 eip 90000
(XEN) Initializing CPU#18
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 72
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#18.
(XEN) CPU18: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU18: Thermal monitoring enabled
(XEN) CPU18: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 19/150 eip 90000
(XEN) Initializing CPU#19
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 75
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#19.
(XEN) CPU19: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU19: Thermal monitoring enabled
(XEN) CPU19: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 20/160 eip 90000
(XEN) Initializing CPU#20
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 80
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#20.
(XEN) CPU20: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU20: Thermal monitoring enabled
(XEN) CPU20: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 21/166 eip 90000
(XEN) Initializing CPU#21
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 83
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#21.
(XEN) CPU21: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU21: Thermal monitoring enabled
(XEN) CPU21: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 22/176 eip 90000
(XEN) Initializing CPU#22
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 88
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#22.
(XEN) CPU22: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU22: Thermal monitoring enabled
(XEN) CPU22: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 23/182 eip 90000
(XEN) Initializing CPU#23
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 91
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#23.
(XEN) CPU23: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU23: Thermal monitoring enabled
(XEN) CPU23: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 24/192 eip 90000
(XEN) Initializing CPU#24
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 96
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#24.
(XEN) CPU24: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU24: Thermal monitoring enabled
(XEN) CPU24: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 25/198 eip 90000
(XEN) Initializing CPU#25
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 99
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#25.
(XEN) CPU25: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU25: Thermal monitoring enabled
(XEN) CPU25: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 26/208 eip 90000
(XEN) Initializing CPU#26
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 104
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#26.
(XEN) CPU26: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU26: Thermal monitoring enabled
(XEN) CPU26: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 27/214 eip 90000
(XEN) Initializing CPU#27
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 107
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#27.
(XEN) CPU27: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU27: Thermal monitoring enabled
(XEN) CPU27: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 28/224 eip 90000
(XEN) Initializing CPU#28
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 112
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#28.
(XEN) CPU28: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU28: Thermal monitoring enabled
(XEN) CPU28: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 29/230 eip 90000
(XEN) Initializing CPU#29
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 115
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#29.
(XEN) CPU29: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU29: Thermal monitoring enabled
(XEN) CPU29: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 30/240 eip 90000
(XEN) Initializing CPU#30
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 120
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#30.
(XEN) CPU30: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU30: Thermal monitoring enabled
(XEN) CPU30: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Booting processor 31/246 eip 90000
(XEN) Initializing CPU#31
(XEN) Leaving ESR disabled.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 123
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#31.
(XEN) CPU31: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU31: Thermal monitoring enabled
(XEN) CPU31: Intel(R) Xeon(TM) MP CPU 3.33GHz stepping 01
(XEN) Total of 32 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... works.
(XEN) checking TSC synchronization across 32 CPUs:
(XEN) CPU#0 had 45507 usecs TSC skew, fixed it up.
(XEN) CPU#1 had 45508 usecs TSC skew, fixed it up.
(XEN) CPU#2 had 45509 usecs TSC skew, fixed it up.
(XEN) CPU#3 had 45509 usecs TSC skew, fixed it up.
(XEN) CPU#4 had 229663 usecs TSC skew, fixed it up.
(XEN) CPU#5 had 229663 usecs TSC skew, fixed it up.
(XEN) CPU#6 had 229660 usecs TSC skew, fixed it up.
(XEN) CPU#7 had 229660 usecs TSC skew, fixed it up.
(XEN) CPU#8 had 228837 usecs TSC skew, fixed it up.
(XEN) CPU#9 had 228832 usecs TSC skew, fixed it up.
(XEN) CPU#10 had 228831 usecs TSC skew, fixed it up.
(XEN) CPU#11 had 228834 usecs TSC skew, fixed it up.
(XEN) CPU#12 had -96931 usecs TSC skew, fixed it up.
(XEN) CPU#13 had -96911 usecs TSC skew, fixed it up.
(XEN) CPU#14 had -96843 usecs TSC skew, fixed it up.
(XEN) CPU#15 had -96946 usecs TSC skew, fixed it up.
(XEN) CPU#16 had -309439 usecs TSC skew, fixed it up.
(XEN) CPU#17 had -309504 usecs TSC skew, fixed it up.
(XEN) CPU#18 had -309385 usecs TSC skew, fixed it up.
(XEN) CPU#19 had -309496 usecs TSC skew, fixed it up.
(XEN) CPU#20 had -177595 usecs TSC skew, fixed it up.
(XEN) CPU#21 had -177595 usecs TSC skew, fixed it up.
(XEN) CPU#22 had -177590 usecs TSC skew, fixed it up.
(XEN) CPU#23 had -177585 usecs TSC skew, fixed it up.
(XEN) CPU#24 had 45646 usecs TSC skew, fixed it up.
(XEN) CPU#25 had 45589 usecs TSC skew, fixed it up.
(XEN) CPU#26 had 45605 usecs TSC skew, fixed it up.
(XEN) CPU#27 had 45640 usecs TSC skew, fixed it up.
(XEN) CPU#28 had 34330 usecs TSC skew, fixed it up.
(XEN) CPU#29 had 34335 usecs TSC skew, fixed it up.
(XEN) CPU#30 had 34329 usecs TSC skew, fixed it up.
(XEN) CPU#31 had 34329 usecs TSC skew, fixed it up.
(XEN) Cyclone: Could not find valid CBAR value.
(XEN) Platform timer is 333.333MHz HPET
(XEN) Brought up 32 CPUs
(XEN) Machine check exception polling timer started.
(XEN) BUG at domain_build.c:256
(XEN) ----[ Xen-3.0.2-2    Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e010:[<ffff83000011a4ef>] construct_dom0+0xaf/0x1660
(XEN) RFLAGS: 0000000000010282   CONTEXT: hypervisor
(XEN) rax: ffff830000172740   rbx: ffff830001000000   rcx: 00000000000068f2
(XEN) rdx: 00000000000028f2   rsi: 0000000000000001   rdi: 000000000000000a
(XEN) rbp: 00000000006810e0   rsp: ffff830000187cd8   r8:  00000000fffffff9
(XEN) r9:  0000000000000001   r10: 00000000ffffffff   r11: ffff830000114880
(XEN) r12: ffff8300001ac920   r13: 0000000000000000   r14: ffff830000fba080
(XEN) r15: 0000000000342e00   cr0: 000000008005003b   cr3: 0000000000102000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e010
(XEN) Xen stack trace from rsp=ffff830000187cd8:
(XEN)    0000000000000000 ffff83000011bdc0 0000000000000000 0000000000000286
(XEN)    0000000000000000 ffff83000019288f ffff830000169a91 0000000000000000
(XEN)    ffff830000114880 ffff8300001b1dc0 0000000000000001 ffff83000011ce5a
(XEN)    0000000000000000 0000000000000286 00000000000000fb ffff828bfffff000
(XEN)    0000000000000020 ffff8300001b2110 ffff830000114880 0000000000000000
(XEN)    0000000000000000 0000000000000001 00000000000008fb 000000000000000f
(XEN)    0000000000000000 0000000000000000 0000000000000000 000000fb00000000
(XEN)    ffff830001682000 ffff830000f9a080 0000000000000296 0000000000000001
(XEN)    0000000000000000 ffff8300001ac920 0000000000342e00 0000000000000001
(XEN)    0000000000001780 0000000000000000 ffff830000f9a080 ffff830000fba080
(XEN)    0000000000000000 0000000000000293 ffff830000fba080 ffff830000168e8c
(XEN)    ffff830000fba080 ffff83000010db50 ffff830000fba080 ffff830000fba080
(XEN)    0000000000000001 0000000000000000 0000000000000000 00000000ffffffff
(XEN)    ffff830000188020 ffff8300001ac920 ffff83000002cd40 0000000001682000
(XEN)    0000000000342e00 ffff830000161e1b 0000000000000000 ffff830000199440
(XEN)    ffff830000021b20 0000000800000000 0000000800000000 000000010000006e
(XEN)    0000000000000003 00000000000002f8 0000000000000000 0000000000000000
(XEN)    0000000000067ed0 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffff8300001002bf 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN)    [<ffff83000011a4ef>] construct_dom0+0xaf/0x1660
(XEN)    [<ffff83000011bdc0>] common_interrupt+0x20/0x30
(XEN)    [<ffff830000114880>] ns16550_putc+0x0/0x10
(XEN)    [<ffff83000011ce5a>] call_function_interrupt+0x2a/0x30
(XEN)    [<ffff830000114880>] ns16550_putc+0x0/0x10
(XEN)    [<ffff83000010db50>] rangeset_new+0x30/0x110
(XEN)    [<ffff830000161e1b>] __start_xen+0x9ab/0xa20
(XEN)    [<ffff8300001002bf>] __high_start+0x94/0x96
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) CPU0 FATAL TRAP: vector = 6 (invalid opcode)
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds.

[-- Attachment #3: Type: text/plain, Size: 137 bytes --]

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

Re: RE: [Xen-users] Xen in a 32 way system

[Ryan Harper]

* Pablo Montesinos <pablomontesinos@gmail.com> [2006-05-31 13:41]:

> (XEN) Total of 32 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> (XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
> (XEN) ...trying to set up timer as Virtual Wire IRQ... works.

I think you need to use the "new ACK" method.  When my x460 boots, the
above section looks like this:

(XEN) Total of 32 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... works.

I think if you add 'ioapic_ack=new' to your xen command line in grub.
I'm not sure if this is available in the testing tree or only in
unstable.  The other thing to try is seeing if the machine boots on
xen-unstable.


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

Re: [Xen-devel] RE: Xen in a 32 way system

[Pablo Montesinos]

I tried the "new ACK" method, no luck.
I'll try xen-unstable. Each reboot takes forever,
I am going nuts :(

thanks,
Pablo

On 5/31/06, Ryan Harper <ryanh@us.ibm.com> wrote:
> * Pablo Montesinos <pablomontesinos@gmail.com> [2006-05-31 13:41]:
>
> > (XEN) Total of 32 processors activated.
> > (XEN) ENABLING IO-APIC IRQs
> > (XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> > (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> > (XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
> > (XEN) ...trying to set up timer as Virtual Wire IRQ... works.
>
> I think you need to use the "new ACK" method.  When my x460 boots, the
> above section looks like this:
>
> (XEN) Total of 32 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> (XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
> (XEN) ...trying to set up timer as Virtual Wire IRQ... works.
>
> I think if you add 'ioapic_ack=new' to your xen command line in grub.
> I'm not sure if this is available in the testing tree or only in
> unstable.  The other thing to try is seeing if the machine boots on
> xen-unstable.
>
>
> --
> Ryan Harper
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> (512) 838-9253   T/L: 678-9253
> ryanh@us.ibm.com
>

Re: RE: [Xen-users] Xen in a 32 way system

[Keir Fraser]

On 31 May 2006, at 20:48, Ryan Harper wrote:

> I think if you add 'ioapic_ack=new' to your xen command line in grub.
> I'm not sure if this is available in the testing tree or only in
> unstable.  The other thing to try is seeing if the machine boots on
> xen-unstable.

The lack of that line of output indicates that the Xen image is too old 
to have the new ack'ing method. 3.0 series has had teh new code for a 
while now. Time to upgrade to 3.0.3!

  -- Keir

Re: [Xen-devel] RE: Xen in a 32 way system

[Pablo Montesinos]

I installed xen-unstable and it seems to solve that problem. However,
I am getting a kernel bug. xen-unstable downloaded the 2.6.16.13
kernel. It is possible to use a 2.6.16?

Thanks,
Pablo

PS: if you enjoy kernel bugs:


Kernel BUG at drivers/xen/core/smpboot.c:224
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.16.13-xen #2
RIP: e030:[<ffffffff802c5d15>] <ffffffff802c5d15>{cpu_initialize_context+514}
RSP: e02b:ffff8800018bca78  EFLAGS: 00010282
RAX: ffffffffffffffea RBX: ffff8800018bca88 RCX: 0000000000000101
RDX: ffff8800018bca88 RSI: 0000000000000020 RDI: 0000000000000000
RBP: ffff8800018bdee8 R08: ffff8800102b5a20 R09: 0000000000000000
R10: ffff8800018bca88 R11: 0000000000000200 R12: 0000000000000020
R13: 0000000000000140 R14: ffff8800102b5860 R15: ffffffff8040be40
FS:  0000000000000000(0000) GS:ffffffff8052f000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 1, threadinfo ffff8800018bc000, task ffff8800018a4760)
Stack: 00000000002fab4f 0000000000000020 0000000000000000 0000000000000000
       0000000000000000 0000000000000000 0000000000000000 0000000000000000
       0000000000000000 0000000000000000
Call Trace: <ffffffff802c5adb>{cpu_bringup+0} <ffffffff8010b758>{divide_error+0}
       <ffffffff80398fa4>{debug+0} <ffffffff80398fc0>{int3+0}
       <ffffffff8010b65c>{overflow+0} <ffffffff8010b678>{bounds+0}
       <ffffffff8010b694>{invalid_op+0}
<ffffffff8010b640>{device_not_available+0}
       <ffffffff8010b6b0>{coprocessor_segment_overrun+0}
<ffffffff8010b6e8>{invalid_TSS+0}
       <ffffffff8010b704>{segment_not_present+0}
<ffffffff8010b720>{stack_segment+0}
       <ffffffff80398fdc>{general_protection+0} <ffffffff80398f88>{page_fault+0}
       <ffffffff8010b774>{spurious_interrupt_bug+0}
<ffffffff8010b608>{coprocessor_error+0}
       <ffffffff8010b73c>{alignment_check+0}
<ffffffff8010b624>{simd_coprocessor_error+0}
       <ffffffff8011b2e8>{ia32_syscall+0}
<ffffffff8010b2a4>{hypervisor_callback+0}
       <ffffffff8010b3a4>{failsafe_callback+0} <ffffffff8010aa94>{system_call+0}
       <ffffffff80564e5f>{smp_prepare_cpus+456} <ffffffff80108084>{init+60}
       <ffffffff8010b532>{child_rip+8}
<ffffffff80275580>{acpi_ds_init_one_object+0}
       <ffffffff80108048>{init+0} <ffffffff8010b52a>{child_rip+0}

Code: 0f 0b 68 e2 61 3d 80 c2 e0 00 48 81 c4 48 14 00 00 5b 41 5c
RIP <ffffffff802c5d15>{cpu_initialize_context+514} RSP <ffff8800018bca78>
 <0>Kernel panic - not syncing: Attempted to kill init!
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
(XEN) Reboot disabled on cmdline: require manual reset

RE: [Xen-devel] RE: Xen in a 32 way system

[Petersson, Mats]

The line you have the BUG in is a VCPUOP_initialize, which ends up in
.../xen/common/domain.c: do_vcpu_op(), where it does essentially the
first thing is a check:
	if ((vcpuid < 0) || (vcpuid >= MAX_VIRT_CPUS))
		return -EINVAL;

And I think this check will fail if vcpuid is 32, unless MAX_VIRT_CPUS
is not the standard value in . RSI is 32 (0x20)

As per this code:
ffff830000106d8c:       83 fe 1f                cmp    $0x1f,%esi
ffff830000106d8f:       41 89 f4                mov    %esi,%r12d
ffff830000106d92:       49 89 d5                mov    %rdx,%r13
ffff830000106d95:       48 8b 58 10             mov    0x10(%rax),%rbx
ffff830000106d99:       48 c7 c0 ea ff ff ff    mov
$0xffffffffffffffea,%rax
ffff830000106da0:       0f 87 9d 01 00 00       ja     ffff830000106f43
<do_vcpu_op+0x1f3>

So it seems like you're trying to start MORE than 32 CPUS to me... Don't
know why... Or is this check bogus? It doesn't look bogus to me... 

By the way, this is a "bug" in XEN-code inside the linux-kernel, so it's
not a because of the general 2.6.16.13 kernel code, and I suspect you'd
hit the same thing with a slightly earlier kernel - although this code
is something I haven't looked much at before - maybe it silently ignored
error-returns from this call before... 

--
Mats

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
> Pablo Montesinos
> Sent: 01 June 2006 17:11
> To: Ryan Harper
> Cc: xen-devel@lists.xensource.com; Uros Trebec; 
> Puthiyaparambil, Aravindh; xen-users@lists.xensource.com
> Subject: Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system
> 
> I installed xen-unstable and it seems to solve that problem. 
> However, I am getting a kernel bug. xen-unstable downloaded 
> the 2.6.16.13 kernel. It is possible to use a 2.6.16?
> 
> Thanks,
> Pablo
> 
> PS: if you enjoy kernel bugs:
> 
> 
> Kernel BUG at drivers/xen/core/smpboot.c:224 invalid opcode: 
> 0000 [1] SMP CPU 0 Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.16.13-xen #2
> RIP: e030:[<ffffffff802c5d15>] 
> <ffffffff802c5d15>{cpu_initialize_context+514}
> RSP: e02b:ffff8800018bca78  EFLAGS: 00010282
> RAX: ffffffffffffffea RBX: ffff8800018bca88 RCX: 0000000000000101
> RDX: ffff8800018bca88 RSI: 0000000000000020 RDI: 0000000000000000
> RBP: ffff8800018bdee8 R08: ffff8800102b5a20 R09: 0000000000000000
> R10: ffff8800018bca88 R11: 0000000000000200 R12: 0000000000000020
> R13: 0000000000000140 R14: ffff8800102b5860 R15: ffffffff8040be40
> FS:  0000000000000000(0000) GS:ffffffff8052f000(0000) 
> knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000
> Process swapper (pid: 1, threadinfo ffff8800018bc000, task 
> ffff8800018a4760)
> Stack: 00000000002fab4f 0000000000000020 0000000000000000 
> 0000000000000000
>        0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
>        0000000000000000 0000000000000000 Call Trace: 
> <ffffffff802c5adb>{cpu_bringup+0} <ffffffff8010b758>{divide_error+0}
>        <ffffffff80398fa4>{debug+0} <ffffffff80398fc0>{int3+0}
>        <ffffffff8010b65c>{overflow+0} <ffffffff8010b678>{bounds+0}
>        <ffffffff8010b694>{invalid_op+0}
> <ffffffff8010b640>{device_not_available+0}
>        <ffffffff8010b6b0>{coprocessor_segment_overrun+0}
> <ffffffff8010b6e8>{invalid_TSS+0}
>        <ffffffff8010b704>{segment_not_present+0}
> <ffffffff8010b720>{stack_segment+0}
>        <ffffffff80398fdc>{general_protection+0} 
> <ffffffff80398f88>{page_fault+0}
>        <ffffffff8010b774>{spurious_interrupt_bug+0}
> <ffffffff8010b608>{coprocessor_error+0}
>        <ffffffff8010b73c>{alignment_check+0}
> <ffffffff8010b624>{simd_coprocessor_error+0}
>        <ffffffff8011b2e8>{ia32_syscall+0}
> <ffffffff8010b2a4>{hypervisor_callback+0}
>        <ffffffff8010b3a4>{failsafe_callback+0} 
> <ffffffff8010aa94>{system_call+0}
>        <ffffffff80564e5f>{smp_prepare_cpus+456} 
> <ffffffff80108084>{init+60}
>        <ffffffff8010b532>{child_rip+8}
> <ffffffff80275580>{acpi_ds_init_one_object+0}
>        <ffffffff80108048>{init+0} <ffffffff8010b52a>{child_rip+0}
> 
> Code: 0f 0b 68 e2 61 3d 80 c2 e0 00 48 81 c4 48 14 00 00 5b 
> 41 5c RIP <ffffffff802c5d15>{cpu_initialize_context+514} RSP 
> <ffff8800018bca78>  <0>Kernel panic - not syncing: Attempted 
> to kill init!
>  (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> (XEN) Reboot disabled on cmdline: require manual reset
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 

Re: RE: [Xen-users] Xen in a 32 way system

[Keir Fraser]

On 1 Jun 2006, at 18:00, Petersson, Mats wrote:

> The line you have the BUG in is a VCPUOP_initialize, which ends up in
> .../xen/common/domain.c: do_vcpu_op(), where it does essentially the
> first thing is a check:
> 	if ((vcpuid < 0) || (vcpuid >= MAX_VIRT_CPUS))
> 		return -EINVAL;
>
> And I think this check will fail if vcpuid is 32, unless MAX_VIRT_CPUS
> is not the standard value in . RSI is 32 (0x20)

Our smpboot.c in Linux should only try to initialise context for cpus 
in cpu_possible_map. And that map is initialised by querying Xen about 
the state of each VCPU. So it's unclear how you can end up getting this 
crash. Looks like it needs some more tracing added...

  -- Keir

Re: [Xen-devel] RE: Xen in a 32 way system

[Pablo Montesinos]

The reason why I wanted to use a 2.6.16 kernel is the following. When
I installed this morning the "vanilla unstable" version I downloaded,
it created only one kernel, 2.6.16.13-xen. I booted the system with
it, and it didn't work well because of some network card, but RHEL
acutally booted. I didnt check the output while it booted, but I
assumed that it was using all the cpus. So I reconfigured the kernel
with my kernel config, and I got the crash.

I am inserting some extra code in XEN to check how many cpus it is
seeing. But this is the first time I look into XEN's code, so I am
going very slow.

Thanks,
Pablo

On 6/1/06, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 1 Jun 2006, at 18:00, Petersson, Mats wrote:
>
> > The line you have the BUG in is a VCPUOP_initialize, which ends up in
> > .../xen/common/domain.c: do_vcpu_op(), where it does essentially the
> > first thing is a check:
> >       if ((vcpuid < 0) || (vcpuid >= MAX_VIRT_CPUS))
> >               return -EINVAL;
> >
> > And I think this check will fail if vcpuid is 32, unless MAX_VIRT_CPUS
> > is not the standard value in . RSI is 32 (0x20)
>
> Our smpboot.c in Linux should only try to initialise context for cpus
> in cpu_possible_map. And that map is initialised by querying Xen about
> the state of each VCPU. So it's unclear how you can end up getting this
> crash. Looks like it needs some more tracing added...
>
>   -- Keir
>
>

RE: [Xen-devel] RE: Xen in a 32 way system

[Petersson, Mats]

Isn't it a bug that we don't check for -EINVAL in the line here:
        for (i = 0; i < NR_CPUS; i++) {
                rc = HYPERVISOR_vcpu_op(VCPUOP_is_up, i, NULL);
                if (rc == -ENOENT)
                        break;
                cpu_set(i, cpu_possible_map);
        }

If NR_CPUS in Linux is bigger than 32, then rc = -EINVAL, not -ENOENT
when it returns from the vcpu_op, because the first check is to see if
vcpuid is >=32...

Checking if (rc < 0) would be better, I should think... 
		 

--
Mats 

> -----Original Message-----
> From: Pablo Montesinos [mailto:pablomontesinos@gmail.com] 
> Sent: 01 June 2006 18:30
> To: Keir Fraser
> Cc: Petersson, Mats; Uros Trebec; 
> xen-devel@lists.xensource.com; Puthiyaparambil, Aravindh; 
> Ryan Harper; xen-users@lists.xensource.com
> Subject: Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system
> 
> The reason why I wanted to use a 2.6.16 kernel is the 
> following. When I installed this morning the "vanilla 
> unstable" version I downloaded, it created only one kernel, 
> 2.6.16.13-xen. I booted the system with it, and it didn't 
> work well because of some network card, but RHEL acutally 
> booted. I didnt check the output while it booted, but I 
> assumed that it was using all the cpus. So I reconfigured the 
> kernel with my kernel config, and I got the crash.
> 
> I am inserting some extra code in XEN to check how many cpus 
> it is seeing. But this is the first time I look into XEN's 
> code, so I am going very slow.
> 
> Thanks,
> Pablo
> 
> On 6/1/06, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> >
> > On 1 Jun 2006, at 18:00, Petersson, Mats wrote:
> >
> > > The line you have the BUG in is a VCPUOP_initialize, 
> which ends up 
> > > in
> > > .../xen/common/domain.c: do_vcpu_op(), where it does 
> essentially the 
> > > first thing is a check:
> > >       if ((vcpuid < 0) || (vcpuid >= MAX_VIRT_CPUS))
> > >               return -EINVAL;
> > >
> > > And I think this check will fail if vcpuid is 32, unless 
> > > MAX_VIRT_CPUS is not the standard value in . RSI is 32 (0x20)
> >
> > Our smpboot.c in Linux should only try to initialise 
> context for cpus 
> > in cpu_possible_map. And that map is initialised by 
> querying Xen about 
> > the state of each VCPU. So it's unclear how you can end up getting 
> > this crash. Looks like it needs some more tracing added...
> >
> >   -- Keir
> >
> >
> 
> 

Re: RE: [Xen-users] Xen in a 32 way system

[Keir Fraser]

On 1 Jun 2006, at 18:59, Petersson, Mats wrote:

> Isn't it a bug that we don't check for -EINVAL in the line here:
>         for (i = 0; i < NR_CPUS; i++) {
>                 rc = HYPERVISOR_vcpu_op(VCPUOP_is_up, i, NULL);
>                 if (rc == -ENOENT)
>                         break;
>                 cpu_set(i, cpu_possible_map);
>         }
>
> If NR_CPUS in Linux is bigger than 32, then rc = -EINVAL, not -ENOENT
> when it returns from the vcpu_op, because the first check is to see if
> vcpuid is >=32...
>
> Checking if (rc < 0) would be better, I should think...

Yes, the current code is rather mad. I'll fix it.

  -- Keir

RE: [Xen-devel] RE: Xen in a 32 way system

[Petersson, Mats]

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
> Sent: 01 June 2006 19:09
> To: Petersson, Mats
> Cc: xen-devel@lists.xensource.com; Puthiyaparambil, Aravindh; 
> Uros Trebec; Ryan Harper; xen-users@lists.xensource.com; 
> Pablo Montesinos
> Subject: Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system
> 
> 
> On 1 Jun 2006, at 18:59, Petersson, Mats wrote:
> 
> > Isn't it a bug that we don't check for -EINVAL in the line here:
> >         for (i = 0; i < NR_CPUS; i++) {
> >                 rc = HYPERVISOR_vcpu_op(VCPUOP_is_up, i, NULL);
> >                 if (rc == -ENOENT)
> >                         break;
> >                 cpu_set(i, cpu_possible_map);
> >         }
> >
> > If NR_CPUS in Linux is bigger than 32, then rc = -EINVAL, 
> not -ENOENT 
> > when it returns from the vcpu_op, because the first check 
> is to see if 
> > vcpuid is >=32...
> >
> > Checking if (rc < 0) would be better, I should think...
> 
> Yes, the current code is rather mad. I'll fix it.

Of course, if NR_CPUS is 32, it shouldn't matter... 

Pablo, can you check the CONFIG_NR_CPUS in your .config for your
linux-2.6.16.13-xen? As in my system, NR_CPUS = 32.. 

--
Mats
> 
>   -- Keir
> 
> 
> 

Re: [Xen-devel] RE: Xen in a 32 way system

[Pablo Montesinos]

hat tip for you... It is booting, I am still not able to run xend with
more than 4 procs, but that's a complete different story.
Ryan: did you do anything special to load configure xend? it just
hangs as soon as I enable more than 1 chassis

Thank you very much to all of you guys!
Pablo

On 6/1/06, Petersson, Mats <Mats.Petersson@amd.com> wrote:
> > -----Original Message-----
> > From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
> > Sent: 01 June 2006 19:09
> > To: Petersson, Mats
> > Cc: xen-devel@lists.xensource.com; Puthiyaparambil, Aravindh;
> > Uros Trebec; Ryan Harper; xen-users@lists.xensource.com;
> > Pablo Montesinos
> > Subject: Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system
> >
> >
> > On 1 Jun 2006, at 18:59, Petersson, Mats wrote:
> >
> > > Isn't it a bug that we don't check for -EINVAL in the line here:
> > >         for (i = 0; i < NR_CPUS; i++) {
> > >                 rc = HYPERVISOR_vcpu_op(VCPUOP_is_up, i, NULL);
> > >                 if (rc == -ENOENT)
> > >                         break;
> > >                 cpu_set(i, cpu_possible_map);
> > >         }
> > >
> > > If NR_CPUS in Linux is bigger than 32, then rc = -EINVAL,
> > not -ENOENT
> > > when it returns from the vcpu_op, because the first check
> > is to see if
> > > vcpuid is >=32...
> > >
> > > Checking if (rc < 0) would be better, I should think...
> >
> > Yes, the current code is rather mad. I'll fix it.
>
> Of course, if NR_CPUS is 32, it shouldn't matter...
>
> Pablo, can you check the CONFIG_NR_CPUS in your .config for your
> linux-2.6.16.13-xen? As in my system, NR_CPUS = 32..
>
> --
> Mats
> >
> >   -- Keir
> >
> >
> >
>
>

Re: RE: [Xen-users] Xen in a 32 way system

[Ryan Harper]

* Pablo Montesinos <pablomontesinos@gmail.com> [2006-06-01 15:40]:
> hat tip for you... It is booting, I am still not able to run xend with
> more than 4 procs, but that's a complete different story.
> Ryan: did you do anything special to load configure xend? it just
> hangs as soon as I enable more than 1 chassis

No, I've done nothing special.  One of the quirks of our network is that
when xend comes up, it messes with the ethernet interface names and sets
up the bridging.  If I manually start xend via ssh, that ssh session
hangs.  I don't think that is a hardware or software issue, more of an
issue with our lab infrastructure.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

RE: RE: [Xen-users] Xen in a 32 way system

[Puthiyaparambil, Aravindh]

> hat tip for you... It is booting, I am still not able to run xend with
> more than 4 procs, but that's a complete different story.
> Ryan: did you do anything special to load configure xend? it just
> hangs as soon as I enable more than 1 chassis

Are you on the latest changeset? Changeset 10240 fixed a networking
issue. We were having problems on our systems that did not have a
default gateway defined. Though your problem could be something totally
different.

Aravindh