[Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not

Tomi Sarvela tomi.p.sarvela at intel.com
Fri Nov 3 08:18:32 UTC 2017


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?

> 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.

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).

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.

Tomi
-- 
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo


More information about the Intel-gfx mailing list