From: "Earle R. Nietzel" <nietzel@rhinobox.org>
To: linux-smp@vger.kernel.org
Subject: Re: APIC error on CPU1: 08(08)
Date: 15 Aug 2002 22:39:43 +0200 [thread overview]
Message-ID: <1029443984.27224.25.camel@pc> (raw)
In-Reply-To: <1029422917.29816.32.camel@irongate.swansea.linux.org.uk>
On Thu, 2002-08-15 at 16:48, Alan Cox wrote:
> On Thu, 2002-08-15 at 15:20, Jose Vicente Nunez Zuleta wrote:
> > Greetings,
> >
> > I got also the same problem on several Linux boxes:
> >
> > Aug 14 16:35:30 linux0105 automount[777]: attempting to mount entry /data/prepayModel
> > Aug 14 16:35:30 linux0105 automount[777]: attempting to mount entry /data/commonFiles
> > Aug 14 16:35:30 linux0105 kernel: APIC error on CPU0: 01(01)
> > Aug 14 16:35:30 linux0105 kernel: APIC error on CPU1: 02(02)
I also receive a bunch of these errors on my ABIT BP6 motherboard.
Aug 5 20:43:00 hyperion kernel: APIC error on CPU0: 00(08)
Aug 5 20:43:00 hyperion kernel: APIC error on CPU1: 00(04)
Aug 5 21:41:44 hyperion kernel: APIC error on CPU1: 04(04)
Aug 6 21:53:29 hyperion kernel: APIC error on CPU1: 04(08)
Though this box has been solid even with these errors, it has never
crashed.
Linus also mentioned to me that if I didn't have any trouble I could
disregard these errors.
>
> Different errors. BTW you ought to update the 2.4.7 boxes to the 7.2
> errata kernel.
>
> The long stream of 8/4 is something odder going on
> -
> To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2002-08-15 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 9:00 APIC error on CPU1: 08(08) Lists (lst)
2002-08-15 14:20 ` Jose Vicente Nunez Zuleta
2002-08-15 14:48 ` Alan Cox
2002-08-15 20:39 ` Earle R. Nietzel [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=1029443984.27224.25.camel@pc \
--to=nietzel@rhinobox.org \
--cc=linux-smp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.