Failure to boot with SMP kernel on x86_64 SMP system ...

Meadows, Andrew AMeadows at BMI.com
Wed Dec 6 01:47:02 UTC 2006


Anything installed recently.... Hardware or software? 

-----Original Message-----
From: redhat-list-bounces at redhat.com <redhat-list-bounces at redhat.com>
To: General Red Hat Linux discussion list <redhat-list at redhat.com>
Sent: Tue Dec 05 18:43:34 2006
Subject: Failure to boot with SMP kernel on x86_64 SMP system ...

Hi, Folks ...

One of my Sun X4100s was hung this morning.  All of them are running  
RHEL 4 update 4. On rebooting with an SMP kernel, it consistently  
hangs after printing the below to the console:

===========================================================

powernow-k8: Found 4 AMD Athlon 64 / Opteron processors (version  
1.50.04-rh)
powernow-k8: MP systems not supported by PSB BIOS structure
powernow-k8: init not cpu 0
powernow-k8: init not cpu 0
powernow-k8: init not cpu 0
ACPI: (supports S0 S1 S4 S5)
ACPI wakeup devices:
PCI1 USB0 ETHR USB1
Unable to handle kernel NULL pointer dereferenceFreeing unused kernel  
memory: 192k freed

============================================================

All of the systems I have are running the same kernel  
(2.6.9-42.0.2.ELsmp), but I also tried booting it with 2.6.9-34.ELsmp  
kernel, with the same exact result.

I can boot it fine using the "non-SMP" kernel, but of course, I wind  
up with only one CPU.

This kernel isn't new to the system; it has been running fine with it  
for a while. I ran the hardware diagnostic DVD, and it found no  
hardware problems.

So, I'm fishing for ideas here ... anyone got any?  Thanks!

	-s-

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************


More information about the redhat-list mailing list