Red Hat Bugzilla – Bug 188157
Kernel panic right after uncompressing the kernel during CD installation on a dual xeon EM64T machine
Last modified: 2008-07-24 14:41:51 EDT
Description of problem:
Try to install RHEL4 for x86_64 onto a HP ML150 G2 (dual Xeon EM64T CPU, 1GB RAM
(2x512)) with CD. Right after the kernel uncompress (boot into linux), the
installation got a kernel panic, the last line is something like:
"kernel panic: can not sync, oops. "
Somewhere in the screen, one of the functions shown was something like
We tried RHEL4 installer CD for the original release, update 1, and update 3 for
x86_64 distribution, with the same results. All these CDs can boot our dual
opteron server just fine, but panic with em64t server during boot (the setting
of bios of hyperthreading does not matter).
We also tried to boot with RHEL4 for 32-bit, that one works. SuSE ent linux 9
server for x86_64 will also hang. Solaris 10 can be installed. So, it seems that
the 64-bit linux installation all failed.
But if we do the following, the installation can be done:
1) remove the 2nd CPU
2) run the CD installation (only non-SMP kernel is installed), and get RHEL4
3) boot into RHEL4, manually installed the SMP kernel rpm, and set grub to use
SMP kernel by default
4) poweroff, and install the 2nd CPU again, and then boot up
This will get everything installed and running.
It looks like the 2nd CPU causes the kernel panic during the CD booting.
Version-Release number of selected component (if applicable):
Everytime, with RHEL4 for x86_64.
Steps to Reproduce:
1. Insert the Disc 1 of the CD
2. boot server to CD, and at the install screen, just hit enter
After showing kernel uncompressed, panic
show some hardware info, and boot into installation screen
Called HP for support. But they are equally surprised by my news. HP claims that
at least RHEL4 U1 is supported (which also failed anyway for the server I have).
As this happened during the boot, I am not sure how to get the full screen
output here. If someone can give me instruction, I would love to do it.
One more clarification: I am reporting the RHEL4 AS installation. Never tried
the ES and WS version.
I think we resolve the issue. The vendor goofed by sending us a SMP server, the
primary CPU with 2MB cache, and the 2nd CPU with only 1MB cache.
This is causing the boot CD to panic. Removing one of them, or using the CPU
with 1MB cache as the primary CPU, will fix the issue.
Since the customer's last comment indicates that the issue is resolved by
hardware changes, I am closing this.