Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Comment 2RHEL Program Management
2010-05-12 23:18:57 UTC
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.
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.
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.
Comment 9Christopher Aillon
2010-07-15 20:51:47 UTC
Closing based on reporter's comments in comment 7. Reopen if still exists.
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?
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 22releng-rhel@redhat.com
2010-11-15 14:17:05 UTC
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.