[Intel-gfx] [drm-intel:drm-intel-gt-next] [drm/i915] [confidence: ] 9bb66c179f: assertion_failure

[Jani Nikula]

On Thu, 07 Dec 2023, kernel test robot <oliver.sang at intel.com> wrote:
> Hello,
>
> kernel test robot noticed "assertion_failure" on:
>
> commit: 9bb66c179f50e61df20ba13c9b34ca17d00b05fb ("drm/i915: Reserve some kernel space per vm")
> git://anongit.freedesktop.org/drm-intel drm-intel-gt-next
>
> in testcase: igt

So the kernel test robot runs igt. I've seen a handful of reports over
the years, but not a whole lot. If you run it even semi-regularly, I
would have expected more. What's the deal here?

There's clearly overlap with what our CI is doing. Maybe better
coordination would be useful? Especially wrt reporting. I'm not sure if
anyone's going to track these mails.

Cc: Ewelina

> version: igt-x86_64-0f075441-1_20230520

That's six months old and more than 1k commits behind. The results are
going to be useless, I'm afraid.


BR,
Jani.


> with following parameters:
>
> 	group: group-04
>
>
>
> compiler: gcc-12
> test machine: 20 threads 1 sockets (Commet Lake) with 16G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
> we also observed below tests failed upon this commit while pass on parent.
>
> 8aa519f17512da50 9bb66c179f50e61df20ba13c9b3
> ---------------- ---------------------------
>        fail:runs  %reproduction    fail:runs
>            |             |             |
>            :6          100%           6:6     igt.api_intel_bb.bb-with-allocator.fail
>            :6          100%           6:6     igt.api_intel_bb.blit-noreloc-keep-cache.fail
>            :6          100%           6:6     igt.api_intel_bb.blit-noreloc-purge-cache.fail
>            :6          100%           6:6     igt.api_intel_bb.blit-reloc-purge-cache.fail
>            :6          100%           6:6     igt.api_intel_bb.delta-check.fail
>            :6          100%           6:6     igt.api_intel_bb.object-noreloc-keep-cache-simple.fail
>            :6          100%           6:6     igt.api_intel_bb.object-noreloc-purge-cache-simple.fail
>            :6           83%           5:6     igt.api_intel_bb.object-reloc-purge-cache.fail
>            :6          100%           6:6     igt.api_intel_bb.simple-bb-ctx.fail
>            :6          100%           6:6     igt.api_intel_bb.simple-bb.fail
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang at intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202312071643.321205c6-oliver.sang@intel.com
>
>
> [   43.922756][  T447]
> [   43.935008][  T447] IGT-Version: 1.27.1-g0f075441 (x86_64) (Linux: 6.6.0-rc7-01579-g9bb66c179f50 x86_64)
> [   43.935018][  T447]
> [   43.947248][  T447] Starting subtest: bb-with-allocator
> [   43.947258][  T447]
> [   43.956752][  T447] (api_intel_bb:857) intel_batchbuffer-CRITICAL: Test assertion failure function __intel_bb_add_object, file ../lib/intel_batchbuffer.c:1673:
> [   43.956762][  T447]
> [   43.974467][  T447] (api_intel_bb:857) intel_batchbuffer-CRITICAL: Failed assertion: allocated || reserved
> [   43.974477][  T447]
> [   43.987691][  T447] (api_intel_bb:857) intel_batchbuffer-CRITICAL: Can't get offset, allocated: 0, reserved: 0
> [   43.987706][  T447]
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20231207/202312071643.321205c6-oliver.sang@intel.com

-- 
Jani Nikula, Intel