From: Anthony Wright <anthony@overnetdata.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.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 14:39:12 +0100 [thread overview]
Message-ID: <4E7C8C00.2050806@overnetdata.com> (raw)
In-Reply-To: <20110923133341.GD19579@phenom.oracle.com>
On 23/09/2011 14:33, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 23, 2011 at 11:34:25AM +0100, Anthony Wright 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.
>> __ __ _ _ _ _
>> \ \/ /___ _ __ | || | / | / |
>> \ // _ \ '_ \ | || |_ | | | |
>> / \ __/ | | | |__ _|| |_| |
>> /_/\_\___|_| |_| |_|(_)_(_)_|
>>
>> (XEN) Xen version 4.1.1 (@[unknown]) (gcc version 4.4.3 (GCC) ) Wed Sep 21 08:25:36 GMT 2011
>> (XEN) Latest ChangeSet: unavailable
>> (XEN) Bootloader: GNU GRUB 0.97
>> (XEN) Command line:
>> (XEN) Video information:
>> (XEN) VGA is text mode 80x25, font 8x16
>> (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
>> (XEN) Disc information:
>> (XEN) Found 0 MBR signatures
>> (XEN) Found 0 EDD information structures
>> (XEN) Xen-e820 RAM map:
>> (XEN) 0000000000000000 - 00000000000a0000 (usable)
>> (XEN) 00000000000f0000 - 0000000000100000 (reserved)
>> (XEN) 0000000000100000 - 000000001feae000 (usable)
>> (XEN) 000000001feae000 - 0000000020000000 (reserved)
>> (XEN) 00000000ffb00000 - 0000000100000000 (reserved)
>> (XEN) System RAM: 510MB (522552kB)
> Is that right? 512MB?
Yup 512MB
3.4.1 with 2.6.18 works fine on it. 4.4.1 with 3.0.4 also seems to work
fine, though it does seem to use an awful lot of ram (something I'm
going to have a closer look at shortly). It's just that I get these
error messages in 'xl dmesg', and wondered whether I can safely ignore
them, or whether they're indicative of a more serious problem.
next prev parent reply other threads:[~2011-09-23 13:39 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
2011-09-23 13:33 ` Konrad Rzeszutek Wilk
2011-09-23 13:39 ` Anthony Wright [this message]
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=4E7C8C00.2050806@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=konrad.wilk@oracle.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.