RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 619153 - no input devices after booting up 2.6.32-53.el6
Summary: no input devices after booting up 2.6.32-53.el6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dracut
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Harald Hoyer
QA Contact: Release Test Team
URL:
Whiteboard:
: 619374 619708 620812 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-28 17:32 UTC by Jay Turner
Modified: 2015-01-08 00:17 UTC (History)
13 users (show)

Fixed In Version: dracut-004-28.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-02 13:37:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jay Turner 2010-07-28 17:32:58 UTC 
Description of problem:
X completely freezes at GDM after booting up 2.6.32-53.el6.x86_64 on a machine running the nouveau driver (GeForce 9600M GT.)  System boots fine, no messages that I've been able to locate to this point, but once GDM starts up, the display is completely frozen.

Version-Release number of selected component (if applicable):
kernel-2.6.32-53.el6.x86_64
xorg-x11-drv-nouveau-0.0.16-8.20100423git13c1043.el6.x86_64

How reproducible:
Always.  Dropping back to -52.el6 and everything works fine again

Steps to Reproduce:
1. Boot up -53.el6.x86_64 on a nouveau-enabled system
2.
3.
  
Actual results:
Display freeze

Expected results:


Additional info:
Seeing this on another nouveau machine as well (GeForce GTX 285)
Comment 1 Jay Turner 2010-07-28 18:33:36 UTC 
Additional note.  Although access via ssh is fine, the directly attached keyboard and mouse are completely frozen as well (unable to cycle the capslock/numlock, etc.)
Comment 2 Linda Wang 2010-07-28 18:46:40 UTC 
-53 has the following patches pull in..

- [drm] nouveau: cleanup connector/encoder creation (Ben Skeggs) [612402]
- [drm] nouveau: move LVDS detection back to connector detect() time (Ben Skeggs) [612402]
- [drm] nouveau: fix race condition when under memory pressure (Ben Skeggs) [602663]
Comment 3 Jay Turner 2010-07-28 19:09:50 UTC 
The 3rd patch listed above (602663) was independently verified in a scratch-build kernel.  Just as a data point.
Comment 4 Ben Skeggs 2010-07-28 22:25:43 UTC 
All 3 patches were actually present in the scratch build mentioned.

Can you provide dmesg and Xorg.0.log, hopefully they'll reveal something.
Comment 5 Dave Airlie 2010-07-29 03:34:22 UTC 
this isn't a nouveau bug,

something has broken hal and input devices.

lshal | grep x11

from a working kernel and non-working kernel are different,

restarting hal fixes the problem, I suspect 

kernel
dracut
hal.
Comment 6 Dave Airlie 2010-07-29 03:40:12 UTC 
cc'd Harald and Richard Hughes.
Comment 7 Ray Strode [halfline] 2010-07-29 04:05:06 UTC 
This may be related to the fix for bug 617526
Comment 8 Ray Strode [halfline] 2010-07-29 04:19:21 UTC 
airlied just confirmed this problem only happens if you rebuild the initrd after having dracut-004-27 installed.  Rebuilding the initrd with any other version of dracut works.  Moving to dracut...
Comment 9 Dave Airlie 2010-07-29 04:24:14 UTC 
if I remove the umask in the 0196 patch in dracut it all seems to work okay.
Comment 10 Harald Hoyer 2010-07-29 09:14:09 UTC 
dracut-004-28.el6
Comment 12 Harald Hoyer 2010-07-29 09:34:43 UTC 
I would be very interested, which files were affected by the umask. Can you find that out for me?
Comment 13 Dave Airlie 2010-07-29 11:39:56 UTC 
I'll try and reproduce, at a guess some files hal was going to read.
Comment 14 Dave Airlie 2010-07-29 12:15:00 UTC 
*** Bug 619374 has been marked as a duplicate of this bug. ***
Comment 15 Jeff Layton 2010-07-29 12:26:32 UTC 
Confirmed. Installing new dracut package and rebuilding the initramfs fixed the issue for me.
Comment 16 Jay Turner 2010-07-29 12:41:45 UTC 
+1 for comment 15.
Comment 17 Harald Hoyer 2010-07-29 16:18:00 UTC 
regression from bugfix of bug 617526
Comment 19 Phil Knirsch 2010-08-02 13:00:56 UTC 
*** Bug 619708 has been marked as a duplicate of this bug. ***
Comment 21 Harald Hoyer 2010-08-05 06:51:49 UTC 
*** Bug 620812 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.