From: Erik Mouw <mouw@nl.linux.org>
To: sofia.munozvelez@telefonica.es
Cc: linux-smp@vger.kernel.org
Subject: Re: aid about kernel release
Date: Wed, 9 Jan 2008 00:38:03 +0100 [thread overview]
Message-ID: <20080108233803.GA18621@gateway.home> (raw)
In-Reply-To: <OFBAD40CF4.64CA4B0C-ONC12573BE.002C9641-C12573BE.002F6AAD@telefonica.es>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
On Thu, Dec 27, 2007 at 09:36:29AM +0100, sofia.munozvelez@telefonica.es wrote:
> I am working with ESX servers at "Telefonica", located in Spain , Madrid.
> And staring into the file /var/log/dmesg I have already found the following
> message several times:
> "An unexpected IO-APIC was lound.If this kernel release is less than three
> months old please report this to linux-smp@vger.kernel.org".
>
> The version of the ESX is 3.02, and the ouput of "uname -a" is : Linux
> esxc03s01.vmware.adm 2.4.21-47.0.1.ELvmnix #1 Mon Nov 19 18:30:34 PST 2007
> i868 i868 i286 GNU/Linux
2.4.21 is from June 13, 2003, over 4 year old. The "-47.0.1.ELvmnix"
string suggests it's a vendor kernel.
> The vmkernel version is "63195"
>
> Could you tell me what´s wrong or which outputs do you need furthermore?
There's nothing wrong, the kernel just tells you it doesn't know the
IO-APIC and tries to work with it. The warning is not uncommon for old
kernels running on modern hardware.
> Should we upgrade the linux version?
If everything works like it should, you don't have to upgrade (minus
security updates, but it is very well possible your vendor takes care
about that).
Erik
--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-01-08 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 8:36 aid about kernel release sofia.munozvelez
2008-01-08 23:38 ` Erik Mouw [this message]
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=20080108233803.GA18621@gateway.home \
--to=mouw@nl.linux.org \
--cc=linux-smp@vger.kernel.org \
--cc=sofia.munozvelez@telefonica.es \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).