From: kernel test robot <oliver.sang@intel.com>
To: Taotao Chen <chentaotao@didiglobal.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
<intel-gfx@lists.freedesktop.org>, <oliver.sang@intel.com>
Subject: [linus:master] [drm/i915] 048832a3f4: assertion_failure
Date: Fri, 8 Aug 2025 16:38:52 +0800 [thread overview]
Message-ID: <202508081029.343192ec-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "assertion_failure" on:
commit: 048832a3f4003113c3a0f060b08376c103622099 ("drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 479058002c32b77acac43e883b92174e22c4be2d]
[test failed on linux-next/master b7d4e259682caccb51a25283655f2c8f02e32d23]
in testcase: igt
version: igt-x86_64-a53a2b478-1_20250803
with following parameters:
group: group-24
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 20 threads 1 sockets (Commet Lake) with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202508081029.343192ec-lkp@intel.com
user :err : [ 80.799062] grep: warning: ? at start of expression
user :err : [ 80.807324] grep: warning: ? at start of expression
user :notice: [ 93.658557] (gen9_exec_parse:1321) ioctl_wrappers-CRITICAL: Test assertion failure function gem_write, file ../lib/ioctl_wrappers.c:416:
user :notice: [ 93.675127] (gen9_exec_parse:1321) ioctl_wrappers-CRITICAL: Failed assertion: ret == 0 || ret == -EOPNOTSUPP
user :notice: [ 93.688924] (gen9_exec_parse:1321) ioctl_wrappers-CRITICAL: Last errno: 5, Input/output error
user :info : [ 93.698755] [IGT] gen9_exec_parse: finished subtest bb-large, FAIL
user :notice: [ 93.700815] Subtest bb-large failed.
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250808/202508081029.343192ec-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-08 8:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202508081029.343192ec-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=chentaotao@didiglobal.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.