From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: "tzimmermann@suse.de" <tzimmermann@suse.de>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Regression on linux-next (next-20240506)
Date: Wed, 8 May 2024 09:34:48 +0000 [thread overview]
Message-ID: <SJ1PR11MB61294E38C4405716DE9BE2CBB9E52@SJ1PR11MB6129.namprd11.prod.outlook.com> (raw)
Hello Thomas,
Hope you are doing well.
This mail is regarding a regression we are seeing in our CI runs[1] on
linux-next repository.
Since the version next-20240506 [2], we are seeing the following regression
`````````````````````````````````````````````````````````````````````````````````
Starting dynamic subtest: gt_contexts
(i915_selftest:1107) igt_kmod-WARNING: i915: Unknown symbol acpi_video_unregister (err -2)
(i915_selftest:1107) igt_kmod-WARNING: i915: Unknown symbol acpi_video_register_backlight (err -2)
(i915_selftest:1107) igt_kmod-WARNING: i915: Unknown symbol __acpi_video_get_backlight_type (err -2)
(i915_selftest:1107) igt_kmod-WARNING: i915: Unknown symbol acpi_video_register (err -2)
(i915_selftest:1107) igt_kmod-CRITICAL: Test assertion failure function igt_kselftest_execute, file ../../../usr/src/igt-gpu-tools/lib/igt_kmod.c:1594:
(i915_selftest:1107) igt_kmod-CRITICAL: Failed assertion: err == 0
(i915_selftest:1107) igt_kmod-CRITICAL: kselftest "i915 igt__23__live_gt_contexts=1 live_selftests=-1 disable_display=1 st_filter=" failed: No such file or directory [2]
Dynamic subtest gt_contexts failed.
`````````````````````````````````````````````````````````````````````````````````
Details log can be found in [3].
After bisecting the tree, the following patch [4] seems to be the first "bad" commit
`````````````````````````````````````````````````````````````````````````````````````````````````````````
2fd001cd36005846caa6456fff1008c6f5bae9d4 is the first bad commit
commit 2fd001cd36005846caa6456fff1008c6f5bae9d4
Author: Thomas Zimmermann tzimmermann@suse.de
Date: Fri Mar 29 21:32:12 2024 +0100
arch: Rename fbdev header and source files
`````````````````````````````````````````````````````````````````````````````````````````````````````````
We also verified that if we revert the patch the issue is not seen.
Could you please check why the patch causes this regression and provide a fix if necessary?
Thank you.
Regards
Chaitanya
[1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
[2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20240506
[3] https://intel-gfx-ci.01.org/tree/linux-next/next-20240506/bat-mtlp-9/igt@i915_selftest@live@gt_contexts.html
[4] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20240506&id=2fd001cd36005846caa6456fff1008c6f5bae9d4
next reply other threads:[~2024-05-08 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:34 Borah, Chaitanya Kumar [this message]
2024-05-15 8:16 ` Regression on linux-next (next-20240506) Borah, Chaitanya Kumar
2024-05-15 8:54 ` Thomas Zimmermann
2024-05-15 11:36 ` Borah, Chaitanya Kumar
2024-05-15 11:38 ` Borah, Chaitanya Kumar
2024-05-15 12:36 ` Thomas Zimmermann
2024-05-16 11:04 ` Borah, Chaitanya Kumar
2024-05-16 11:20 ` Thomas Zimmermann
2024-05-15 13:56 ` ✗ Fi.CI.BUILD: failure for " Patchwork
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=SJ1PR11MB61294E38C4405716DE9BE2CBB9E52@SJ1PR11MB6129.namprd11.prod.outlook.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=suresh.kumar.kurmi@intel.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).