Created attachment 81535 [details] dmesg: mplayer screen frozen Environment: ----------------------------- Kernel: (drm-intel-next-queued)6dd8224ec64c809dad5ceceac299918f5d9c7c31 Some additional commit info: Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Wed Jun 26 17:44:15 2013 +0300 drm/i915: Mask out hardware status bits from VLV DPLL register HSW mobile: MSI Haswell Notebook MSI MS-16GC Notebook 15.6; Host bridge ID=0x0c04 (rev 06);VGA ID=0x0416 (rev06);CPU: i7-4700MQ 2.4GHz stepping c3; BIOS: E16GCIMS.509 (04/24/2013) EC: 16GCEMS1 ver5.00 (04/12/2013);ME: 9.0.2.1345; MEM: 8G ; Descripiton: ------------------------------ Starting X, then play a video with mplayer, the screen is frozened at the beginning frames. Reproduce steps: ------------------------------ 1. xinit & 2. mplayer -vo xv /home/testframework/MPEG-2.mpeg
Xorg.log would be useful as well, thanks.
Also test with i915.i915_enable_fbc=0
Created attachment 81596 [details] Xorg.0.log
(In reply to comment #2) > Also test with i915.i915_enable_fbc=0 I added i915.i915_enable_fbc=0 in grub.cfg, then the video can play well.
Does UXA or SNA matter here?
(In reply to comment #5) > Does UXA or SNA matter here? Our machine is built up only just, and new machine doesn't have the config file " /etc/X11/xorg.conf", So I didn't switch it to UXA or SNA.
fbc is new in 3.11, so we need to treat this as a regression.
(In reply to comment #5) > Does UXA or SNA matter here? Today, I find this issue suddenly gone, no matter I use UXA or SNA, I tested -testing and -next-queued branch kernels, all passed. Then I test it without command "i915.i915_enable_fbc=0", it also worked well. I backtrack to the original environment, and this issue also gone. I can't explain the reason, maybe we can close it now.
So even with old UXA/SNA the bug is gone now?
(In reply to comment #9) > So even with old UXA/SNA the bug is gone now? Yes, with old UXA/SNA, I just can't reproduce it.
Closing old verified.
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.