Red Hat Bugzilla – Bug 171115
2.6.9-22.ELsmp crashes on unsymetric memory configuration
Last modified: 2012-06-20 12:04:03 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
Sun X4100 (2x Opteron 275) with 10 GB (6 GB on CPU#0, 4 GB on CPU#1) DOES NOT run with or without "numa=off" and kernel 2.6.9-22.ELsmp (hang after "decompressing kernel" or something -- before first kernel message).
Same Sun X4100 with same memory configuration DOES run without "numa=off" with 2.6.9-11.ELsmp.
Same Sun X4100 but with 8 GB (2x 2 GB on #0, 2x 2 GB on #1) DOES run (without "numa=off") with either kernel.
(Since Sun X4100 (nicknamed "Galaxy") is not yet listed as RHEL-certified, RH support won't even look at this issue -- I'm therefore filing it in Bugzilla for future reference.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install a X4100 with Suns Installation CD (RAID driver necessary is not included in RHEL 4 U1), "up2date" it => 2.6.9-11.ELsmp get's updated to 2.6.9-22.ELsmp. Rebooting into 2.6.9-22.ELsmp works fine (with symetric memory configuration)
2. Add 2 DIMMs to CPU0, making the memory configuration unsymetric.
3. Reboot into 2.6.9-22.ELsmp.
Actual Results: Hard hang before the first kernel message. Last message is "decompressing kernel" or something.
Expected Results: No crash, like when booting 2.6.9-11.ELsmp with 4/4 or 6/4 memory config or like booting a 4/4 memory config with 2.6.9-22.ELsmp.
"numa=off" does not change anything with 2.6.9-22.ELsmp and 6/4 memory config.
Try reproducing the original problem and specify "earlyprintk=vga" to see if
anything useful is printed. To redirect to the serial port for capture, boot
with "earlyprintk=ttyS0,115200" (or whichever baudrate you prefer).
User firstname.lastname@example.org's account has been closed
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.