Bug 724856 - IBM system x3690 x5 with Rhel 6.1s default kernel
Summary: IBM system x3690 x5 with Rhel 6.1s default kernel
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-22 02:54 UTC by ben.kaehne
Modified: 2011-08-23 13:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-23 13:19:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description ben.kaehne 2011-07-22 02:54:56 UTC 
Description of problem:
IBM system x3690 x5 with Rhel 6.1s default kernel
I have found an issue in which and IBM system x3690 x5 will hang while trying to load kernel 2.6.32-131.0.15.el6.x86_64.

However I can load a RHEL 6.1 installation with Rhel 6.0s 2.6.32-71.el6.x86_64.

When I try boot into 2.6.32-131.0.15.el6.x86_64 (rhel 6.1s default kernel) the server will hang while trying to load the initrd image.


Version-Release number of selected component (if applicable):
2.6.32-131.0.15.el6.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Obtain x3690 x5
2. Either install rhel 6.1 (does not reach anaconda) or upgrade from 6
3. Envisage freezage.
  

Actual results:
Freezed while loading initrd image.


Expected results:


Additional info:
Comment 2 Prarit Bhargava 2011-07-22 14:50:06 UTC 
Can you please

a) add debug as a kernel parameter
b) attach the boot log from both the good kernel and bad kernel?

Thanks,

P.
Comment 3 Prarit Bhargava 2011-08-08 17:10:28 UTC 
Hi, 

Can you please

a) add debug as a kernel parameter
b) attach the boot log from both the good kernel and bad kernel?

Thanks,

P.
Comment 4 Prarit Bhargava 2011-08-23 13:19:00 UTC 
No answer to last requests.  Closed INSUFFICIENT_DATA.
Note You need to log in before you can comment on or make changes to this bug.