All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: <linux+lkp@weissschuh.net>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [thomas-weissschuh:b4/module-hashes] [module]  967cf780de: ltp.lock_torture.fail
Date: Wed, 13 May 2026 15:08:18 +0800	[thread overview]
Message-ID: <202605131448.9fc0ef33-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "ltp.lock_torture.fail" on:

commit: 967cf780de6fd48a69e8096342cf0f9b9292ee7b ("module: Introduce hash-based integrity checking")
https://git.kernel.org/cgit/linux/kernel/git/thomas.weissschuh/linux.git b4/module-hashes

in testcase: ltp
version: 
with following parameters:

	test: kernel_misc/lock_torture



config: x86_64-rhel-9.4-ltp
compiler: gcc-14
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4790T CPU @ 2.70GHz (Haswell) 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/202605131448.9fc0ef33-lkp@intel.com


2026-05-09 19:10:48 export LTP_RUNTIME_MUL=2
2026-05-09 19:10:48 export LTPROOT=/lkp/benchmarks/ltp
2026-05-09 19:10:48 kirk -f temp_single_test
Host information
	Hostname:   lkp-hsw-d05
	Python:     3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
	Directory:  /tmp/kirk.root/tmpav49d11b

Connecting to SUT: default

Suite: temp_single_test
───────────────────────
^[[1;37mlock_torture: ^[[0m^[[1;31mfail^[[0m | ^[[1;33mtainted^[[0m  (6m 8s)

Execution time: 6m 8s

Disconnecting from SUT: default

Target information
──────────────────
Kernel:   Linux 7.1.0-rc1+ #1 SMP PREEMPT_DYNAMIC Sun May 10 02:46:19 CST 2026
Cmdline:  ip=::::lkp-hsw-d05::dhcp
          root=/dev/ram0
          RESULT_ROOT=/result/ltp/kernel_misc_lock_torture/lkp-hsw-d05/debian-13-x86_64-20250902.cgz/x86_64-rhel-9.4-ltp/gcc-14/967cf780de6fd48a69e8096342cf0f9b9292ee7b/0
          BOOT_IMAGE=/pkg/linux/x86_64-rhel-9.4-ltp/gcc-14/967cf780de6fd48a69e8096342cf0f9b9292ee7b/vmlinuz-7.1.0-rc1+
          branch=linux-devel/devel-hourly-20260508-100921
          job=/lkp/jobs/scheduled/lkp-hsw-d05/ltp-kernel_misc_lock_torture-debian-13-x86_64-20250902.cgz-967cf780de6f-20260510-27890-1e8k4j9-0.yaml
          user=lkp
          ARCH=x86_64
          kconfig=x86_64-rhel-9.4-ltp
          commit=967cf780de6fd48a69e8096342cf0f9b9292ee7b
          intremap=posted_msi
          max_uptime=14400
          LKP_SERVER=internal-lkp-server
          nokaslr
          selinux=0
          debug
          apic=debug
          sysrq_always_enabled
          rcupdate.rcu_cpu_stall_timeout=100
          net.ifnames=0
          printk.devkmsg=on
          panic=-1
          softlockup_panic=1
          nmi_watchdog=panic
          oops=panic
          load_ramdisk=2
          prompt_ramdisk=0
          drbd.minor_count=8
          systemd.log_level=err
          ignore_loglevel
          console=tty0
          earlyprintk=ttyS0,115200
          console=ttyS0,115200
          vga=normal
          rw
          keep_initrds=/osimage/pkg/debian-13-x86_64-20250902.cgz/ltp-x86_64-92ea0639e-1_20260301.cgz
Machine:  unknown
Arch:     x86_64
RAM:      14040280 kB
Swap:     0 kB
Distro:   debian 13

────────────────────────
      TEST SUMMARY
────────────────────────
Suite:   temp_single_test
Runtime: 6m 8s
Runs:    1

Results:
    Passed:   0
    Failed:   6
    Broken:   0
    Skipped:  0
    Warnings: 0

^[[1;31mFailures:^[[0m
    • lock_torture

Session stopped



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260513/202605131448.9fc0ef33-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2026-05-13  7:08 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=202605131448.9fc0ef33-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=linux+lkp@weissschuh.net \
    --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.