From: Josip Rodin <joy@entuzijast.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6
Date: Wed, 24 Mar 2010 09:37:55 +0100 [thread overview]
Message-ID: <20100324083755.GA4305@orion.carnet.hr> (raw)
In-Reply-To: <4BA99ED8.8030209@goop.org>
On Tue, Mar 23, 2010 at 10:10:48PM -0700, Jeremy Fitzhardinge wrote:
>>> And then when I gave up and updated to latest xen/stable for one last try,
>>> that was the biggest d'oh moment - it's fixed :) Was it de67ec8b?
>
> Yes.
OK. Thanks. :)
In the meantime I've verified that the fixed kernel also works on another
32-bit server (a Dell PE750, 2003) where it had also previously crashed on
boot.
>> [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>> [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>> [ 0.030115] ERROR: Unable to locate IOAPIC for GSI 9
>>
>> Is there anything I can do to avoid these?
>
> These are just noise; the kernel thinks it can poke at the IO APICs, but
> they're owned by Xen and so don't exist for the kernel; instead some
> alternate mechanisms come into play to keep the interrupts flowing. At
> some point I hope we can completely remove all trace of the APICs from
> the kernel's sight, so it won't even try to access them and print these
> confused messages.
OK. I just noticed it because it trips up the default check_dmesg Nagios
verification, as it has the word 'error' in it.
--
2. That which causes joy or happiness.
next prev parent reply other threads:[~2010-03-24 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100306115833.GA28039@orion.carnet.hr>
[not found] ` <20100306132711.GK2580@reaktio.net>
2010-03-07 23:31 ` current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6 Josip Rodin
2010-03-08 23:16 ` Jeremy Fitzhardinge
2010-03-09 9:01 ` Josip Rodin
2010-03-11 23:25 ` Yasir Assam
2010-03-11 23:40 ` Boris Derzhavets
2010-03-12 2:22 ` Yasir Assam
2010-03-12 7:14 ` Pasi Kärkkäinen
2010-03-12 11:28 ` Boris Derzhavets
2010-03-12 21:41 ` Yasir Assam
2010-03-11 15:08 ` Josip Rodin
2010-03-11 19:24 ` Pasi Kärkkäinen
2010-03-12 11:41 ` Josip Rodin
2010-03-12 12:09 ` Josip Rodin
2010-03-23 23:18 ` Josip Rodin
2010-03-23 23:22 ` Josip Rodin
2010-03-24 5:10 ` Jeremy Fitzhardinge
2010-03-24 8:37 ` Josip Rodin [this message]
2010-03-12 13:02 ` Pasi Kärkkäinen
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=20100324083755.GA4305@orion.carnet.hr \
--to=joy@entuzijast.net \
--cc=jeremy@goop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).