From: "Rinaldi J. Montessi" <rinaldij@adelphia.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: APIC revisited
Date: Mon, 01 Oct 2001 18:56:16 -0400 [thread overview]
Message-ID: <3BB8F490.4638A81E@adelphia.net> (raw)
I realize that this is a FAQ item, but the information contained therein
is a bit sparse. I have an Abitbp6 motherboard with dual celerons 533's
not overclocked. The bus is 66mhz.
My boot params are (from dmesg)
Kernel command line: BOOT_IMAGE=linux2410 ro root=2203
BOOT_FILE=/boot/vmlinuz-2.4.10 hdc=ide-scsi noapic
The BIOS is set for MPS 1.1
These are both recommended in the FAQ (as is trashing the Abit mobo, but
that is not feasible at the present time).
I am of the impression that with the noapic parameter all calls are to
be handled via CPU0, yet I am getting several errors on CPU1 as well.
uptime
4:28pm up 4 days, 17:50, 4 users, load average: 0.00, 0.00, 0.00
/proc/interrupts
CPU0 CPU1
0: 40989069 0 XT-PIC timer
1: 64603 0 XT-PIC keyboard
2: 0 0 XT-PIC cascade
3: 663114 0 XT-PIC eth1
7: 230556 0 XT-PIC soundblaster
8: 1 0 XT-PIC rtc
9: 2735 0 XT-PIC eth0
10: 720950 0 XT-PIC ide2, ide3
12: 2096913 0 XT-PIC PS/2 Mouse
14: 705487 0 XT-PIC ide0
15: 5 0 XT-PIC ide1
NMI: 0 0
LOC: 40988011 40988007
ERR: 97
MIS: 0
The errors are fairly divided between CPU0 and CPU1 54/43 per dmesg,
although this seems to indicate otherwise.
The last series of errors is fairly representative:
APIC error on CPU0: 02(04)
APIC error on CPU1: 04(08)
APIC error on CPU1: 08(08)
APIC error on CPU0: 04(04)
APIC error on CPU0: 04(02)
APIC error on CPU0: 02(02)
Can I assume there is no kernel solution to this problem; and is there a
way for me to quantify potential/probable file corruption?
Thanks,
Rinaldi
--
By all means marry. If you get a good wife you will become happy,
and if you get a bad one you will become a philosopher. --Socrates
next reply other threads:[~2001-10-01 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 22:56 Rinaldi J. Montessi [this message]
2001-10-01 22:59 ` APIC revisited Benjamin LaHaise
2001-10-02 2:01 ` Keith Owens
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=3BB8F490.4638A81E@adelphia.net \
--to=rinaldij@adelphia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox