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
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.
alternatively, anyone who can reproduce this, please boot with drm.debug=0x0f and attach dmesg from the resulting udev storm.
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.
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.
Closing based on reporter's comments in comment 7. Reopen if still exists.
Reopening, I still have changes pending for this.
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?
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.
Patch(es) available on kernel-2.6.32-52.el6
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.
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.