Bug 111628 - [CI][RESUME] igt@gem_mocs_settings@mocs-(rc6|reset)-blt - fail - Failed assertion: read_val == val
Summary: [CI][RESUME] igt@gem_mocs_settings@mocs-(rc6|reset)-blt - fail - Failed asser...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-10 08:35 UTC by Martin Peres
Modified: 2019-10-16 10:38 UTC (History)
1 user (show)

See Also:
i915 platform: TGL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-09-10 08:35:28 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_362/fi-tgl-u/igt@gem_mocs_settings@mocs-reset-blt.html

Starting subtest: mocs-reset-blt
(gem_mocs_settings:1366) CRITICAL: Test assertion failure function check_control_registers, file ../tests/i915/gem_mocs_settings.c:378:
(gem_mocs_settings:1366) CRITICAL: Failed assertion: read_val == val
(gem_mocs_settings:1366) CRITICAL: engine=3 index=2 read_value=0x00000000 value=0x00000037
Comment 1 CI Bug Log 2019-09-10 08:35:49 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@gem_mocs_settings@mocs-(rc6|reset)-blt - fail - Failed assertion: read_val == val
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_362/fi-tgl-u/igt@gem_mocs_settings@mocs-reset-blt.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_362/fi-tgl-u/igt@gem_mocs_settings@mocs-rc6-blt.html
Comment 2 Francesco Balestrieri 2019-09-24 06:50:30 UTC
TGL MOCS table was added and this test doesn't fail anymore, resolving.
Comment 3 CI Bug Log 2019-10-16 10:38:33 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


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.