From: Jason <xen@jasonandjessi.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-users@lists.xensource.com, Jason <xen@jasonandjessi.com>,
xen-devel@lists.xensource.com,
Hans-Christian Armingeon <johnny@wh-netz.de>
Subject: Re: [Xen-devel] (XEN) APIC error on CPU0: 04(40)
Date: Thu, 23 Mar 2006 11:44:46 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.63.0603231144320.1627@localhost> (raw)
In-Reply-To: <E1FMSzn-0007S7-00@mta1.cl.cam.ac.uk>
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
>>
>
>
next prev parent reply other threads:[~2006-03-23 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 8:07 (XEN) APIC error on CPU0: 04(40) Hans-Christian Armingeon
2006-03-22 17:36 ` [Xen-devel] " Jason
2006-03-23 15:34 ` [Xen-users] " Hans-Christian Armingeon
2006-03-23 16:49 ` Keir Fraser
2006-03-23 17:44 ` Jason [this message]
2006-03-23 17:58 ` [Xen-devel] " Jason
2006-03-23 17:52 ` Keir Fraser
2006-03-23 18:42 ` [Xen-devel] " Jason
2006-03-23 18:07 ` Keir Fraser
2006-03-23 19:08 ` Jason
2006-03-23 22:27 ` Hans-Christian Armingeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0603231144320.1627@localhost \
--to=xen@jasonandjessi.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=johnny@wh-netz.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.