From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Rest of my DSI and DPLL stuff
Date: Thu, 14 Apr 2016 11:46:12 +0300 [thread overview]
Message-ID: <20160414084612.GF4329@intel.com> (raw)
In-Reply-To: <8397044.BClUR51EGa@fractal>
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/ilk-hp8440p/[1]
> http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/Patchwork_1881/ivb-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?
I did find the skipped kms_force_connector_basic/prune-stale-modes in
the dmesg eventually, but it was a bit more difficult since it skipped
already from a fixture, and so the subtest name was never recorded in
the dmesg, which is a bit unfortunate. As far as the skipping goes, it
look like the VGA connector flips to 'connected' after every suspend
for some reason, and then goes back to 'disconnected' at some point. So
it feels like we have a bug in the connector resume handling still.
>
> The dmesg is synced, but if the reset happens with delay, then it might be in wrong
> place. I'm suggesting to search for test name and looking upwards from there.
>
> > > Results at /archive/results/CI_IGT_test/Patchwork_1881/
>
> Tomi
>
> --------
> [1] http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/Patchwork_1881/ilk-hp8440p/
> [2] http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/Patchwork_1881/ivb-t430s/
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-14 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 19:14 [PATCH 0/5] drm/i915: Rest of my DSI and DPLL stuff ville.syrjala
2016-04-12 19:14 ` [PATCH 1/5] drm/i915: Setup DPLL/DPLLMD for DSI too on VLV/CHV ville.syrjala
2016-04-15 13:09 ` Jani Nikula
2016-04-15 13:27 ` Ville Syrjälä
2016-04-12 19:14 ` [PATCH 2/5] drm/i915: Compute DSI PLL parameters during .compute_config() ville.syrjala
2016-04-12 19:14 ` [PATCH 3/5] drm/i915: Eliminate {vlv, bxt}_configure_dsi_pll() ville.syrjala
2016-04-12 19:14 ` [PATCH 4/5] drm/i915: Hook up pfit for DSI ville.syrjala
2016-04-12 19:14 ` [PATCH 5/5] drm/i915: Reject 'Center' scaling mode for eDP/DSI on GMCH platforms ville.syrjala
2016-04-13 16:02 ` ✗ Fi.CI.BAT: failure for drm/i915: Rest of my DSI and DPLL stuff Patchwork
2016-04-13 16:29 ` Ville Syrjälä
2016-04-14 7:24 ` Tomi Sarvela
2016-04-14 8:46 ` Ville Syrjälä [this message]
2016-04-14 8:54 ` Tomi Sarvela
2016-04-14 9:03 ` Ville Syrjälä
2016-04-15 12:52 ` [PATCH 0/5] " Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160414084612.GF4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomi.p.sarvela@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox