public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: APIC error on CPU0
Date: Tue, 6 Apr 2004 17:05:46 +0200	[thread overview]
Message-ID: <200404061705.56852.mbuesch@freenet.de> (raw)
In-Reply-To: <200404060057.i360vtNV012133@harpo.it.uu.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 06 April 2004 02:57, you wrote:
> On Mon, 5 Apr 2004 23:35:59 +0200, Michael Buesch wrote:
> >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)
> >
> >kernel is 2.6.5 with reiser4 patch.
> 
> Send Illegal Vector and Receive Illegal Vector at the same time.
> This is more interesting than the usual 40(40) errors
> (just Receive Illegal Vector), since 60 implies that the
> CPU itself is the source of the bogus vector, whereas 40
> usually implies a crap mainboard.
> 
> My guess is that either your hardware (whatever it is,
> you didn't leave any clues) has problems with a noisy
> APIC bus, broken chipset, or something like that, or
> you enabled ACPI and the ACPI tables are crap.
> 
> In any event, Linux is probably not the source of the
> problem. You may need to run without I/O APIC ("noapic"
> kernel param), no ACPI-based PCI routing ("pci=noapci"),
> or completely without ACPI ("acpi=off").

Ok, thanks for this long explanation.
I think it's possible, that the reason is bad hardware.

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAcsdTFGK1OIvVOP4RAji5AJ9G4ms5U3ktWNDV0zih30XnPAMwxQCgqkxI
5bDE3Tki3a+BSSyWS1kw9+Q=
=Oqt5
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-04-06 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  0:57 APIC error on CPU0 Mikael Pettersson
2004-04-06 15:05 ` Michael Buesch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-05 21:35 Michael Buesch
2004-04-05 23:03 ` Steve Youngs
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=200404061705.56852.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=sryoungs@bigpond.net.au \
    /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