From: Andy Biddle <andyb@chainsaw.com>
To: linux-config@vger.kernel.org
Cc: linux-newbie@vger.kernel.org
Subject: Asus A7M266-D, Linux 2.6.7 and APIC (fwd)
Date: Tue, 20 Jul 2004 22:42:16 -0700 (PDT) [thread overview]
Message-ID: <20040720223850.C80982@sublime.winfirst.com> (raw)
I'm having what I suspect is a newbie-type problem, but I assure you I've
looked around.
I have a dual-proc server that I've recently decided to overhaul. It's an
Asus A7M266-D motherboard. It has been running with dual Athlon MP
1800+s, RedHat and BIOS rev 1003 for at least a year with no real
problems.
First I decided to change the OS to Gentoo. I built the system with no
problem and built a custom kernel based on linux 2.6.7-gentoo-r11.
Everything was working great. Then I changed out the procs and went with
dual Athlon MP 2800+s. To support these, I needed to (according to Asus's
website) upgrade the BIOS to 1011.002 or higher. (Latest is 1011.003, so
that's what I used.)
Now, when I boot to this custom kernel I get about 2 seconds into the boot
process before the system starts spewing constant "APIC error on CPU0:
04(04)" messages. It stops booting at that point.
I've done a little research and it seems that I'm supposed to do a couple
of things:
1. Disable "MPS 1.4 Support" in the BIOS.
2. pass the kernel "noapic" as a parameter.
I've done both of these and I STILL get the APIC messages. (Which leads
me to suspect the "noapic" isn't working or I'm doing it wrong at the very
least.) My line from the grub.conf is:
kernel /kernel-2.6.7-gentoo-r11-smp root=/dev/hda3 noapic acpi=off apm=off
I've build another custom kernel where the only difference is that SMP is
disabled. Sure enough, that works like a champ, but with only the single
CPU.
I've searched through the kernel "make menuconfig" menus and can't see
that I'm missing anything. In fact, I can't even FIND "APIC" options
unless I disable SMP...
I'm just about out of ideas here... Any suggestions?
Thanks,
AndyB
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
reply other threads:[~2004-07-21 5:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040720223850.C80982@sublime.winfirst.com \
--to=andyb@chainsaw.com \
--cc=linux-config@vger.kernel.org \
--cc=linux-newbie@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;
as well as URLs for NNTP newsgroup(s).