Bug 58899

Created attachment 72328 [details]
errorstatus

How very 845g.

Do you mean QA need to verify this issue on 845g  flatform?
BTW, this issue only can be reproduced on HSW.
(In reply to comment #2)
> How very 845g.

Could you double check the issue is cuased by mplayer -vo vaapi ? I can't reprocude this issue on my HSW.

It is a Kernel bug. 
(In reply to comment #4)
> Could you double check the issue is cuased by mplayer -vo vaapi ? I can't
> reprocude this issue on my HSW.

HSW:Shark Bay Desktop Beta SDP (Flathead Creek): B0 stepping (id=0x40660, rev 02), Lynx Point 02 (B0 stepping) and Host bridge id=0x0d04 (rev 02) 4Cores/4Thread, CPU 2.0GHz, 0xD26 2000MHz

Kernel: (drm-intel-nightly)cdb96764a45f87e4614df1b16d68b2ccb9806f57 good
Kernel: (drm-intel-nightly)071f0a705c081ed6b1d61b6fa8be969a5b15ddf8 bad

Libdrm:(master)libdrm-2.4.40-1-g7d42b49c0cf19dbb4531cd84efae51f95db2eea1
Mesa:(master)bb284669f85a32900bfec648d68ba4c4300772f4
Xserver:(master)xorg-server-1.13.0-135-g011f8458805e443ac9130865d2840a929a00cabf
Xf86_video_intel:(master)2.20.13-3-g66eb0adffa63ef8ece7621ba90dc96af91549612
Cairo:		(master)62b795fe52c73ad58101c101aa77449f4b61a576
   
Kernel: (drm-intel-nightly)071f0a705c081ed6b1d61b6fa8be969a5b15ddf8
Libva: (staging)2e11d2273b2974a7d1959cbcaf8db5b8e9aedd9e
Intel-driver: (staging)16dc6293002995da07148279f3846a2a9749ded3

HSW:Shark Bay Desktop Beta SDP (Flathead Creek): B0 stepping (id=0x40660, rev 02), Lynx Point 02 (B0 stepping) and Host bridge id=0x0d04 (rev 02) 4Cores/4Thread, CPU 2.0GHz, 0xD26 2000MHz

Was it the same symptomatic incoherency? With the regression suggestion, is it then bisectable? The symptom suggested a missing w/a or sync-flush, the regression tag suggests potentially otherwise.

We can find a good commit.
Kernel: (drm-intel-nightly)cdb96764a45f87e4614df1b16d68b2ccb9806f57 good
Kernel: (drm-intel-nightly)071f0a705c081ed6b1d61b6fa8be969a5b15ddf8 bad
But now the good commit"cdb96764a45f87e4614df1b16d68b2ccb9806f57" can't find in the branch drm-intel-nightly any more.
With the latest kernel, the issue still can be reproduced. But if adding "drm.debug=0xe" in kernel command line, this issue can't be reproduced.

(In reply to comment #9)
> Was it the same symptomatic incoherency? With the regression suggestion, is
> it then bisectable? The symptom suggested a missing w/a or sync-flush, the
> regression tag suggests potentially otherwise.

Yi, can we locate the specific kernel branch, the try bisecting?

(In reply to comment #11)
> Yi, can we locate the specific kernel branch, the try bisecting?

By quick investigation, I got little confused. 
First, this issue only happen on Ubuntu OS, I didn't reproduce on the Fedora. 
Second, on Ubuntu, I found that issue is related to the order of kernel command. 
For example:
a. BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc7+ root=UUID=452d1dd9-ee6a-451b-8330-8d4a5595f851 ro quiet splash text drm.debug=0xe
b. BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc7+ root=UUID=452d1dd9-ee6a-451b-8330-8d4a5595f851 drm.debug=0xe ro quiet splash text

Boot system with command b can trigger this issue, but command b can't

sorry typo:
Boot system with command a can trigger this issue, but command b can't

Is this HSW specific?

I do think this issue is due to some special setting in their environment. I tried to reproduce this issue in a refreshed Ubuntu 12.04 64 bit, and use the same kernel command line as previous. But failed to reproduce it. I assume this issue can't say the DRM issue exactly.

So we don't know how to reproduce the hang, nor whether it is a regression.

let's close it, unless Media QA could defense.

Closing verified+notourbug. No activity ~4 years.