From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
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: Thu, 2 Nov 2017 19:08:27 +0200 [thread overview]
Message-ID: <20171102170827.GQ10981@intel.com> (raw)
In-Reply-To: <20171102163426.9895.72028@emeril.freedesktop.org>
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?
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.
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.
>
> 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).
--
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-02 17:08 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ä [this message]
2017-11-03 7:19 ` Saarinen, Jani
2017-11-03 8:18 ` Tomi Sarvela
2017-11-03 10:41 ` Ville Syrjälä
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=20171102170827.GQ10981@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