Red Hat Bugzilla – Bug 142579
Viper: install kernel panics on DP system with 4GB all on cpu#2
Last modified: 2013-08-05 21:10:46 EDT
Escalated to Bugzilla from IssueTracker
On a Viper, I have found that if you install 4 GB, or more, of memory
only on the second cpu of a dual cpu system, that the install kernel
panics and reboots the system. This experiment works fine if you use
less than 4 GB in the same configuration. FYI: Viper memory *must* be
loaded in pairs.
The install works fine if you switch the memory over to cpu #1.
I will ship (2) 2 GB sticks of memory to Westford tonight for use in
Event posted 11-22-2004 02:36pm by jeff.burrell with duration of 0.00
Event posted 11-23-2004 05:00pm by jeff.burrell with duration of 0.00
(2) 2GB DDR1 sticks for Viper will ship from HP tonight(11/23)
overnight to Bill Peck's attention.
Adjusting severity to match Issue Tracker.
Larry, could you please link this BZ to the IT ticket? Also, please
provide the oops console output. Thanks.
Event posted 12-14-2004 01:21pm by Daryl with duration of 0.00
Let's aim for an Update 5 fix.
Event posted 12-20-2004 11:28am by kim.jensen with duration of 0.00
I cannot access 142579 so please update Bugzilla ...
RH has 5 dual processor systems
- to duplcate the oops, put 4 GB in the second processor's memory bank.
Here's the latest update on this bug from HP...
Using RHEL 3 U4 gold, I can successfully install and run with 4 1GB
sticks in the second CPU's memory slots, and, of course, nothing in
CPU 0's memory slots.
When I install 4 2GB sticks in the second CPU's memory, the following
1) Can't boot the newly installed U4 image that boots with 4 GB.
Kernel panics and reboots. No messages visible on monitor.
2) Install kernel for U4 panics and reboots. No messages visible on
If I put any memory at all in CPU 0's slots, with 8 GB in CPU 1's
memory, the install kernel is happy and installs properly. The newly
installed kernel boots properly and all is good. Remove the memory
from CPU 0, leaving 8 GB on CPU 1 and the kernel panics.
Why is this in NEEDINFO? Kim responded. Changing to Assigned.
Does the problem occur when "numa=off" is entered on the boot command line?
I strongly suspect that this bug is the RHEL3 equivalent of Bug 160230, and that
the same fix is indicated for RHEL3.
*** Bug 156645 has been marked as a duplicate of this bug. ***
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-37.3.EL).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.