From: "Steve Lee" <steve@tuxsoft.com>
To: "'Jan Dittmer'" <j.dittmer@portrix.net>, <linux-kernel@vger.kernel.org>
Subject: RE: APIC error on CPU1: 00(02) && APIC error on CPU0: 00(02)
Date: Thu, 10 Jun 2004 13:57:47 -0500 [thread overview]
Message-ID: <000c01c44f1c$d6b1ed80$8119fea9@pluto> (raw)
In-Reply-To: <40C8A3F1.7020007@portrix.net>
They are genuine AMD Athlon 1900 MPs (never over-clocked) on a Giga-byte
7DPXDW-P. The only time these errors seem to occur is when the system
is under heavy disk activity. Could there be a bug with the APIC timer?
This motherboard has two ide-controllers on board. I've noticed in the
log:
Enabling APIC mode: Flat. Using 1 I/O APICs
Is this correct, or should it be 2 I/O APICs?
I'm really fishing for answers. I'd like to know if there really is
something wrong with my system (although it still seems rock stable) or
is this possible a kernel bug?
I'm currently using 2.6.7-rc3 compiled with gcc 3.4.0.
Thanks,
Steve
-----Original Message-----
From: Jan Dittmer [mailto:j.dittmer@portrix.net]
Sent: Thursday, June 10, 2004 1:10 PM
To: Steve Lee
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC error on CPU1: 00(02) && APIC error on CPU0: 00(02)
Steve Lee wrote:
> APIC error on CPU1: 00(02)
> APIC error on CPU0: 00(02)
Is this a Dual AMD Platform? If yes, are this real MPs or just modded
XPs? I've had this kind of error for years on a dual AMD with modded XPs
on a Tyan 2460 - until now, no processor broke down. The APIC is very
picky on this board, judging different posts from the internet.
Jan
next prev parent reply other threads:[~2004-06-10 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 17:53 APIC error on CPU1: 00(02) && APIC error on CPU0: 00(02) Steve Lee
2004-06-10 18:09 ` Jan Dittmer
2004-06-10 18:57 ` Steve Lee [this message]
2004-06-10 19:05 ` Mikael Pettersson
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='000c01c44f1c$d6b1ed80$8119fea9@pluto' \
--to=steve@tuxsoft.com \
--cc=j.dittmer@portrix.net \
--cc=linux-kernel@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.