Bug 88655 - [BSW Regression]igt/gem_pread_after_blit/default-hang causes system hang
Summary: [BSW Regression]igt/gem_pread_after_blit/default-hang causes system hang
Status: CLOSED DUPLICATE of bug 88652
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords: bisect_pending
Depends on:
Blocks:
 
Reported: 2015-01-21 07:44 UTC by lu hua
Modified: 2017-10-06 14:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (2.19 MB, image/jpeg)
2015-01-21 07:44 UTC, lu hua 		no flags Details
View All

Description lu hua 2015-01-21 07:44:58 UTC 
Created attachment 112589 [details]
dmesg

==System Environment==
--------------------------
Regression: yes
good commit: 1d83d957e621f160dfe0f08194e9c2fdd5fa7f3e
bad commit: 93180785d44e3d417099e293b9ff6eeb4fd20aa2

no-working platforms: BSW

==kernel==
--------------------------
drm-intel-nightly/d6bc7a6a0a7573350e8be8ec54002c20d1dbe1e0
commit d6bc7a6a0a7573350e8be8ec54002c20d1dbe1e0
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Tue Jan 20 15:10:59 2015 +0100

    drm-intel-nightly: 2015y-01m-20d-14h-10m-40s UTC integration manifest

==Bug detailed description==
-----------------------------
It causes system on drm-intel-nightly and drm-intel-next-queued kernel.

output
IGT-Version: 1.9-g032f30c (x86_64) (Linux: 3.19.0-rc4_drm-intel-nightly_d6bc7a_20150121+ x86_64)

==Reproduce steps==
---------------------------- 
1. ./gem_pread_after_blit --run-subtest default-hang
Comment 1 Chris Wilson 2015-01-21 09:20:14 UTC 

*** This bug has been marked as a duplicate of bug 88652 ***
Comment 2 lu hua 2015-03-13 06:59:58 UTC 
Verified.Fixed.
Comment 3 Elizabeth 2017-10-06 14:32:04 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.