Bug 591709 - udev takes almost 100% CPU due to xorg (intel) continuously re-initializing displays
udev takes almost 100% CPU due to xorg (intel) continuously re-initializing d...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.0
All Linux
medium Severity high
: rc
: ---
Assigned To: Adam Jackson
desktop-bugs@redhat.com
card_GM45
: Patch, Reopened, Triaged
Depends On: udev-intel-flood
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-12 17:02 EDT by Matěj Cepl
Modified: 2010-11-15 09:17 EST (History)
10 users (show)

See Also:
Fixed In Version: 2.6.32-52.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: udev-intel-flood
Environment:
Last Closed: 2010-11-15 09:17:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Comment 2 RHEL Product and Program Management 2010-05-12 19:18:57 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Adam Jackson 2010-05-24 10:18:18 EDT
So the deal here is that we're enabling output hotplug interrupts on more outputs than we perhaps should, because Intel hardware doesn't give us an especially reliable connector table.  So we get status change events for outputs that aren't actually there.

There may also be a secondary bug where we _keep_ getting these events, triggered by the output rescan itself.

Getting the hardware would be an important first step here.
Comment 4 Adam Jackson 2010-05-24 12:58:25 EDT
alternatively, anyone who can reproduce this, please boot with drm.debug=0x0f and attach dmesg from the resulting udev storm.
Comment 5 Adam Jackson 2010-07-01 10:28:26 EDT
There's been some motion on this upstream, some patches that resolve it for some people but not for others.  I've got a couple in mind that I can backport, but it's hard to say whether they'll fix the issue completely.
Comment 7 Matěj Cepl 2010-07-15 05:37:34 EDT
Just to emphasize I cannot reproduce this bug anymore, I haven't seen this for couple of months with RHEL-6. However, given its heavy hardware dependency I wouldn't close this as fixed.
Comment 9 Christopher Aillon 2010-07-15 16:51:47 EDT
Closing based on reporter's comments in comment 7.  Reopen if still exists.
Comment 10 Adam Jackson 2010-07-16 11:27:52 EDT
Reopening, I still have changes pending for this.
Comment 11 Adam Jackson 2010-07-16 15:02:29 EDT
Patch posted
Comment 12 Cameron Meadors 2010-07-19 15:07:55 EDT
What hardware is actually affected by this?  I only found mention of the MSI-GT725 in the fedora.  Are there other laptops that exhibit this bug? Is this maybe somthing that only depends on what graphics card you have?  or is it the whole package and how the graphics is integrated into the system?
Comment 13 Dave Airlie 2010-07-20 21:32:57 EDT
its a whole package type of thing, though I think any of the T500/W500 should be able to reproduce. I think I reproduced on a W500 at one point.
Comment 16 Aristeu Rozanski 2010-07-26 11:16:43 EDT
Patch(es) available on kernel-2.6.32-52.el6
Comment 21 James Laska 2010-09-01 14:44:14 EDT
I tested this bug on a t500 borrowed from helpdesk.  I'm unable to reproduce any udev issues when coming out of suspend.  Both suspend+resume work beautifully on this laptop.  Considering I wasn't able to reproduce the reported problem, I'm marking this issue as verified:SanityOnly.
Comment 22 releng-rhel@redhat.com 2010-11-15 09:17:05 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.