Re: [Xen-devel] Upgrade to xen-unstable-rc4

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 31.08.12 at 11:44, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:
> - Messages i haven't seen in dmesg with xen-4.1.3 in combination with 3.6-rc? 
> kernel:
> 
> [    3.333195] tseg: 0000000000
> [    3.333231] CPU: Physical Processor ID: 0
> [    3.333236] CPU: Processor Core ID: 0
> [    3.333240] mce: CPU supports 2 MCE banks
> [    3.333258] LVT offset 0 assigned for vector 0xf9
> [    3.333263] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for 
> vector 0xf9, but the register is already in use for vector 0x0 on this cpu
> [    3.333272] [Firmware Bug]: cpu 0, failed to setup threshold interrupt 
> for bank 4, block 0 (MSR00000413=0xc008000001000000)
> [    3.333281] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for 
> vector 0xf9, but the register is already in use for vector 0x0 on this cpu
> [    3.333290] [Firmware Bug]: cpu 0, failed to setup threshold interrupt 
> for bank 4, block 1 (MSRC0000408=0xc000000001000000)
> [    3.333306] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for 
> vector 0xf9, but the register is already in use for vector 0x0 on this cpu
> [    3.333315] [Firmware Bug]: cpu 0, failed to setup threshold interrupt 
> for bank 4, block 2 (MSRC0000409=0xc000000001000000)
> [    3.333331] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
> [    3.333331] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0
> [    3.333331] tlb_flushall_shift is 0xffffffff
> [    3.334057] ACPI: Core revision 20120711
> 
> The kernel gives these firmware bugs for the other CPUS later on, this is on 
> a AMD Phenom x6, but everything seems to be working so perhaps a minor thing.

This is the usual effect of keeping all sorts of native code enabled
in the pv-ops kernel that tries to control what really is being
controlled by Xen (MCE in this case).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel