|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-3.5][linux-pvops-2.6.31.6] Xen BUG at hpet.c:663 triggered by changeset #20430
Hello Yunhong,
Your patch fixes it !
Thanks,
--
Sander
Wednesday, November 25, 2009, 3:24:44 AM, you wrote:
> Hi, Sander, can you please have a try to following patch?
> The reason for this issue is, in hpet_broadcast_enter(), it will return
> directly if timer_deadline==0 without setting the channel, while
> hpet_broadcast_exit() missed the checking.
> As the timer_deadline is only changed in softirq context as per_cpu action,
> it will not be changed between hpet_broadcast_entry()/hpet_broadcast_exit(),
> the checking is safe.
> We considered to use the num_present_cpu() instead of num_possible_cpu() in
> hpet_broadcast_init(), but that seems not so important, since it is already
> limited by HPET's channel number already.
> --jyh
> diff -r d62bede476cb xen/arch/x86/hpet.c
> --- a/xen/arch/x86/hpet.c Mon Nov 23 15:19:38 2009 +0000
> +++ b/xen/arch/x86/hpet.c Tue Nov 24 19:33:01 2009 +0800
> @@ -660,6 +660,9 @@ void hpet_broadcast_exit(void)
> int cpu = smp_processor_id();
> struct hpet_event_channel *ch = per_cpu(cpu_bc_channel, cpu);
> + if (this_cpu(timer_deadline) == 0)
> + return;
> +
> BUG_ON( !ch );
> spin_lock_irq(&ch->lock);
> xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote:
>> Hello Yunhong,
>>
>> I was allready afraid it was only revealed by that changeset,
>> 60 cpu's for free seems to good to be true :(
>> Hope you can find it soon, it crashes the hypervisor
>> frequently and fast (often right after boot).
>> At least I didn't buy my null-modem cable and setup a serial
>> console for nothing :-)
>>
>> Thx,
>>
>> --
>> Sander
>>
>>
>> Tuesday, November 24, 2009, 10:38:24 AM, you wrote:
>>
>>> Have a quick look on the code,
>>
>>> This should be caused by following code in
>> hpet_broadcast_init(). Without changeset 20430, the
>> num_possible_cpus() get 4 on your platform, and is 64 after the
>> change.
>>> I suspect this is a bug just revealed by #20430, I will have
>> a deep look on the hpet logic and discuss with WeiGang to fix it.
>>
>>> if ( num_hpets_used < num_possible_cpus() ) {
>>> hpet_attach_channel = hpet_attach_channel_share;
>>> hpet_detach_channel = hpet_detach_channel_share;
>>> }
>>
>>> Thanks
>>> --jyh
>>
>>
>>> Keir Fraser wrote:
>>>> Cc'ing patch author (Yunhong Jiang).
>>>>
>>>> -- Keir
>>>>
>>>> On 20/11/2009 22:05, "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>
>>>> wrote:
>>>>
>>>>>
>>>>> It seems this bug is triggered by changeset #20430, although it
>>>>> doesn't seem to change hpet.c, so the actual problem will probably
>>>>> be elsewhere. #20429 is booting and working fine for me (at least
>>>>> it doesn't give this bug). changesets #20430 up until tip not, i
>>>>> can trigger this bug every time by compiling xen (make xen), this
>>>>> makes it panic and reboot.
>>>>>
>>>>> --
>>>>> Sander
>>>>>
>>>>>
>>>>>
>>>>> Friday, November 20, 2009, 12:03:59 PM, you wrote:
>>>>>
>>>>>> Hi All,
>>>>>
>>>>>> When booting, the system spontaneus reboots some but not all the
>>>>>> times Serial console output appended.
>>>>>
>>>>>> --
>>>>>> Sander
>>>>>
>>>>>> System: intel Q9400, asus p5q-em do (intel Q45 chipset), 2GB ram
>>>>>
>>>>>
>>>>>> __ __ _____ ____ _
>> _ _
>>>>>> \ \/ /___ _ __ |___ / | ___| _ _ _ __ ___| |_ __ _| |__ |
>>>>>> | ___ \ // _ \ '_ \ |_ \ |___ \ __| | | | '_ \/ __| __/ _`
>>>>>> '_ \| |/ _ \ / \ __/ | | | ___) | ___) |__| |_| | | | \__ \
>>>>>> || (_| _) | | __/ /_/\_\___|_| |_| |____(_)____/ \__,_|_|
>>>>>> _|___/\__\__,_|_.__/|_|\___|
>>>>>>
>>>>>> (XEN) Xen version 3.5-unstable (root@) (gcc version 4.3.2 (Debian
>>>>>> 4.3.2-1.1) ) T hu Nov 19 08:37:49 CET 2009
>>>>>> (XEN) Latest ChangeSet: Sat Nov 14 10:32:59 2009 +0000
>>>>>> 20453:bec27eb6f72c (XEN) Command line: loglvl=all loglvl_guest=all
>>>>>> dom0_mem=512M com1=115200,8n1 co nsole=com1
>>>>>> (XEN) Video information:
>>>>>> (XEN) VGA is text mode 80x25, font 8x16
>>>>>> (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
>>>>>> (XEN) EDID info not retrieved because of reasons unknown (XEN)
>>>>>> Disc information: (XEN) Found 1 MBR signatures
>>>>>> (XEN) Found 1 EDD information structures
>>>>>> (XEN) Xen-e820 RAM map:
>>>>>> (XEN) 0000000000000000 - 000000000009fc00 (usable)
>>>>>> (XEN) 000000000009fc00 - 00000000000a0000 (reserved)
>>>>>> (XEN) 00000000000e4000 - 0000000000100000 (reserved)
>>>>>> (XEN) 0000000000100000 - 000000007ee70000 (usable)
>>>>>> (XEN) 000000007ee70000 - 000000007ee7e000 (ACPI data)
>>>>>> (XEN) 000000007ee7e000 - 000000007eed0000 (ACPI NVS)
>>>>>> (XEN) 000000007eed0000 - 000000007ef00000 (reserved)
>>>>>> (XEN) 00000000fed00000 - 00000000fed01100 (reserved)
>>>>>> (XEN) 00000000fed02000 - 00000000fed14c00 (reserved)
>>>>>> (XEN) 00000000fed20000 - 00000000fed40000 (reserved)
>>>>>> (XEN) 00000000fee00000 - 00000000fee01000 (reserved)
>>>>>> (XEN) 00000000ffe00000 - 0000000100000000 (reserved)
>>>>>> (XEN) System RAM: 2000MB (2048816kB)
>>>>>> (XEN) ACPI: RSDP 000FB080, 0024 (r2 ACPIAM)
>>>>>> (XEN) ACPI: XSDT 7EE70100, 0064 (r1 A_M_I_ OEMXSDT 5000927 MSFT
>>>>>> 97) (XEN) ACPI: FACP 7EE70290, 00F4 (r3 A_M_I_ OEMFACP 5000927
>>>>>> MSFT 97) (XEN) ACPI: DSDT 7EE70440, 841F (r1 A1065 A1065000 0
>>>>>> INTL 20060113) (XEN) ACPI: FACS 7EE7E000, 0040
>>>>>> (XEN) ACPI: APIC 7EE70390, 006C (r1 A_M_I_ OEMAPIC 5000927 MSFT
>>>>>> 97) (XEN) ACPI: MCFG 7EE70400, 003C (r1 A_M_I_ OEMMCFG 5000927
>>>>>> MSFT 97) (XEN) ACPI: OEMB 7EE7E040, 0089 (r1 A_M_I_ AMI_OEM
>>>>>> 5000927 MSFT 97) (XEN) ACPI: HPET 7EE78860, 0038 (r1 A_M_I_
>>>>>> OEMHPET 5000927 MSFT 97) (XEN) ACPI: GSCI 7EE7E0D0, 2024 (r1
>>>>>> A_M_I_ GMCHSCI 5000927 MSFT 97) (XEN) ACPI: DMAR 7EE80100, 0070
>>>>>> (r1 AMI OEMDMAR 1 MSFT 97) (XEN) ACPI: SSDT 7EE810E0, 0A7C
>>>>>> (r1 DpgPmm CpuPm 12 INTL 20060113) (XEN) NUMA turned off (XEN)
>>>>>> Faking a node at 0000000000000000-000000007ee70000 (XEN) Domain
>>>>>> heap initialised (XEN) found SMP MP-table at 000ff780 (XEN) DMI
>>>>>> present. (XEN) Using APIC driver default
>>>>>> (XEN) ACPI: PM-Timer IO Port: 0x808
>>>>>> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
>>>>>> (XEN) ACPI: wakeup_vec[7ee7e00c], vec_size[20]
>>>>>> (XEN) ACPI: Local APIC address 0xfee00000
>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
>>>>>> (XEN) Processor #0 7:7 APIC version 20
>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
>>>>>> (XEN) Processor #1 7:7 APIC version 20
>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
>>>>>> (XEN) Processor #2 7:7 APIC version 20
>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
>>>>>> (XEN) Processor #3 7:7 APIC version 20
>>>>>> (XEN) ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
>>>>>> (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI
>>>>>> 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl
>>>>>> dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
>>>>>> level) (XEN) ACPI: IRQ0 used by override.
>>>>>> (XEN) ACPI: IRQ2 used by override.
>>>>>> (XEN) ACPI: IRQ9 used by override.
>>>>>> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
>>>>>> (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
>>>>>> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 -
>>>>>> 255 (XEN) PCI: Not using MMCONFIG.
>>>>>> (XEN) Using ACPI (MADT) for SMP configuration information
>>>>>> (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN)
>>>>>> Initializing CPU#0 (XEN) Detected 2666.415 MHz processor.
>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>>>>> (XEN) CPU: L2 cache: 3072K
>>>>>> (XEN) CPU: Physical Processor ID: 0
>>>>>> (XEN) CPU: Processor Core ID: 0
>>>>>> (XEN) VMX: Supported advanced features:
>>>>>> (XEN) - APIC MMIO access virtualisation
>>>>>> (XEN) - APIC TPR shadow
>>>>>> (XEN) - Virtual NMI
>>>>>> (XEN) - MSR direct-access bitmap
>>>>>> (XEN) HVM: VMX enabled
>>>>>> (XEN) xsave_init: cpu0: cntxt_max_size: 0x240 and states:
>>>>>> 00000000:00000003 (XEN) xsave_init: using cntxt_size: 0x240 and
>>>>>> states: 00000000:00000003 (XEN) Intel machine check reporting
>>>>>> enabled on CPU#0. (XEN) CPU0: Thermal monitoring enabled (TM2)
>>>>>> (XEN) CMCI: CPU0 has no CMCI support
>>>>>> (XEN) I/O virtualisation disabled
>>>>>> (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>>>>> stepping 0a (XEN) Booting processor 1/1 eip 8c000
>>>>>> (XEN) Initializing CPU#1
>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>>>>> (XEN) CPU: L2 cache: 3072K
>>>>>> (XEN) CPU: Physical Processor ID: 0
>>>>>> (XEN) CPU: Processor Core ID: 1
>>>>>> (XEN) xsave_init: cpu1: cntxt_max_size: 0x240 and states:
>>>>>> 00000000:00000003 (XEN) Intel machine check reporting enabled on
>>>>>> CPU#1. (XEN) CPU1: Thermal monitoring enabled (TM2)
>>>>>> (XEN) CMCI: CPU1 has no CMCI support
>>>>>> (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>>>>> stepping 0a (XEN) Booting processor 2/2 eip 8c000
>>>>>> (XEN) Initializing CPU#2
>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>>>>> (XEN) CPU: L2 cache: 3072K
>>>>>> (XEN) CPU: Physical Processor ID: 0
>>>>>> (XEN) CPU: Processor Core ID: 2
>>>>>> (XEN) xsave_init: cpu2: cntxt_max_size:0x240 and states:
>>>>>> 00000000:00000003 (XEN) Intel machine check reporting enabled on
>>>>>> CPU#2. (XEN) CPU2: Thermal monitoring enabled (TM2)
>>>>>> (XEN) CMCI: CPU2 has no CMCI support
>>>>>> (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>>>>> stepping 0a (XEN) Booting processor 3/3 eip 8c000
>>>>>> (XEN) Initializing CPU#3
>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>>>>> (XEN) CPU: L2 cache: 3072K
>>>>>> (XEN) CPU: Physical Processor ID: 0
>>>>>> (XEN) CPU: Processor Core ID: 3
>>>>>> (XEN) xsave_init: cpu3: cntxt_max_size: 0x240 and states:
>>>>>> 00000000:00000003 (XEN) Intel machine check reporting enabled on
>>>>>> CPU#3. (XEN) CPU3: Thermal monitoring enabled (TM2)
>>>>>> (XEN) CMCI: CPU3 has no CMCI support
>>>>>> (XEN) CPU3: Intl(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>>>>> stepping 0a (XEN) Total of 4 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) checking TSC synchronization across 4 CPUs: passed.
>>>>>> (XEN) Platform timer is 14.318MHz HPET
>>>>>> (XEN) microcode.c:73:d32767 microcode: CPU1 resumed
>>>>>> (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) Brought
>>>>>> up 4 CPUs (XEN) microcode.c:73:d32767 microcode: CPU3 resumed
>>>>>> (XEN) HPET: 8 timers in total, 8 timers will be used for broadcast
>>>>>> (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check
>>>>>> polling timer started. (XEN) *** LOADING DOMAIN 0 ***
>>>>>> (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x821000
>>>>>> (XEN) elf_parse_binary: phdr: paddr=0x1821000 memsz=0xe57f8
>>>>>> (XEN) elf_parse_binary: phdr: paddr=0x1907000 memsz=0x888
>>>>>> (XEN) elf_parse_binary: phdr: paddr=0x1908000 memsz=0x15860
>>>>>> (XEN) elf_parse_binary: phdr: paddr=0x191d860 memsz=0x1a57a0
>>>>>> (XEN) elf_parse_binary: memory: 0x1000000 -> 0x1ac3000
>>>>>> (XEN) elf_xen_parse_note: GUEST_OS = "linux"
>>>>>> (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
>>>>>> (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
>>>>>> (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
>>>>>> (XEN) elf_xen_parse_note: ENTRY = 0xffffffff8191da60
>>>>>> (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81009000
>>>>>> (XEN) elf_xen_parse_note: FEATURES =
>>>>>> "!writable_page_tables|pae_pgdir_above_4gb"
>>>>>> (XEN) elf_xen_parse_note: PAE_MODE = "yes"
>>>>>> (XEN) elf_xen_parse_note: LOADER = "generic"
>>>>>> (XEN) elf_xen_parse_note: unknown xen elf note (0xd)
>>>>>> (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
>>>>>> (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
>>>>>> (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
>>>>>> (XEN) elf_xen_addr_calc_check: addresses:
>>>>>> (XEN) virt_base = 0xffffffff80000000
>>>>>> (XEN) elf_paddr_offset = 0x0
>>>>>> (XEN) virt_offset = 0xffffffff80000000
>>>>>> (XEN) virt_kstart = 0xffffffff81000000
>>>>>> (XEN) virt_kend = 0xffffffff81ac3000
>>>>>> (XEN) virt_entry = 0xffffffff8191da60
>>>>>> (XEN) p2m_base = 0xffffffffffffffff
>>>>>> (XEN) Xen kernel: 64-bit, lsb, compat32
>>>>>> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ac3000
>>>>>> (XEN) PHYSICAL MEMORY ARRANGEMENT:
>>>>>> (XEN) Dom0 alloc.: 0000000074000000->0000000078000000 (114688
>>>>>> pages to be all ocated) (XEN) VIRTUAL MEMORY ARRANGEMENT:
>>>>>> (XEN) Loaded kernel: ffffffff81000000->ffffffff81ac3000
>>>>>> (XEN) Init. ramdisk: ffffffff81ac3000->ffffffff82172a00
>>>>>> (XEN) Phys-Mach map: ffffffff82173000->ffffffff82273000
>>>>>> (XEN) Start info: ffffffff82273000->ffffffff822734b4
>>>>>> (XEN) Page tables: ffffffff82274000->ffffffff82289000
>>>>>> (XEN) Boot stack: ffffffff82289000->ffffffff8228a000
>>>>>> (XEN) TOTAL: ffffffff80000000->ffffffff82400000
>>>>>> (XEN) ENTRY ADDRESS: ffffffff8191da60
>>>>>> (XEN) Dom0 has maximum 4 VCPUs
>>>>>> (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 ->
>>>>>> 0xffffffff81821000 (XEN) elf_load_binary: phdr 1 at
>>>>>> 0xffffffff81821000 -> 0xffffffff819067f8 (XEN) elf_load_binary:
>>>>>> phdr 2 at 0xffffffff81907000 -> 0xffffffff81907888 (XEN)
>>>>>> elf_load_binary: phdr 3 at 0xffffffff81908000 ->
>>>>>> 0xffffffff8191d860 (XEN) elf_load_binary: phdr 4 at
>>>>>> 0xffffffff8191d860 -> 0xffffffff81998000 (XEN) Scrubbing Free
>>>>>> RAM: ..............done. (XEN) Xen trace buffers: disabled (XEN)
>>>>>> Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) *** Serial
>>>>>> input -> DOM0 (type 'CTRL-a' three times to switch input to Xen )
>>>>>> (XEN) Freed 156kB init memory.
>>>>>> mapping kernel into physical memory
>>>>>> Xen: setup ISA identity maps
>>>>>> about to get started...
>>>>>> (XEN) io_apic.c:2251:
>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0
>>>>>> (XEN) ioapic_guest_write: new_entry=00010900
>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>>>>>> IRQ! (XEN) io_apic.c:2251: (XEN) ioapic_guest_write: apic=0,
>>>>>> pin=2, irq=0 (XEN) ioapic_guest_write: new_entry=00010900
>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>>>>>> IRQ! (XEN) irq.c:1444: dom0: pirq 0 or irq 3 already mapped (XEN)
>>>>>> io_apic.c:2251: (XEN) ioapic_guest_write: apic=0, pin=4, irq=4
>>>>>> (XEN) ioapic_guest_write: new_entry=00010900
>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>>>>>> IRQ! (XEN) irq.c:1444: dom0: pirq 0 or irq 5 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 6 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 7 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 8 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 9 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 10 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 11 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 12 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 13 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 14 already mapped
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 15 already mapped
>>>>>> (XEN) allocated vector for irq:16
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 16 already mapped
>>>>>> (XEN) allocated vector for irq:17
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 17 already mapped
>>>>>> (XEN) allocated vector for irq:18
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 18 already mapped
>>>>>> (XEN) allocated vector for irq:19
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 19 already mapped
>>>>>> (XEN) allocated vector for irq:20
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 20 already mapped
>>>>>> (XEN) allocated vector for irq:22
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 22 already mapped
>>>>>> (XEN) allocated vector for irq:23
>>>>>> (XEN) irq.c:1444: dom0: pirq 0 or irq 23 already mapped (XEN)
>>>>>> io_apic.c:2251: (XEN) ioapic_guest_write: apic=0, pin=0, irq=0
>>>>>> (XEN) ioapic_guest_write: new_entry=00000900
>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>>>>>> IRQ! (XEN) io_apic.c:2251: (XEN) ioapic_guest_write: apic=0,
>>>>>> pin=4, irq=4 (XEN) ioapic_guest_write: new_entry=00000904
>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>>>>>> IRQ! (XEN) PCI add device 00:00.0 (XEN) PCI add device 00:01.0
>>>>>> (XEN) PCI add device 00:03.0 (XEN) PCI add device 00:19.0
>>>>>> (XEN) PCI add device 00:1e.0
>>>>>> (XEN) PCI add device 00:1f.0
>>>>>> (XEN) PCI add device 00:1f.2
>>>>>> (XEN) PCI add device 00:1f.3
>>>>>> (XEN) PCI add device 00:1f.5
>>>>>> (XEN) PCI add device 01:00.0
>>>>>> (XEN) PCI add device 01:00.1
>>>>>> (XEN) io_apic.c:2251:
>>>>>> (XEN) ioapic_guest_write: apic=0, pin=4, irq=4
>>>>>> (XEN) ioapic_guest_write: new_entry=00000904
>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>>>>>> IRQ! (XEN) Set CPU acpi_id(1) cpuid(0) Px State info: (XEN)
>>>>>> _PPC: 0 (XEN) cpuid.MWAIT[.eax=40, .ebx=40, .ecx=3, .edx=22220]
>>>>>> (XEN) Monitor-Mwait will be used to enter C-1 state
>>>>>> (XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PSS: state_count=3
>>>>>> (XEN) State0: 2670MHz 89000mW 10us 10us 0x81f 0x81f
>>>>>> (XEN) State1: 2336MHz 76000mW 10us 10us 0x71b 0x71b
>>>>>> (XEN) State2: 2003MHz 63000mW 10us 10us 0x616 0x616
>>>>>> (XEN) _PSD: num_entries=5 rev=0 domain=0 coord_type=254
>>>>>> num_processors=4 (XEN) _PPC: 0 (XEN) xen_pminfo:
>>>>>> @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 0
>>>>>> initialization completed (XEN) Set CPU acpi_id(2) cpuid(1) Px
>>>>>> State info: (XEN) _PPC: 0 (XEN) cpuid.MWAIT[.eax=40, .ebx=40,
>>>>>> .ecx=3, .edx=22220] (XEN) Monitor-Mwait will be used to enter C-1
>>>>>> state (XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PSS: state_count=3
>>>>>> (XEN) State0: 2670MHz 89000mW 10us 10us 0x81f 0x81f
>>>>>> (XEN) State1: 2336MHz 76000mW 10us 10us 0x71b 0x71b
>>>>>> (XEN) State2: 2003MHz 63000mW 10us 10us 0x616 0x616
>>>>>> (XEN) _PSD: num_entries=5 rev=0 domain=0 coord_type=254
>>>>>> num_processors=4 (XEN) _PPC: 0 (XEN) xen_pminfo:
>>>>>> @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 1
>>>>>> initialization completed (XEN) Set CPU acpi_id(3) cpuid(2) Px
>>>>>> State info: (XEN) _PPC: 0 (XEN) cpuid.MWAIT[.eax=40, .ebx=40,
>>>>>> .ecx=3, .edx=22220] (XEN) Monitor-Mwait will be used to enter C-1
>>>>>> state (XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PSS: state_count=3
>>>>>> (XEN) State0: 2670MHz 89000mW 10us 10us 0x81f 0x81f
>>>>>> (XEN) State1: 2336MHz 76000mW 10us 10us 0x71b 0x71b
>>>>>> (XEN) State2: 2003MHz 63000mW 10us 10us 0x616 0x616
>>>>>> (XEN) _PSD: num_entries=5 rev=0 domain=0 coord_type=254
>>>>>> num_processors=4 (XEN) _PPC: 0 (XEN) xen_pminfo:
>>>>>> @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 2
>>>>>> initialization completed (XEN) Set CPU acpi_id(4) cpuid(3) Px
>>>>>> State info: (XEN) _PPC: 0 (XEN) cpuid.MWAIT[.eax=40, .ebx=40,
>>>>>> .ecx=3, .edx=22220] (XEN) Monitor-Mwait will be used to enter C-1
>>>>>> state (XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PCT: descriptor=130, length=12, space_id=127,
>>>>>> bit_width=0, bit_offset=0 , reserved=0, address=0
>>>>>> (XEN) _PSS: state_count=3
>>>>>> (XEN) State0: 2670MHz 89000mW 10us 10us 0x81f 0x81f
>>>>>> (XEN) State1: 2336MHz 76000mW 10us 10us 0x71b 0x71b
>>>>>> (XEN) State2: 2003MHz 63000mW 10us 10us 0x616 0x616
>>>>>> (XEN) _PSD: num_entries=5 rev=0 domain=0 coord_type=254
>>>>>> num_processors=4 (XEN) _PPC: 0 (XEN) xen_pminfo:
>>>>>> @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 3
>>>>>> initialization completed (XEN) Xen BUG at hpet.c:663
>>>>>> (XEN) ----[ Xen-3.5-unstable x86_64 debug=y Not tainted ]----
>>>>>> (XEN) CPU: 3 (XEN) RIP: e008:[<ffff82c480189b81>]
>>>>>> hpet_broadcast_exit+0x4b/0xf2 (XEN) RFLAGS: 0000000000010246
>>>>>> CONTEXT: hypervisor (XEN) rax: ffff82c48025fa88 rbx:
>>>>>> 0000000000000000 rcx: 0000000000000010 (XEN) rdx:
>>>>>> 0000000000006000 rsi: 000000054583d5f5 rdi: ffff82c4802306b0
>>>>>> (XEN) rbp: ffff83007ea37e30 rsp: ffff83007ea37e10 r8:
>>>>>> 0000000000000004 (XEN) r9: ffff83007ea68e68 r10:
>>>>>> ffff83007ea68e68 r11: 0f0f0f0f0f0f0f0f (XEN) r12:
>>>>>> 0000000000000003 r13: 0000000000006000 r14: ffff830076401830
>>>>>> (XEN) r15: 0000000000916ce8 cr0: 000000008005003b cr4:
>>>>>> 00000000000026f0 (XEN) cr3: 000000007ecec000 cr2:
>>>>>> 000000000046e320 (XEN) ds: 002b es: 002b fs: 0000 gs: 0000
>>>>>> ss: e010 cs: e008 (XEN) Xen stack trace from rsp=ffff83007ea37e10:
>>>>>> (XEN) 0000000000000002 ffff82c4802362a0 ffff8300764018c0
>>>>>> ffff830076401830 (XEN) ffff83007ea37ee0 ffff82c48018bbf1
>>>>>> ffff83007ea37ea0 ffff82c48011fd9e (XEN) ffff82c480265080
>>>>>> 00916ce37ea37ed8 ffff82c48011cb6f ffff82c480265100 (XEN)
>>>>>> ffff83007ea2e380 0000000000000003 ffff82c4802362a0
>>>>>> 000000007ea37f28 (XEN) 0000000000000000 0000000000000000
>>>>>> ffff83007ea37ee0 fffff83000000046 (XEN) 0000000000000003
>>>>>> ffff83007ea37f28 ffff82c4802362a0 ffff83007ea37f28 (XEN)
>>>>>> ffff82c48025fa00 ffff82c480236918 ffff83007ea37f20
>>>>>> ffff82c48014ca00 (XEN) ffff83007cefa000 ffff83007ea3e000
>>>>>> 0000000000000003 ffff83007cefa000 (XEN) 00000002314e8a32
>>>>>> ffff82c480265080 ffff83007ea37dc8 0000000000000000 (XEN)
>>>>>> 0000000000000000 0000000000000000 0000000000000000
>>>>>> ffff88001f89bf10 (XEN) ffffffff818fe0a8 0000000000000246
>>>>>> 000000000000000c ffff88001f89be30 (XEN) 0000000000000000
>>>>>> 0000000000000000 ffffffff810093aa 0000000000000000 (XEN)
>>>>>> 00000000deadbeef 00000000deadbeef 0000010000000000
>>>>>> ffffffff810093aa (XEN) 000000000000e033 0000000000000246
>>>>>> ffff88001f89bef8 000000000000e02b (XEN) 5555555555555555
>>>>>> 5555555555555555 5555555555555555 5555555555555555 (XEN)
>>>>>> 5555555500000003 ffff83007ea3e000 (XEN) Xen call trace: (XEN)
>>>>>> [<ffff82c480189b81>] hpet_broadcast_exit+0x4b/0xf2 (XEN)
>>>>>> [<ffff82c48018bbf1>] acpi_processor_idle+0x5f6/0x6b5 (XEN)
>>>>>> [<ffff82c48014ca00>] idle_loop+0x89/0x93 (XEN) (XEN) (XEN)
>>>>>> **************************************** (XEN) Panic on CPU 3:
>>>>>> (XEN) Xen BUG at hpet.c:663 (XEN)
>>>>>> **************************************** (XEN) (XEN) Reboot in
>>>>>> five seconds...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> host : xentest
>>>>>> release : 2.6.31.6
>>>>>> version : #1 SMP Fri Nov 20 02:18:08 CET 2009
>>>>>> machine : x86_64
>>>>>> nr_cpus : 4
>>>>>> nr_nodes : 1
>>>>>> cores_per_socket : 4
>>>>>> threads_per_core : 1
>>>>>> cpu_mhz : 2666
>>>>>> hw_caps :
>>>>>>
>>>>
>> bfebfbff:20100800:00000000:00000940:0408e3fd:00000000:00000001:00000000
>>>>>> virt_caps : hvm
>>>>>> total_memory : 2000
>>>>>> free_memory : 1496
>>>>>> node_to_cpu : node0:0-3
>>>>>> node_to_memory : node0:1496
>>>>>> node_to_dma32_mem : node0:1496
>>>>>> xen_major : 3
>>>>>> xen_minor : 5
>>>>>> xen_extra : -unstable
>>>>>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
>>>>>> hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
>>>>>> xen_scheduler : credit
>>>>>> xen_pagesize : 4096
>>>>>> platform_params : virt_start=0xffff800000000000
>>>>>> xen_changeset : Sat Nov 14 10:32:59 2009 +0000
>>>>>> 20453:bec27eb6f72c xen_commandline : loglvl=all
>>>>>> loglvl_guest=all dom0_mem=512M com1=115200,8n1 console=com1
>>>>>> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
>>>>>> cc_compile_by : root cc_compile_domain :
>>>>>> cc_compile_date : Thu Nov 19 08:37:49 CET 2009
>>>>>> xend_config_format : 4
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best regards,
>>>>> Sander mailto:linux@xxxxxxxxxxxxxx
>>
>>
>>
>> --
>> Best regards,
>> Sander mailto:linux@xxxxxxxxxxxxxx
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
--
Best regards,
Sander mailto:linux@xxxxxxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |