From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH topic/core-for-CI] drm/i915/dg2: Add relocation exception
Date: Fri, 18 Feb 2022 16:02:19 -0800 [thread overview]
Message-ID: <87ley77mgk.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220218223853.939464-1-lucas.demarchi@intel.com>
On Fri, 18 Feb 2022 14:38:53 -0800, Lucas De Marchi wrote:
>
> The move to softpin in igt is ongoing and should land soon.
> Meanwhile, like was done for ADL and RKL, add an exception to allow
> running the igt display tests before that conversion is complete
> so we can unblock CI.
One example failure we see on DG2 if we don't do this (reported by Lucas):
IGT-Version: 1.26-g9cb64a75 (x86_64) (Linux: 5.17.0-rc4-demarchi+ x86_64)
(testdisplay:10068) ioctl_wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ../lib/ioctl_wrappers.c:674:
(testdisplay:10068) ioctl_wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0
(testdisplay:10068) ioctl_wrappers-CRITICAL: error: -22 != 0
Stack trace:
#0 ../lib/igt_core.c:1754 __igt_fail_assert()
#1 [gem_execbuf+0x48]
#2 ../lib/intel_batchbuffer.c:1053 igt_blitter_fast_copy__raw()
#3 ../lib/igt_fb.c:2497 blitcopy()
#4 ../lib/igt_fb.c:2646 setup_linear_mapping()
#5 ../lib/igt_fb.c:2671 create_cairo_surface__gpu()
#6 ../lib/igt_fb.c:3959 igt_get_cairo_surface()
#7 ../lib/igt_fb.c:3987 igt_get_cairo_ctx()
#8 ../lib/igt_fb.c:1980 igt_create_pattern_fb()
#9 ../tests/testdisplay.c:271 set_mode()
#10 ../tests/testdisplay.c:511 update_display()
#11 ../tests/testdisplay.c:763 main()
#12 ../csu/libc-start.c:342 __libc_start_main()
#13 [_start+0x2e]
Test testdisplay failed
next prev parent reply other threads:[~2022-02-19 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 22:38 [Intel-gfx] [PATCH topic/core-for-CI] drm/i915/dg2: Add relocation exception Lucas De Marchi
2022-02-19 0:02 ` Dixit, Ashutosh [this message]
2022-02-19 4:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-02-19 20:48 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-21 5:42 ` [Intel-gfx] [PATCH topic/core-for-CI] " Lucas De Marchi
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=87ley77mgk.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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