From: Anthony Wright <anthony@overnetdata.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Getting IOAPIC errors in xl dmesg on old hardware
Date: Fri, 23 Sep 2011 13:04:27 +0100 [thread overview]
Message-ID: <4E7C75CB.3010509@overnetdata.com> (raw)
In-Reply-To: <4E7C803E02000078000578A3@nat28.tlf.novell.com>
On 23/09/2011 11:49, Jan Beulich wrote:
>>>> On 23.09.11 at 12:34, Anthony Wright <anthony@overnetdata.com> wrote:
>> I am getting a series of IOAPIC errors in xl dmesg on a Dell OptiPlex
>> GX100 machine (bought in 2000). I also get an error from traps.c which
>> is very similar to the one in the 'Getting mm.c errors from xl dmesg on
>> certain hardware' thread. This happens during system startup with no
>> DomUs running. I have attached the xl dmesg log.
> Seems like the kernel is trying to use IO-APIC despite the LAPIC being
> unavailable. Is this with a pv-ops kernel or a forward port one? Which
> version?
Sorry - this is xen 4.1.1 with vanilla linux 3.0.4
> Also, did you try following what this message
>
> (XEN) Local APIC disabled by BIOS -- you can enable it with "lapic"
I tried putting lapic on the xen command line, and while I got a message
in dmesg saying it had been disabled in the bios, but then re-enabled,
the IOAPIC errors were still present.
next prev parent reply other threads:[~2011-09-23 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 10:34 Getting IOAPIC errors in xl dmesg on old hardware Anthony Wright
2011-09-23 10:49 ` Jan Beulich
2011-09-23 12:04 ` Anthony Wright [this message]
2011-09-23 13:33 ` Konrad Rzeszutek Wilk
2011-09-23 13:39 ` Anthony Wright
2011-09-26 13:59 ` Konrad Rzeszutek Wilk
2011-09-26 15:07 ` Anthony Wright
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=4E7C75CB.3010509@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@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.