All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Dvorak <dvorakv@vdsoft.org>
To: linux-kernel@vger.kernel.org
Subject: APIC error on CPUx
Date: Mon, 22 May 2006 09:38:07 +0200	[thread overview]
Message-ID: <44716A5F.3070208@vdsoft.org> (raw)

Hello to all,

after mailserver installation im getting these messages from kernel:

APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU0: 00(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)

Approximatelly from 2 to 5 messages per 24 hours.

Linux requisities:
Debian 3.1
Linux mailserver 2.6.8-3-686-smp #1 SMP Thu Feb 9 07:05:39 UTC 2006 i686
GNU/Linux

Hardware:
Intel SR1200


Solution from google ?
 "upgrade BIOS firmware"  - but  Im sure the BIOS is the latest.


How serious is this problem ? Does some patch exist to workaround APIC
errors ?
What is the sense of putting "noapic and nolapic" parameters into the
cmdline ? ( Can these parameters cause performance decreasing ? )

Thank you !

Vladimir Dvorak



             reply	other threads:[~2006-05-22  7:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22  7:38 Vladimir Dvorak [this message]
2006-05-22 11:15 ` APIC error on CPUx Andi Kleen
2006-05-22 11:58   ` Vladimir Dvorak
2006-05-22 12:03     ` Andi Kleen
2006-05-22 12:19       ` Vladimir Dvorak
2006-05-22 12:31         ` Jan Engelhardt
2006-05-22 12:54         ` Andi Kleen
2006-05-22 13:13           ` Xavier Bestel
2006-05-22 19:44         ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2006-05-24  5:15 Brown, Len
2006-05-24  8:10 ` Mikael Pettersson
2006-05-23 20:16 Brown, Len
2006-05-23 20:37 ` Vladimir Dvorak
2006-05-25 11:51   ` Jan Engelhardt
2006-05-22 14:47 Brown, Len
2006-05-22 14:50 ` Andi Kleen
2006-05-23  6:44 ` Vladimir Dvorak
2002-01-13 12:51 Teodor Iacob

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=44716A5F.3070208@vdsoft.org \
    --to=dvorakv@vdsoft.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.