[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Rest of my DSI and DPLL stuff

[Ville Syrjälä]

On Thu, Apr 14, 2016 at 11:54:53AM +0300, Tomi Sarvela wrote:
> On Thursday 14 April 2016 11:46:12 Ville Syrjälä wrote:
> > On Thu, Apr 14, 2016 at 10:24:23AM +0300, Tomi Sarvela wrote:
> > > On Wednesday 13 April 2016 19:29:25 Ville Syrjälä wrote:
> > > [ILK-hp8440p problems]
> > > 
> > > > ...
> > > > 
> > > > [  265.316531] drm/i915: Resetting chip after gpu hang
> > > > [  265.316585] [drm:i915_reset [i915]] *ERROR* Failed to reset chip:
> > > > -110
> > > > 
> > > > Looks like the GPU died for some reason.
> > > > 
> > > > > Test kms_force_connector_basic:
> > > > >         Subgroup prune-stale-modes:
> > > > >                 pass       -> SKIP       (ivb-t430s)
> > > > 
> > > > No clue what happened here. The change isn't visible in the results
> > > > visualization page, nor can I see this subtest even being run in
> > > > the dmesg for Patchwork_1881. The dmesg ends at gtt-blt, but based on
> > > > the json there were a ton of tests run after that. In fact the json
> > > > and dmesg seem totally out of sync.
> > > > 
> > > > Tomi, any idea what's going on here?
> > > 
> > > The link from Patchwork page is hosed, but the full dmesgs are at
> > > http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/Patchwork_1881/il
> > > k-hp8440p/[1]
> > > http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/Patchwork_1881/i
> > > vb-t430s/[2]
> > Not sure what you mean with hosed. It took me to the same place where I
> > was before (ie. [2]). But if you look at the dmesg vs. results.json the
> > order of the tests is totally different. I thought the json would show
> > them in the order they were run, but maybe I'm wrong?
> 
> HOst link took me to unexisting host.html page instead of host/ directory.
> 
> Looking at results.json and dmesg-during.log, they seem same. Example, ivb-
> t430s start of the logs:
> 
> [   54.485575] kms_addfb_basic: starting subtest addfb25-Yf-tiled
> [   54.580441] gem_mmap_gtt: starting subtest basic-short
> [   54.728538] gem_storedw_loop: starting subtest basic-vebox
> 
>     "tests": {
>         "igt at kms_addfb_basic@addfb25-yf-tiled": {
>         "igt at gem_mmap_gtt@basic-short": {
>         "igt at gem_storedw_loop@basic-vebox": {
> 
> Do you have specific build/host/test which shows the inconsistency between 
> logs?

results.json looks like this around gtt-blt:
igt at kms_flip@basic-flip-vs-modeset
igt at gem_exec_parse@basic-allowed
igt at gem_exec_basic@gtt-blt
igt at kms_setmode@basic-clone-single-crtc
igt at kms_pipe_crc_basic@read-crc-pipe-a

The dmesg on the other hand ends like this:
[  574.506500] kms_pipe_crc_basic: executing
[  574.518000] kms_pipe_crc_basic: starting subtest suspend-read-crc-pipe-B
[  577.846181] kms_pipe_crc_basic: exiting, ret=0
[  579.048483] gem_sync: executing
[  579.055032] gem_sync: starting subtest basic-bsd2
[  579.058293] gem_sync: exiting, ret=0
[  579.285709] kms_addfb_basic: executing
[  579.289292] kms_addfb_basic: starting subtest bo-too-small-due-to-tiling
[  579.289848] kms_addfb_basic: exiting, ret=0
[  579.456086] gem_exec_basic: executing
[  579.459748] gem_exec_basic: starting subtest gtt-blt
[  579.461952] gem_exec_basic: exiting, ret=0

So based on dmesg gtt-blt was the last one executed, but according to
the json it wasn't.

-- 
Ville Syrjälä
Intel OTC