Bug 89216 - moving vlc window to secondary hdmi-attached monitor freezes GUI
Summary: moving vlc window to secondary hdmi-attached monitor freezes GUI
Status: CLOSED DUPLICATE of bug 69119
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-19 01:38 UTC by m.manico
Modified: 2017-07-24 22:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
first 70000 lines of /sys/class/drm/card0/error (1.41 MB, text/plain)
2015-02-19 01:38 UTC, m.manico
no flags Details
second (=last) part of /sys/class/drm/card0/error (1.70 MB, text/plain)
2015-02-19 01:41 UTC, m.manico
no flags Details

Description m.manico 2015-02-19 01:38:40 UTC
Created attachment 113650 [details]
first 70000 lines of /sys/class/drm/card0/error

== Setup ==
Hardware: Lenovo Thinkpad S440(*) with secondary monitor connected via HDMI
Software: Gentoo Linux, Fluxbox, xrandr (for extending GUI to sec. monitor), vlc

(*) There exist several version of the Lenovo Thinkpad S440. My model is non-touch and has an Intel HD G4400 grapic card (other models may have AMD).

== Actions taken ==
1) Play a video in vlc on laptop's monitor
2) move vlc window to sec. monitor

== Behaviour ==
X freezes on both monitors after more than half of the vlc windows is on the hdmi monitor; sound still plays back; mouse pointer behaves normally

== Expected Behaviour ==
GUI keeps on working as before; vlc plays back video as it did on laptop's monitor

== dmesg ==
[44010.240584] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44010.240587] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[44010.240587] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[44010.240588] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[44010.240589] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[44010.240589] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[44014.246958] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44018.250198] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44027.245162] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44031.256416] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44035.259649] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44039.255014] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44043.270088] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44043.270173] [drm] no progress on render ring
[44043.271102] [drm] GPU HANG: ecode -1:0x00000000, reason: Ring hung, action: reset
[44640.752702] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44644.755913] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44648.759160] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44659.763984] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44663.767146] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44667.770472] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[44671.773737] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue

== Comments ==
The line [44640.752702] and following lines were caused by a second attempt to move vlc to sec. monitor.

ls /sys/class/drm/
card0
card0-DP-1
card0-eDP-1
card0-HDMI-A-1
card0-HDMI-A-2
controlD64
renderD128
version

lspci
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
Comment 1 m.manico 2015-02-19 01:41:06 UTC
Created attachment 113651 [details]
second (=last) part of /sys/class/drm/card0/error
Comment 2 m.manico 2015-02-19 02:07:06 UTC
== A ==
Things that _do_ work on sec. (hdmi) monitor:
* playing video streams in browser
* 3D games (openarena)
* 2D games (wesnoth)

== B ==
using mplayer has same symptoms as vlc player has plus sound get laggy and finally dies off

== C ==
When I move the vlc/mplayer video window torwards the hdmi display until I notice misbehaviour (which happens as soon as more than 50% of the video window are visible on hdmi monitor) I pull it back to the laptop's monitor. That "pulling back" is only visible after a long delay (30 Seconds - 1 Minute) but after that the computer is recovered and proceeds to work as expected.
Comment 3 Chris Wilson 2015-02-20 12:21:28 UTC

*** This bug has been marked as a duplicate of bug 69119 ***
Comment 4 Chris Wilson 2015-02-20 12:21:54 UTC
Fixed in xf86-video-intel-2.99.903.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.