From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: swsnyder@home.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Mon, 7 Jan 2002 23:17:47 +1300 [thread overview]
Message-ID: <20020107101747.GA27284@weta.f00f.org> (raw)
In-Reply-To: <20020103195551.BEHH23959.femail47.sdc1.sfba.home.com@there> <E16MGVH-0001Jl-00@the-village.bc.nu>
In-Reply-To: <E16MGVH-0001Jl-00@the-village.bc.nu>
On Thu, Jan 03, 2002 at 10:38:27PM +0000, Alan Cox wrote:
The occasional APIC error is fine (its logging a hardware event -
probably something that caused enough noise to lose a message and
retry it). The APIC bus is designed to stand these occasional
errors
I'm curious... is there any way to determine what is causing these?
On a UP athlon I have:
cw:tty5@charon(cw)$ uname -r ; uptime && grep ERR /proc/interrupts
2.4.17-rc2
02:09:50 up 4 days, 5:18, 10 users, load average: 0.00, 0.00, 0.00
ERR: 5216
which equates several per minute at times... no funny hardware, not
running X11, and I don't remembering seeing these a while ago on this
same mainboard (but I never really looked either, so that might not be
true).
On a similar Athlon box, which has been up 32 days, I have nearly 45000
events, whilst on a UP P3 which has been up for 124 days I see none,
another UP PII which has been up for 196 days see's none, an SMP P3
which has been up 150 days sees none too... is this an Athlon or VIA
chipset quirk perhaps?
--cw
next prev parent reply other threads:[~2002-01-07 10:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 19:55 Steve Snyder
2002-01-03 20:10 ` listmail
2002-01-03 21:47 ` Ryan Cumming
2002-01-03 22:38 ` Alan Cox
2002-01-03 23:21 ` Pozsar Balazs
2002-01-07 10:17 ` Chris Wedgwood [this message]
2002-01-07 12:29 Petr Vandrovec
2002-01-07 13:08 ` Chris Wedgwood
2002-01-07 13:16 Petr Vandrovec
2002-01-07 13:33 ` Alan Cox
2002-01-07 13:42 ` Chris Wedgwood
2002-01-07 14:40 ` Martin Eriksson
2002-01-07 17:32 ` Steven Walter
2002-01-07 18:20 ` Rene Rebe
2002-01-07 16:58 Petr Vandrovec
2002-01-08 12:12 ` Maciej W. Rozycki
2002-01-08 12:30 ` Chris Wedgwood
2002-01-08 17:35 Petr Vandrovec
2002-01-09 12:41 Petr Vandrovec
2002-01-09 14:34 ` Maciej W. Rozycki
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=20020107101747.GA27284@weta.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=swsnyder@home.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
all inboxes | Powered by JetHome®