I don't think that is the "harmless" error message mentioned in the release notes as that had to do with the "crash kernel".
I saw this same error on a Dell AMD system. It seems the motherboard in that system didn't do ACPI IRQ routing as the kernel expected and experienced a lot of random problems until "acpi=noirq" was passed as a kernel option to disable ACPI IRQ routing defaulting back to the APIC IRQ routing. If that still gives you problems then you may need to use "irq=poll" which forces the kernel to poll for IRQ changes.
-Ross
----- Original Message ----- From: centos-bounces@centos.org centos-bounces@centos.org To: CentOS mailing list centos@centos.org Sent: Wed Feb 06 08:03:47 2008 Subject: Re: [CentOS] Re: system gets suspended automatically!
On Wed, 2008-02-06 at 21:48 +0900, Chandra wrote:
=========================================================== AN ERROR IS SHOWING UP AT BOOT TIME. It seems to be a BUG: ============================================================ Memory for crash kernel (0x0 to 0x0) notwithin permissible range ..MP-BIOS bug: 8254 timer not connected to IO-APIC Red Hat nash version 5.1.19.6 starting Welcome to CentOS release 5 (Final) .... ..... and continues normal booting.
Any idea how to deal with it. Please not that it has 4 CPUs.
Thanks a lot,
- Chandra
Check the Release Notes. It is apparently harmless. I see it on all my CentOS 5.1 machines.
B.J.
Ubuntu 7.10, Linux 2.6.22-14-generic unknown 08:02:44 up 21:42, 2 users, load average: 0.15, 0.22, 0.16
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.