(XEN) APIC error on CPU0: 04(40)

(XEN) APIC error on CPU0: 04(40)

[Hans-Christian Armingeon]

Hi,

I get this error message.

(XEN) APIC error on CPU0: 04(40)

I found a spanish website, that says something about it, but I can't speak spanish.
http://www.guiadohardware.net/comunidade/faq-linux/189865/

As far as I can understand, they recommend the noapic option, or recompile the kernel with smo, or upgrade the Bios.

Is this a serious error?

Johnny

Re: [Xen-devel] (XEN) APIC error on CPU0: 04(40)

[Jason]

I just started getting this error off of last nights build also.

-- 
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet

On Wed, 22 Mar 2006, Hans-Christian Armingeon wrote:

> Hi,
>
> I get this error message.
>
> (XEN) APIC error on CPU0: 04(40)
>
> I found a spanish website, that says something about it, but I can't speak spanish.
> http://www.guiadohardware.net/comunidade/faq-linux/189865/
>
> As far as I can understand, they recommend the noapic option, or recompile the kernel with smo, or upgrade the Bios.
>
> Is this a serious error?
>
> Johnny
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

Re: [Xen-users] Re: (XEN) APIC error on CPU0: 04(40)

[Hans-Christian Armingeon]

Am Mittwoch, 22. März 2006 18:36 schrieb Jason:
> I just started getting this error off of last nights build also.

What can I do to help tracking down this issue?

Is this a serious issue?

Thanks in advance,

Johnny

> 
> -- 
> Jason
> The place where you made your stand never mattered,
> only that you were there... and still on your feet
> 
> On Wed, 22 Mar 2006, Hans-Christian Armingeon wrote:
> 
> > Hi,
> >
> > I get this error message.
> >
> > (XEN) APIC error on CPU0: 04(40)
> >
> > I found a spanish website, that says something about it, but I can't speak spanish.
> > http://www.guiadohardware.net/comunidade/faq-linux/189865/
> >
> > As far as I can understand, they recommend the noapic option, or recompile the kernel with smo, or upgrade the Bios.
> >
> > Is this a serious error?
> >
> > Johnny
> >

Re: (XEN) APIC error on CPU0: 04(40)

[Keir Fraser]

Anyone who is seeing this, please try adding the following line to the
end of function smp_error_interrupt() in xen/arch/x86/apic.c:
    show_registers(regs);

This will get a backtrace and let us see what code path is causing this
APIC error.

If we can start to narrow down the cause I can provide more tracing
and debug code to add as necessary.

 -- Keir

> I just started getting this error off of last nights build also.
> 
> -- 
> Jason
> The place where you made your stand never mattered,
> only that you were there... and still on your feet
> 
> On Wed, 22 Mar 2006, Hans-Christian Armingeon wrote:
> 
> > Hi,
> >
> > I get this error message.
> >
> > (XEN) APIC error on CPU0: 04(40)
> >
> > I found a spanish website, that says something about it, but I can't speak spanish.
> > http://www.guiadohardware.net/comunidade/faq-linux/189865/
> >
> > As far as I can understand, they recommend the noapic option, or recompile the kernel with smo, or upgrade the Bios.
> >
> > Is this a serious error?
> >
> > Johnny
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

Re: [Xen-devel] (XEN) APIC error on CPU0: 04(40)

[Jason]

Building now, I will send the trace shortly

-- 
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet

On Thu, 23 Mar 2006, Keir Fraser wrote:

> Anyone who is seeing this, please try adding the following line to the
> end of function smp_error_interrupt() in xen/arch/x86/apic.c:
>    show_registers(regs);
>
> This will get a backtrace and let us see what code path is causing this
> APIC error.
>
> If we can start to narrow down the cause I can provide more tracing
> and debug code to add as necessary.
>
> -- Keir
>
>> I just started getting this error off of last nights build also.
>>
>> --
>> Jason
>> The place where you made your stand never mattered,
>> only that you were there... and still on your feet
>>
>> On Wed, 22 Mar 2006, Hans-Christian Armingeon wrote:
>>
>>> Hi,
>>>
>>> I get this error message.
>>>
>>> (XEN) APIC error on CPU0: 04(40)
>>>
>>> I found a spanish website, that says something about it, but I can't speak spanish.
>>> http://www.guiadohardware.net/comunidade/faq-linux/189865/
>>>
>>> As far as I can understand, they recommend the noapic option, or recompile the kernel with smo, or upgrade the Bios.
>>>
>>> Is this a serious error?
>>>
>>> Johnny
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>

Re: [Xen-devel] (XEN) APIC error on CPU0: 04(40)

[Jason]

The trace doesn't paste real well, so you can download it at
www.jasonandjessi.com/trace.txt if you are so inclined.



(XEN) APIC error on CPU0: 04(04)
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff1327c3>] mce_checkregs+0x3/0xc0
(XEN) EFLAGS: 00000296   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: ff199da8   ecx: 000008fb   edx:
ff171f10
(XEN) esi: ffbfee80   edi: 7a55ddc3   ebp: 0000000a   esp:
ff171f24
(XEN) cr0: 8005003b   cr3: 3ee74000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs:
e008
(XEN) Xen stack trace from esp=ff171f24:
(XEN)    00000000 ff199da8 ffbfee80 ff123bcd 00000000 ff1327c0
00000000 00000001 
(XEN)    00000001 0000000a 00000000 ff1328b3 00000000 00000000
00000001 00000001 
(XEN)    ffbfee80 7a55ddc3 0000000a ff110c5a 00000000 c7abbe10
00000020 00000000 
(XEN)    00000000 00000000 00000000 00000000 00000001 00000000
bfdcea88 ff10fa82 
(XEN)    c82d2230 c117b5b0 ff1b9080 ff148906 0805af18 0805ae34
e814ec4f 00000001 
(XEN)    00000000 bfdcea88 0805af3c 00ef0000 0804e926 00000073
00000206 bfdce6d0 
(XEN)    0000007b 0000007b 0000007b 00000000 00000000 00000000
ff1b9080 
(XEN) Xen call trace:
(XEN)    [<ff1327c3>] mce_checkregs+0x3/0xc0
(XEN)    [<ff123bcd>] smp_call_function+0x4d/0x60
(XEN)    [<ff1327c0>] mce_checkregs+0x0/0xc0
(XEN)    [<ff1328b3>] mce_work_fn+0x33/0x60
(XEN)    [<ff110c5a>] timer_softirq_action+0xaa/0x140
(XEN)    [<ff10fa82>] do_softirq+0x32/0x50
(XEN)    [<ff148906>] process_softirqs+0x6/0x10
(XEN) 
(XEN) APIC error on CPU0: 04(04)
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff1327c3>] mce_checkregs+0x3/0xc0
(XEN) EFLAGS: 00000296   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: ff199da8   ecx: 000008fb   edx:
ff171f10
(XEN) esi: ffbfee80   edi: f86921e4   ebp: 0000000d   esp:
ff171f24
(XEN) cr0: 8005003b   cr3: 3e689000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs:
e008
(XEN) Xen stack trace from esp=ff171f24:
(XEN)    00010206 ff199da8 ffbfee80 ff123bcd 00000000 ff1327c0
00000000 00000001 
(XEN)    00000001 0000000d 00000000 ff1328b3 00000000 00000000
00000001 00000001 
(XEN)    ffbfee80 f86921e4 0000000d ff110c5a 00000000 0007a120
00000000 00000000 
(XEN)    00000000 00000000 00000000 00000000 c05e57c4 c744da00
c0553e30 ff10fa82 
(XEN)    c744da00 c0553e30 ff1b9080 ff148906 c05e57c4 000000f2
000001f0 c05e57c4 
(XEN)    c744da1c c0553e30 000001f0 000d0000 c02f852d 00000061
00010206 c0553e2c 
(XEN)    00000069 0000007b 0000007b 00000000 00000000 00000000
ff1b9080 
(XEN) Xen call trace:
(XEN)    [<ff1327c3>] mce_checkregs+0x3/0xc0
(XEN)    [<ff123bcd>] smp_call_function+0x4d/0x60
(XEN)    [<ff1327c0>] mce_checkregs+0x0/0xc0
(XEN)    [<ff1328b3>] mce_work_fn+0x33/0x60
(XEN)    [<ff110c5a>] timer_softirq_action+0xaa/0x140
(XEN)    [<ff10fa82>] do_softirq+0x32/0x50
(XEN)    [<ff148906>] process_softirqs+0x6/0x10
(XEN)

-- 
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet

On Thu, 23 Mar 2006, Keir Fraser wrote:

> Anyone who is seeing this, please try adding the following line to the
> end of function smp_error_interrupt() in xen/arch/x86/apic.c:
>    show_registers(regs);
>
> This will get a backtrace and let us see what code path is causing this
> APIC error.
>
> If we can start to narrow down the cause I can provide more tracing
> and debug code to add as necessary.
>
> -- Keir
>
>> I just started getting this error off of last nights build also.
>>
>> --
>> Jason
>> The place where you made your stand never mattered,
>> only that you were there... and still on your feet
>>
>> On Wed, 22 Mar 2006, Hans-Christian Armingeon wrote:
>>
>>> Hi,
>>>
>>> I get this error message.
>>>
>>> (XEN) APIC error on CPU0: 04(40)
>>>
>>> I found a spanish website, that says something about it, but I can't speak spanish.
>>> http://www.guiadohardware.net/comunidade/faq-linux/189865/
>>>
>>> As far as I can understand, they recommend the noapic option, or recompile the kernel with smo, or upgrade the Bios.
>>>
>>> Is this a serious error?
>>>
>>> Johnny
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>

Re: (XEN) APIC error on CPU0: 04(40)

[Keir Fraser]

> The trace doesn't paste real well, so you can download it at
> www.jasonandjessi.com/trace.txt if you are so inclined.

Thanks for that, very useful.

I'm guessing you have a uniprocessor P6 system?

I've checked in what I believe is the correct fix to the unstable
repository. The patch won't go public for a couple of hours, so you
can confirm I found the problem by adding the following lines after
the ASSERT line in on_selected_cpus() in xen/arch/x86/smp.c:
    if ( nr_cpus == 0 )
        return 0;

 -- Keir

Re: [Xen-devel] (XEN) APIC error on CPU0: 04(40)

[Jason]

I am actually on a single proc sempron 64, but I have it
compiled and running as a P6 because I didn't feel that 64bit
support for everything that I run is entirely ready.
I will add that line, rebuild and let you know.

root@hive:~# xm info
system                 : Linux
host                   : hive
release                : 2.6.16-xen0
version                : #1 Thu Mar 23 11:04:24 CST 2006
machine                : i686
nr_cpus                : 1
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 1599
hw_caps                :
078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:0 
0000001
total_memory           : 1008
free_memory            : 351
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_32
platform_params        : virt_start=0xfc000000
xen_changeset          : Tue Mar 21 12:26:38 2006 +0100
9359:045bee6e1ebd
cc_compiler            : gcc version 3.4.3
cc_compile_by          : root
cc_compile_domain      : [unknown]
cc_compile_date        : Thu Mar 23 11:10:39 CST 2006


-- 
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet

On Thu, 23 Mar 2006, Keir Fraser wrote:

>> The trace doesn't paste real well, so you can download it at
>> www.jasonandjessi.com/trace.txt if you are so inclined.
>
> Thanks for that, very useful.
>
> I'm guessing you have a uniprocessor P6 system?
>
> I've checked in what I believe is the correct fix to the unstable
> repository. The patch won't go public for a couple of hours, so you
> can confirm I found the problem by adding the following lines after
> the ASSERT line in on_selected_cpus() in xen/arch/x86/smp.c:
>    if ( nr_cpus == 0 )
>        return 0;
>
> -- Keir
>

Re: (XEN) APIC error on CPU0: 04(40)

[Keir Fraser]

> I am actually on a single proc sempron 64, but I have it
> compiled and running as a P6 because I didn't feel that 64bit
> support for everything that I run is entirely ready.
> I will add that line, rebuild and let you know.

Ah well, I guess the AMD APICs behave like P6 APICs.

 -- Keir

Re: (XEN) APIC error on CPU0: 04(40)

[Jason]

That seems to have fixed it!

-- 
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet

On Thu, 23 Mar 2006, Keir Fraser wrote:

>> I am actually on a single proc sempron 64, but I have it
>> compiled and running as a P6 because I didn't feel that 64bit
>> support for everything that I run is entirely ready.
>> I will add that line, rebuild and let you know.
>
> Ah well, I guess the AMD APICs behave like P6 APICs.
>
> -- Keir
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

Re: (XEN) APIC error on CPU0: 04(40)

[Hans-Christian Armingeon]

Am Donnerstag, 23. März 2006 20:08 schrieb Jason:
> That seems to have fixed it!

Thank you very much!

I've been a bit busy today. I have an Athlon64, which runs xen for amd64.

Johnny