From: "M. Ghaeini" <mohammad@cerberian.com>
To: linux-newbie@vger.kernel.org
Subject: APIC problem on kernel Kernel 2.4.18
Date: Fri, 10 Oct 2003 11:56:08 -0600 [thread overview]
Message-ID: <3F86F2B8.2080308@cerberian.com> (raw)
Hello,
I am running RedHat 7.3 with the SMP kernel 2.4.18 on IBM-x360 hardware,
with 6GB memory and 2x1.6GHz Xeon CPUs. This server panic-ed with the
following message:
mp-bios bug: 8254 time not connected to io-apic
Kernel panic io-apic + timer doesn't work pester mingo@redhat.com
I also found these message:
WARNING: MP table in the EBDA can be UNSAFE, contact
linux-smp@vger.kernel.org if you experience SMP problems!
WARNING: unexpected IO-APIC, please mail to linux-smp@vger.kernel.org
in the syslog.
Has anyone else seen these messages? Is there a patch for this problem?
Thanks in advance.
-Ghaeini
-
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:[~2003-10-10 17:56 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=3F86F2B8.2080308@cerberian.com \
--to=mohammad@cerberian.com \
--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