Bug 73309 - Intel Haswell 4400 [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring. Glxgears: 2 frames in 8.0 seconds = 0.250 FPS.
Summary: Intel Haswell 4400 [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter rin...
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-05 17:23 UTC by teodor.vlasov
Modified: 2014-01-10 10:07 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Xorg log (28.22 KB, text/plain)
2014-01-05 17:23 UTC, teodor.vlasov 		no flags Details
dmesg (72.15 KB, text/plain)
2014-01-05 17:24 UTC, teodor.vlasov 		no flags Details
GPU error state (2.65 MB, text/plain)
2014-01-05 17:26 UTC, teodor.vlasov 		no flags Details
glxgears output with LIBGL_DEBUG=verbose (587 bytes, text/plain)
2014-01-05 17:31 UTC, teodor.vlasov 		no flags Details
View All

Description teodor.vlasov 2014-01-05 17:23:52 UTC 
Created attachment 91524 [details]
Xorg log

Hello,
Here is a problem:
All apps, that use 3d are super slow. Blender, glxgears make 2-3 frames per 10 seconds. 

chipset: i915
system architecture: x86_64
Mesa version: 10.0.1
xf86-video-intel version: 2.21.15
xserver version: 1.14.5
libdrm version: 2.4.50
kernel version: 3.12.6
Distribution: ArchLinux
Machine: Lenovo u330p
Display connector: HDMI

Reproduce steps: run glxgears
Comment 1 teodor.vlasov 2014-01-05 17:24:54 UTC 
Created attachment 91525 [details]
dmesg
Comment 2 teodor.vlasov 2014-01-05 17:26:35 UTC 
Created attachment 91526 [details]
GPU error state
Comment 3 teodor.vlasov 2014-01-05 17:31:41 UTC 
Created attachment 91528 [details]
glxgears output with LIBGL_DEBUG=verbose
Comment 4 Chris Wilson 2014-01-10 10:06:58 UTC 
Fixed in a more recent -intel release, 2.99.903 to be precise.

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.