<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [HSW-M/BYT/BDW/BSW]udevadm unable to monitor HDMI plug/unplug event sporadically" href="https://bugs.freedesktop.org/show_bug.cgi?id=82593#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [HSW-M/BYT/BDW/BSW]udevadm unable to monitor HDMI plug/unplug event sporadically" href="https://bugs.freedesktop.org/show_bug.cgi?id=82593">bug 82593</a> from <a class="email" href="mailto:jinxianx.guo@intel.com" title="Guo Jinxian <jinxianx.guo@intel.com>"> Guo Jinxian</a> <pre>Created <a href="attachment.cgi?id=106892" name="attach_106892" title="dmesg">attachment 106892</a> <a href="attachment.cgi?id=106892&action=edit" title="dmesg">[details]</a> dmesg (In reply to <a href="show_bug.cgi?id=82593#c3">comment #3</a>) > (In reply to <a href="show_bug.cgi?id=82593#c2">comment #2</a>) > > Created <a href="attachment.cgi?id=106403" name="attach_106403" title="dmesg">attachment 106403</a> <a href="attachment.cgi?id=106403&action=edit" title="dmesg">[details]</a> > > dmesg > > > > (In reply to <a href="show_bug.cgi?id=82593#c1">comment #1</a>) > > > Please enable drm.debug=0xf to get drm core debugging, *or* apply this patch > > > to debug the hotplug events: > > > > > > diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c > > > index ab1a5f6dde8a..6abf092d9eb4 100644 > > > --- a/drivers/gpu/drm/drm_sysfs.c > > > +++ b/drivers/gpu/drm/drm_sysfs.c > > > @@ -481,7 +481,7 @@ void drm_sysfs_hotplug_event(struct drm_device *dev) > > > char *event_string = "HOTPLUG=1"; > > > char *envp[] = { event_string, NULL }; > > > > > > - DRM_DEBUG("generating hotplug event\n"); > > > + DRM_DEBUG_KMS("generating hotplug event\n"); > > > > > > kobject_uevent_env(&dev->primary->kdev->kobj, KOBJ_CHANGE, envp); > > > } > > > > > > Now, doing hotplug and looking at both udevadm monitor and dmesg, do you see > > > cases where: > > > > > > a) there's the "generating hotplug event" in dmesg, but you do *not* get it > > > in udevadm monitor > > > > > > *or* > > > > > > b) you do hotplug but the message is not in dmesg and you don't get it in > > > udevadm either. > > > > Enable drm.debug=0xf, then doing hotplug, the result is case a):the hotplug > > event is able to catch by dmesg, and not catch by udevadm monitor. > > I can't see "generating hotplug event" in the attached dmesg when you > hotplug. Whether you end up in that function or not is crucial in figuring > out where the problem is. Based on the dmesg, I think it's actually b) but I > can't be sure. > > Based on a hunch, please try reverting > commit 36cd7444c044806cd2a4e450a8385597221d5d25 > Author: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>> > Date: Fri May 2 13:44:18 2014 +1000 > > drm/i915: check connector->encoder before using it. > > and try again. On latest nightly(7101d84020f63f1da7e0c5d021cdd6be4d515de5) revert commit above, udevadm monitor still doesn't work.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>