Bug 77782

Summary: [snb] stuck on wait-for-event (plane B)
Product: DRI Reporter: Dmitry Sinina <dmitry.sinina>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED INVALID QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
content of /sys/class/drm/card0/error
none
content of /sys/class/drm/card0/error again none

Description Dmitry Sinina 2014-04-22 21:07:48 UTC
Created attachment 97775 [details]
content of /sys/class/drm/card0/error

My hardware:
 Lenovo Thinpad x220 laptop;
 i5-2520M cpu;
 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core    Processor Family Integrated Graphics Controller (rev 09)

My system is Debian testing, kernel 3.13.
 
When I tried run video (vlc player or youtube in chromium browser) on external connected monitor(VGA) I got system freeze.

I see this in dmesg:

[ 6456.881715] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
[ 6456.881721] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 6456.881722] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 6456.881723] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 6456.881724] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 6456.881724] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 6466.895407] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
[ 6472.884421] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring


Content of /sys/class/drm/card0/error attached.

In Xorg logs I see lot of messages:

(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f3e2ca5ce98]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x7f3e2c921852]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3e24814000+0x570d) [0x7f3e2481970d]
(EE) 3: /usr/bin/X (0x7f3e2c8b5000+0x92ae8) [0x7f3e2c947ae8]
(EE) 4: /usr/bin/X (0x7f3e2c8b5000+0xbad50) [0x7f3e2c96fd50]
(EE) 5: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3e2b74f000+0xf880) [0x7f3e2b75e880]
(EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f3e2a26a567]
(EE) 7: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x34) [0x7f3e2b546764]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f3e26ce3000+0x26e9b) [0x7f3e26d09e9b]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f3e26ce3000+0x52563) [0x7f3e26d35563]
(EE) 10: /usr/bin/X (0x7f3e2c8b5000+0x1327b4) [0x7f3e2c9e77b4]
(EE) 11: /usr/bin/X (0x7f3e2c8b5000+0xe2337) [0x7f3e2c997337]
(EE) 12: /usr/bin/X (0x7f3e2c8b5000+0xe30e5) [0x7f3e2c9980e5]
(EE) 13: /usr/bin/X (0x7f3e2c8b5000+0xe1a1d) [0x7f3e2c996a1d]
(EE) 14: /usr/bin/X (0x7f3e2c8b5000+0x7e3c6) [0x7f3e2c9333c6]
(EE) 15: /usr/bin/X (MapWindow+0x105) [0x7f3e2c9361b5]
(EE) 16: /usr/bin/X (0x7f3e2c8b5000+0x50908) [0x7f3e2c905908]
(EE) 17: /usr/bin/X (0x7f3e2c8b5000+0x5586e) [0x7f3e2c90a86e]
(EE) 18: /usr/bin/X (0x7f3e2c8b5000+0x5968a) [0x7f3e2c90e68a]
(EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f3e2a1adb45]
(EE) 20: /usr/bin/X (0x7f3e2c8b5000+0x44c2e) [0x7f3e2c8f9c2e]
(EE) 
[  6455.804] [mi] Increasing EQ size to 1024 to prevent dropped events.
[  6455.804] [mi] EQ processing has resumed after 317 dropped events.
[  6455.804] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.

What additional information I have to show?
Thanks.
Comment 1 Chris Wilson 2014-04-22 21:15:46 UTC
If this is easily reproducible for you, please try testing with i915.enable_rc6=0.
Comment 2 Dmitry Sinina 2014-04-22 21:39:12 UTC
Created attachment 97782 [details]
content of /sys/class/drm/card0/error again
Comment 3 Dmitry Sinina 2014-04-22 21:39:50 UTC
(In reply to comment #1)
> If this is easily reproducible for you, please try testing with
> i915.enable_rc6=0.

I have tried with i915.enable_rc6=0. Same behavior.

# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.13-1-amd64 root=UUID=71163ea2-5b45-49be-8483-930a3a244b16 ro intel_iommu=on i915.enable_rc6=0

New content of /sys/class/drm/card0/error attached too.
Comment 4 Jesse Barnes 2014-12-04 21:45:11 UTC
Sorry for the delayed update.  Does this occur with a more recent kernel?  Can you try with the drm-intel-nightly branch from git://anongit.freedesktop.org/drm-intel?
Comment 5 Jesse Barnes 2015-03-30 20:52:51 UTC
Hoping this is resolved now, please re-open if not after testing with current software.

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.