[Bug 82593] [HSW-M/BYT/BDW/BSW]udevadm unable to monitor HDMI plug/unplug event sporadically

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=82593

--- Comment #20 from Hugh Greenberg <hugegreenbug at gmail.com> ---
(In reply to Hugh Greenberg from comment #19)
> (In reply to Jani Nikula from comment #18)
> > (In reply to Hugh Greenberg from comment #11)
> > > I am experiencing this bug on HSW. udevadm monitor does not show hot plug
> > > events and it only triggers the rule below once:
> > > 
> > > SUBSYSTEM=="drm", ACTION=="change", RUN+="script.sh"
> > > 
> > > I'm using the current drm-intel-nightly and I'm using kernel 3.19.6.
> > 
> > Btw, what's the failure mode you see after the missed event? If I'm
> > interpreting the situation right, you should still have the picture on
> > screen after you replug.
> 
> I'm working on 2 different bugs related to HDMI on Ubuntu Unity. The missed
> events didn't cause any problems, but they prevent me from running a command
> to fix issues when an event occurs.
> 
> 1. Plugging in the HDMI cable does show a picture on the external screen and
> Unity is expanded to both screens, but sometimes, there are corrupted
> graphics on the laptop screen. xrandr --auto will refresh the screen. I
> can't remember the exact Compiz warning, but it couldn't apply a texture.
> 
> 2. Removing the HDMI cable will not trigger Unity to resize the screen
> sometimes. Again xrandr --auto will resize the screen.
> 
> Without your patch, I would need to poll the connector status and I would
> rather not do that.

Actually, xrandr --auto doesn't fix the graphics corruption, but it does force
a resize.

Also, I have found that if I remove the hdmi cable slowly, I do not always see
a udev event with udevadm monitor.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150611/f2229113/attachment.html>