Bug 124060 - RHEL 3.0 hangs on IBM x440 with 8 CPUs
Summary: RHEL 3.0 hangs on IBM x440 with 8 CPUs
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Anderson
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-23 16:24 UTC by Billy Newport
Modified: 2007-11-30 22:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-14 20:06:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Billy Newport 2004-05-23 16:24:30 UTC 
Description of problem:
I have an x440 with 8 2.0Ghz MP Xeons and 16GB memory. When I enable 
8 CPUS rather than 4 then after some minutes RHEL crashes to a blank 
screen and I'm forced to reboot.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Enable 8 CPUS
2. Boot, wait 5 mins 
3. Bang
  
Actual results:


Expected results:


Additional info:
Comment 2 john stultz 2004-06-12 01:57:04 UTC 
What kernel version are you using? Are you using the hugemem kernel?
Comment 3 john stultz 2004-08-17 18:43:37 UTC 
Billy: Any chance you could provide the kernel version you are using? 
Also if you are not already, could you try using the hugemem kerel to 
see if the problme persists? 
 
thanks 
-john
Comment 4 john stultz 2004-10-20 22:03:59 UTC 
Is there any way we could get an update on this bug?
Comment 5 john stultz 2004-11-24 21:32:17 UTC 
Billy Newport: Are you still seeing this issue? If so could you 
report the kernel version you are using and if you are not already 
doing so, try the hugemem kernel?
Comment 6 john stultz 2005-09-14 19:15:58 UTC 
This bug is really stale and I suggest it be closed.
Comment 7 Ernie Petrides 2005-09-14 20:06:47 UTC 
Closing due to lack of response from original reporter.
Note You need to log in before you can comment on or make changes to this bug.