public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Cumming <bodnar42@phalynx.dhs.org>
To: swsnyder@home.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Thu, 3 Jan 2002 13:47:24 -0800	[thread overview]
Message-ID: <E16MFhs-00046N-00@phalynx> (raw)
In-Reply-To: <20020103195551.BEHH23959.femail47.sdc1.sfba.home.com@there>
In-Reply-To: <20020103195551.BEHH23959.femail47.sdc1.sfba.home.com@there>

On January 3, 2002 11:55, Steve Snyder wrote:
> I just noticed the following events in my system log:
>
>   Jan  3 14:03:39 mercury kernel: APIC error on CPU1: 00(02)
>   Jan  3 14:03:39 mercury kernel: APIC error on CPU0: 00(02)
>
> Below I've listed the CPU/APIC-related parts of my system start-up.

I occasionaly get the same errors on my UP XP1800+ on a KT133A MB, except 
they look like this:
APIC error on CPU0: 08(02)
APIC error on CPU0: 02(08)

uname -a:
Linux phalynx 2.4.17 #8 Wed Dec 26 20:41:16 PST 2001 i686 unknown

/proc/interrupts:
           CPU0
  0:   66440674    IO-APIC-edge  timer
  1:     378128    IO-APIC-edge  keyboard
  2:          0          XT-PIC  cascade
  8:          2    IO-APIC-edge  rtc
  9:   13768184   IO-APIC-level  eth0
 10:        131   IO-APIC-level  usb-uhci, usb-uhci
 11:   22007511   IO-APIC-level  EMU10K1
 12:   10497666    IO-APIC-edge  PS/2 Mouse
 14:    3717339    IO-APIC-edge  ide0
 15:      18254    IO-APIC-edge  ide1
NMI:          0
LOC:   66439861
ERR:         45
MIS:          0

  parent reply	other threads:[~2002-01-03 21:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 19:55 "APIC error on CPUx" - what does this mean? Steve Snyder
2002-01-03 20:10 ` listmail
2002-01-03 21:47 ` Ryan Cumming [this message]
2002-01-03 22:38 ` Alan Cox
2002-01-03 23:21   ` Pozsar Balazs
2002-01-07 10:17   ` Chris Wedgwood
  -- strict thread matches above, loose matches on Subject: below --
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=E16MFhs-00046N-00@phalynx \
    --to=bodnar42@phalynx.dhs.org \
    --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