Bug 88095 - [BDW]igt/gem_concurrent_blit/gtt-bcs-early-read-forked causes *ERROR* Unclaimed register detected
Summary: [BDW]igt/gem_concurrent_blit/gtt-bcs-early-read-forked causes *ERROR* Unclaim...
Status: CLOSED DUPLICATE of bug 85890
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: 2015-01-06 06:39 UTC by lu hua
Modified: 2017-07-24 22:49 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description lu hua 2015-01-06 06:39:39 UTC 
==System Environment==
--------------------------
Regression: not sure

Non-working platforms: BDW

==kernel==
--------------------------
drm-intel-nightly/07d0c831d9207c937595f081c8fddbddbf53756f
commit 07d0c831d9207c937595f081c8fddbddbf53756f
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Tue Dec 30 15:02:01 2014 +0200

    drm-intel-nightly: 2014y-12m-30d-13h-01m-34s UTC integration manifest

==Bug detailed description==
-----------------------------
It causes <3>[ 2121.211861] [drm:hsw_unclaimed_reg_detect.isra.4 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. on drm-intel-nightly kernel when run automation testing. run the binary, I am unable to reproduce it.

output:
IGT-Version: 1.9-gcb512b6 (x86_64) (Linux: 3.19.0-rc2_drm-intel-nightly_07d0c8_20150105+ x86_64)
using 2x512 buffers, each 1MiB
Subtest gtt-bcs-early-read-forked: SUCCESS (2.200s)

dmesg:
<3>[ 2121.211861] [drm:hsw_unclaimed_reg_detect.isra.4 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.

==Reproduce steps==
---------------------------- 
1. run full igt.
Comment 1 Rodrigo Vivi 2015-01-22 22:28:19 UTC 

*** This bug has been marked as a duplicate of bug 85890 ***

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.