Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 489241

Summary: RHEL5.3 2.6.18-128.el5 PPC64 kernel does not respond to keyboard
Product: Red Hat Enterprise Linux 5 Reporter: Simon Xu <hxunix>
Component: kernelAssignee: Ameet Paranjape <aparanja>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: urgent Docs Contact:
Priority: low    
Version: 5.3CC: dzickus, peterm
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-03 18:13:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Simon Xu 2009-03-09 02:27:37 UTC 
Description of problem:

After booting up RHEL5.3 2.6.18-128.el5 PPC64 kernel on IBM P615, the machine does not respond to keyboard strokes (including scroll lock, num lock, caps lock).  But you can still get normal response if you ping it, and you can use ssh to log into the machine if sshd is running.

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

2.6.18-128.el5

How reproducible:


Steps to Reproduce:
1. Install RHEL5.3 on IBM P615
2. Boot it.
3.
  
Actual results:

the machine does not respond to keyboard strokes (including scroll lock, num lock, caps lock).  But you can still get normal response if you ping it, and you can use ssh to log into the machine if sshd is running.

Expected results:

The machine should respond to key strokes.

Additional info:
Comment 2 Ameet Paranjape 2009-04-03 18:13:47 UTC 

*** This bug has been marked as a duplicate of bug 455232 ***