Bug 99753 - [HSW][BAT] gem_busy/basic-hang-default causing dmesg warning
Summary: [HSW][BAT] gem_busy/basic-hang-default causing dmesg warning
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-10 08:41 UTC by Jani Saarinen
Modified: 2017-03-03 07:36 UTC (History)
1 user (show)

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


Attachments
dmesg during (4.97 MB, text/plain)
2017-02-10 08:41 UTC, Jani Saarinen
no flags Details

Description Jani Saarinen 2017-02-10 08:41:47 UTC
Created attachment 129468 [details]
dmesg during

On patchwork run Test gem_busy/basic-hang-default 
Causes flip-flop 
pass       -> DMESG-WARN (fi-hsw-4770r) and on previous run passed fine.

Test results:
https://intel-gfx-ci.01.org/CI/Patchwork_3763/fi-hsw-4770r/igt@gem_busy@basic-hang-default.html

Dmesg (attached)
Comment 1 Chris Wilson 2017-02-10 08:47:27 UTC
That's unlikely to be us (directly).
Comment 2 Dorota Czaplejewicz 2017-02-27 11:36:21 UTC
Could not see on HSW-4770R with kernel 15ccc64 and config from https://intel-gfx-ci.01.org/CI/CI_DRM_2243/kernel.config.bz2

32/32 tests pass
Fedora 25
System: GIGABYTE M4HM87P-00
Comment 3 Chris Wilson 2017-03-01 17:51:09 UTC
Assuming this is more mutex fallout [fixed with pre-v4.11-rc1 merge in tip] until proven otherwise.
Comment 4 Jani Saarinen 2017-03-03 07:20:06 UTC
Seems one fail now instead of warning
https://intel-gfx-ci.01.org/CI/CI_DRM_2272/fi-hsw-4770r/igt@gem_busy@basic-hang-default.html

Should we re-open?
Comment 5 Chris Wilson 2017-03-03 07:29:57 UTC
(In reply to Jani Saarinen from comment #4)
> Seems one fail now instead of warning
> https://intel-gfx-ci.01.org/CI/CI_DRM_2272/fi-hsw-4770r/igt@gem_busy@basic-
> hang-default.html
> 
> Should we re-open?

It's something else.
Comment 6 Chris Wilson 2017-03-03 07:36:46 UTC
The important note there is:

Hangcheck active, fires in -127360ms

I've yet another patch to try and get more information here, but it is looking like either the timer didn't fire, or the work was never run. The next patch adds a message to try and distinguish those two cases.


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.