Bug 66838 - [ILK]igt/gem_write_read_ring_switch/blt2bsd causes *ERROR* bsd ring hung inside bo (0x952000 ctx 0) at 0x952004
Summary: [ILK]igt/gem_write_read_ring_switch/blt2bsd causes *ERROR* bsd ring hung insi...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-12 01:57 UTC by lu hua
Modified: 2017-10-06 14:45 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (70.67 KB, text/plain)
2013-07-12 01:57 UTC, lu hua 		no flags Details
i915_error_state (1.40 MB, text/plain)
2013-07-12 01:57 UTC, lu hua 		no flags Details
View All

Description lu hua 2013-07-12 01:57:23 UTC 
Created attachment 82351 [details]
dmesg

System Environment:
--------------------------
Platform:       Ironlake
Kernel:    drm-intel-fixes 46a0b638f35b45fc13d3dc0deb6a7e17988170b2

Bug detailed description:
-------------------------
It happens on ironlake with drm-intel-fixes kernel and drm-intel-next-queued.
It's a new igt case.

output:
running subtest blt2bsd

Reproduce steps:
----------------
1. ./gem_write_read_ring_switch --run-subtest blt2bsd
Comment 1 lu hua 2013-07-12 01:57:52 UTC 
Created attachment 82352 [details]
i915_error_state
Comment 2 Chris Wilson 2013-07-12 09:07:29 UTC 
commit b37d89318de5b5e771ad065bb7b55102f6800391
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Jul 12 10:05:34 2013 +0100

    tests/gem_write_ring_switch: Skip on pre-SNB
    
    The test requires MI commands only introduced with SNB, and so causes
    GPU death on gm45 and ilk.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=66838
Comment 3 lu hua 2013-07-15 03:00:43 UTC 
Verified.Fixed.
Comment 4 Elizabeth 2017-10-06 14:45:09 UTC 
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.