From: Hermann Himmelbauer <dusty@violin.dyndns.org>
To: Andy Arvai <arvai@scripps.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC errors on 2.4.4
Date: Fri, 18 May 2001 16:28:19 +0200 [thread overview]
Message-ID: <3B053183.188C47BD@violin.dyndns.org> (raw)
In-Reply-To: <200105180650.XAA04197@astra.scripps.edu>
Andy Arvai wrote:
>
> Hi,
>
> I'm having IO-APIC errors with 2.4.4. I spent some time searching the
> web to understand more about this problem and I'm still not sure if
> it is a hardware problem on the motherboard or a problem with the
> kernel. I will try the noapic boot option, but are there any
> patches that might fix this? Here are some of the errors I was
> getting:
>
> May 15 22:47:43 rad kernel: APIC error on CPU0: 02(01)
> May 15 22:48:00 rad kernel: APIC error on CPU0: 01(02)
This is a hardware error. I also have a buggy motherboard (586DX) and
experience the same problems. Looke at /proc/interrupts, there you can
see how many errors are detected. The problem is that double errors are
not detected - these can lead to system crashes or block network/isdn
cards.
If there are only a few APIC errors, it is very unlikely that a double
error occurs, if there are very many, the probability is high.
It seems that there are quite a lot of motherboards that have a buggy
APIC.
There is some patch by Alan Cox in the 2.4.4-ac series that does
something about this problem but I do not know what exactly.
The only thing you can do is boot with the "noapic" option, and disable
IO-Interrupts on the second CPU (I assume you have a SMP system?). This
will reduce the amount of errors but there is also a performance
decrease.
Regards,
Hermann
--
,_,
(O,O) "There is more to life than increasing its speed."
( ) -- Gandhi
-"-"--------------------------------------------------------------
prev parent reply other threads:[~2001-05-21 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 6:50 Andy Arvai
2001-05-18 14:28 ` Hermann Himmelbauer [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=3B053183.188C47BD@violin.dyndns.org \
--to=dusty@violin.dyndns.org \
--cc=arvai@scripps.edu \
--cc=dusty@strike.wu-wien.ac.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®