public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Youngs <sryoungs@bigpond.net.au>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: Michael Buesch <mbuesch@freenet.de>
Subject: Re: APIC error on CPU0
Date: Tue, 06 Apr 2004 09:03:58 +1000	[thread overview]
Message-ID: <microsoft-free.8765ceyqld.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <200404052336.23585.mbuesch@freenet.de> (Michael Buesch's message of "Mon, 05 Apr 2004 23:35:59 +0200")

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

* Michael Buesch <mbuesch@freenet.de> writes:

  > What does this kernel message mean?

  > Apr  5 23:16:20 lfs kernel: APIC error on CPU0: 60(60)
  > Apr  5 23:16:31 lfs kernel: APIC error on CPU0: 60(60)

My logs are filling up with these as well, although I'm getting
40(40), and the very occasional 00(40).

I'm wondering what it means as well.

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|              Ashes to ashes, dust to dust.               |
|      The proof of the pudding, is under the crust.       |
|------------------------------<sryoungs@bigpond.net.au>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-04-05 23:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 21:35 APIC error on CPU0 Michael Buesch
2004-04-05 23:03 ` Steve Youngs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-06  0:57 Mikael Pettersson
2004-04-06 15:05 ` Michael Buesch
2002-02-11 16:27 Kristian
2002-02-11 16:53 ` Zwane Mwaikambo
2002-02-11 17:29   ` Kristian
2002-02-11 19:11   ` Kristian

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=microsoft-free.8765ceyqld.fsf@eicq.dnsalias.org \
    --to=sryoungs@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    /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