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.IGT: warning for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not
Date: Fri, 3 Nov 2017 12:41:36 +0200 [thread overview]
Message-ID: <20171103104136.GV10981@intel.com> (raw)
In-Reply-To: <72f57736-840b-b420-a9f9-ab631167aa2d@intel.com>
On Fri, Nov 03, 2017 at 10:18:32AM +0200, Tomi Sarvela wrote:
> On 02/11/17 19:08, Ville Syrjälä wrote:
> > On Thu, Nov 02, 2017 at 04:34:26PM -0000, Patchwork wrote:
> >> == Series Details ==
> >>
> >> Series: series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not
> >> URL : https://patchwork.freedesktop.org/series/33060/
> >> State : warning
> >>
> >> == Summary ==
> >>
> >> Test kms_busy:
> >> Subgroup extended-modeset-hang-oldfb-with-reset-render-A:
> >> dmesg-warn -> PASS (shard-hsw)
> >> Subgroup extended-modeset-hang-newfb-with-reset-render-B:
> >> pass -> DMESG-WARN (shard-hsw)
> >
> > Hmm. The warn was there already AFAICS. I wonder why this is claiming
> > things were passing?
>
> The sharded result for the run is 'warning'. What do you mean?
This should read 'DMESG-WARN -> DMESG-WARN' rather than 'pass ->
DMESG-WARN'. If I click the link to open up the results in the browser
this test isn't shown on the shards.html, but I can see it as
orange->orange in shards-all.html.
>
> > Also shard-glkb didn't seem to get any results from this run. No idea
> > why, nor why this summary fails to mention that fact.
>
> One GLK died, and 4 GLKs take nearly 90 minutes to run shards. It's not
> reasonable to wait for them on every run and queue everything else, so
> Patchwork/Trybot runs are skipped on GLK. Anything can be run and added
> to results manually, if needed.
If they aren't being run, then maybe they shouldn't be part of the
shards.html for pw/trybot runs? Would save me having to wonder why I'm
getting empty results. Or we should have some kind of indication why we
didn't get any results for a particular machine (ie. whether it was
expected or not).
>
> As a comparison, SNB/HSW/APL all run shards in ~35 minutes. KBL is the
> only one that gets rebooted between shards (due to leaking context), and
> takes around 50 minutes.
>
> > Oh and BTW the boot/dmesg links from the shard results don't seem to
> > work very well. Sometimes it just gets you an empty log and you have
> > to manually find a file that has some actual content in it.
>
> If there is no bootlog for a run, the host has not booted between runs.
> It's maybe not intuitively clear. I've tried to communicate that the
> shard runs are shifting to conditional reboots (booted only if hung).
I don't know how that relates to the several dmesg/boot logs I see
in the directory. And why the web links often seems to point to the
empty files instead of ones with actual content in them.
Also the files are numbered in some way. Whether there's any significance
to those numbers I can't really tell.
>
> Tomi
>
> >> shard-hsw total:2539 pass:1432 dwarn:2 dfail:0 fail:8 skip:1097 time:9313s
> >>
> >> == Logs ==
> >>
> >> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6930/shards.html
> >
> > Looking at the results we go from
> > <7>[ 2.822784] [drm:i915_ggtt_probe_hw [i915]] GTT stolen size = 128M
> > <7>[ 2.826115] [drm:i915_gem_init_stolen [i915]] Stolen reserved area
> > [0x0000000001100000 - 0x0000000001200000] outside stolen memory
> > [0x00000000c7a00000 - 0x00000000cfa00000]
> >
> > to
> > <7>[ 2.909693] [drm:i915_ggtt_probe_hw [i915]] GTT stolen size = 128M
> > <7>[ 2.912226] [drm:i915_gem_init_stolen [i915]] Memory reserved for
> > graphics device: 131072K, usable: 131072K
> >
> > on shard-snb6 at least.
> >
> > After going through the dmesgs for all the other machines we have in ci,
> > it doesn't look like there were any other changes in the amount of stolen
> > memory we detect (well, couldn't check shard-glkb due to lack fo results).
>
> There is GLK in Farm1, so you can check the bootlogs from fast-feedback
> run if that part is what you're interested in. All the other gens too.
I did check all the BAT runs. But I have no idea if the glks there are
the same board as what we have as gklb in the shard. So not sure if I
actually checked all the N machine types we have, or just N-1.
--
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:[~2017-11-03 10:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 15:17 [PATCH 1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not Ville Syrjala
2017-11-02 15:17 ` [PATCH 2/3] drm/i915: Make the report about a bogus stolen reserved area an error Ville Syrjala
2017-11-14 20:33 ` Paulo Zanoni
2017-11-14 20:41 ` Ville Syrjälä
2017-11-02 15:17 ` [PATCH 3/3] drm/i915: Use ELK stolen memory reserved detection for ILK Ville Syrjala
2017-11-14 20:59 ` Paulo Zanoni
2017-11-14 21:19 ` Ville Syrjälä
2017-11-02 15:38 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not Patchwork
2017-11-02 16:34 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-02 17:08 ` Ville Syrjälä
2017-11-03 7:19 ` Saarinen, Jani
2017-11-03 8:18 ` Tomi Sarvela
2017-11-03 10:41 ` Ville Syrjälä [this message]
2017-11-03 11:14 ` Tomi Sarvela
2017-11-03 10:43 ` Petri Latvala
2017-11-03 11:33 ` Tomi Sarvela
2017-11-03 12:53 ` Tomi Sarvela
2017-11-03 12:52 ` ✓ Fi.CI.IGT: success " Patchwork
2017-11-14 20:12 ` [PATCH 1/3] " Paulo Zanoni
2017-11-14 20:19 ` Chris Wilson
2017-11-14 20:29 ` Paulo Zanoni
2017-11-14 20:41 ` Chris Wilson
2017-11-14 20:34 ` Ville Syrjälä
2017-11-14 20:44 ` Paulo Zanoni
2017-11-14 21:38 ` Ville Syrjälä
2017-11-15 17:11 ` Ville Syrjälä
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=20171103104136.GV10981@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