Bug 65332

Summary: [IVB: Apple MacBook PRO] glxgears cause "gpu hang" reminder messages in dmesg, but machine is reachable
Product: Mesa Reporter: shui yangwei <yangweix.shui>
Component: Drivers/DRI/i965Assignee: Ian Romanick <idr>
Status: VERIFIED FIXED QA Contact:
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: dmesg: glxgears cause "gpu hang"
i915_error_state log

Description shui yangwei 2013-06-04 08:15:25 UTC 
Created attachment 80266 [details]
dmesg: glxgears cause "gpu hang"

Environment:
---------------------
Kernel: (drm-intel-next-queued)92d44621ad2d083bc03920c904ca0a5eb10d9ded
Some additional commit info:
Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
Date:   Fri May 31 16:33:24 2013 -0300

    drm/i915: add i915_ips_status debugfs entry

Description:
---------------------
When I start glxgears on our new IVB platform(Apple MacBook Pro), glxgears will take a little more time to be activated. The graphics box will be black for a while, then glxgears also worked properly. I checked the dmesg, there's some error messages like below:

[  461.016229] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[  461.016240] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state
[  461.019565] [drm:i915_error_work_func], resetting chip 

I also test other one IVB desktop platform, there's not this problem.

Reproduce steps:
---------------------
1. reboot machine
2. xinit & 
3. glxgears &
4. checkout dmesg
Comment 1 Chris Wilson 2013-06-04 08:33:29 UTC 
Always include the i915_error_state following a GPU hang.
Comment 2 shui yangwei 2013-06-04 08:54:47 UTC 
Created attachment 80273 [details]
i915_error_state log

Here's the i915_error_state log.
Comment 3 Chris Wilson 2013-06-04 09:03:06 UTC 
Update mesa, you've hit the broken IVB blorp caused by:

commit 1dfea559c3f188a7a82a4abc09765ba09e939522
Author: Eric Anholt <eric@anholt.net>
Date:   Wed May 1 16:08:12 2013 -0700

    i965: Fix SNB GPU hangs when a blorp batch is the first thing to execute.
    
    The GPU apparently goes looking for constants even though there are no
    shader stages enabled, and gets stuck because we haven't told it there are
    no constants to collect.  If any other user of the 3D pipeline had run
    (even the Render accel of the X server!) since power on, then the in-GPU
    constant buffers would have been set up with some contents we didn't use,
    and we would succeed.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=56416
    Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
    Tested-by: Dave Airlie <airlied@redhat.com>
    NOTE: This is a candidate for the stable branches.

and should be fixed by

commit 5d06c9ea0f1aa2f312660413acd1bd6a1dafe1a6
Author: Eric Anholt <eric@anholt.net>
Date:   Mon May 6 20:44:21 2013 -0700

    i965: Fix hangs on HSW since the gen6 blorp fix.
    
    The constant packets for gen6 are too small for gen7, and while IVB seems
    happy with them HSW blows up.  Fix it by emitting the correct packets on
    gen7, for all stages.
    
    v2: Include the packets instead of just skipping them.
    NOTE: This is a candidate for the stable branches.
    Reviewed-and-tested-by: Chad Versace <chad.versace@linux.intel.com>
    Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Comment 4 shui yangwei 2013-07-02 05:23:28 UTC 
Test with latest X11R7, this bug fixed, I verified here. Sorry for the quite late response.

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.