mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Waiman Long <longman@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Waiman Long <longman@redhat.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v3 2/2] debugobjects: Allow object pool refill mostly in non-atomic context
Date: Tue, 24 Jun 2025 16:28:16 +0800	[thread overview]
Message-ID: <202506201449.f3047c4-lkp@intel.com> (raw)
In-Reply-To: <20250617053527.1223411-3-longman@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3410 bytes --]



Hello,

we don't have enough knowledge to understand why this patch causes seemingly
auto-reboot in this trinity tests. but the issue is quite persistent.

94d15b49922495cd 81c49454d188c6eb34bb736f432
---------------- ---------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
           :50         100%          50:50    last_state.is_incomplete_run
           :50          98%          50:50    last_state.running

we don't see hint from dmesg uploaded to [1], so we also attached one dmesg
from parent FYI in case we miss anything.


kernel test robot noticed "last_state.running" on:

commit: 81c49454d188c6eb34bb736f432e4b1ef623d70f ("[PATCH v3 2/2] debugobjects: Allow object pool refill mostly in non-atomic context")
url: https://github.com/intel-lab-lkp/linux/commits/Waiman-Long/debugobjects-Show-the-state-of-debug_objects_enabled/20250617-133635
base: https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
patch link: https://lore.kernel.org/all/20250617053527.1223411-3-longman@redhat.com/
patch subject: [PATCH v3 2/2] debugobjects: Allow object pool refill mostly in non-atomic context

in testcase: trinity
version: 
with following parameters:

	runtime: 300s
	group: group-01
	nr_groups: 5



config: i386-randconfig-004-20250618
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

(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/202506201449.f3047c4-lkp@intel.com


LKP: ttyS0: 246: Kernel tests: Boot OK!
LKP: ttyS0: 246: HOSTNAME vm-snb, MAC 52:54:00:12:34:56, kernel 6.16.0-rc2-00044-g81c49454d188 1

Poky (Yocto Project Reference Distro) 2.7+snapshot vm-snb /dev/ttyS0

vm-snb login: LKP: ttyS0: 246:  /lkp/lkp/src/bin/run-lkp /lkp/jobs/scheduled/vm-meta-243/trinity-group-01-5-300s-yocto-i386-minimal-20190520.cgz-i386-randconfig-004-20250618-81c49454d188-20250619-2383740-f5ihl3-14.yaml
[   13.087284][  T290] mkdir: can't create directory '/sys/kernel/debug': Operation not permitted
[   13.087284][  T290] mount: mounting debug on /sys/kernel/debug failed: No such file or directory
[   34.877921][ T3450] UDPLite: UDP-Lite is deprecated and scheduled to be removed in 2025, please contact the netdev mailing list
[   34.879165][ T3450] trinity-main uses obsolete (PF_INET,SOCK_PACKET)
[   34.931165][ T3450] UDPLite6: UDP-Lite is deprecated and scheduled to be removed in 2025, please contact the netdev mailing list
[   35.302518][ T3582] VFS: Warning: trinity-c0 using old stat() call. Recompile your binary.
[   35.303816][ T3582] VFS: Warning: trinity-c0 using old stat() call. Recompile your binary.
[   35.307560][ T3585] VFS: Warning: trinity-c3 using old stat() call. Recompile your binary.
[   35.308370][ T3585] VFS: Warning: trinity-c3 using old stat() call. Recompile your binary.
[   35.314526][ T3582] VFS: Warning: trinity-c0 using old stat() call. Recompile your binary.



[1]
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250620/202506201449.f3047c4-lkp@intel.com


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


[-- Attachment #2: dmesg-94d15b4992.xz --]
[-- Type: application/x-xz, Size: 12976 bytes --]

  reply	other threads:[~2025-06-24  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  5:35 [PATCH v3 0/2] " Waiman Long
2025-06-17  5:35 ` [PATCH v3 1/2] debugobjects: Show the state of debug_objects_enabled Waiman Long
2025-06-17  5:35 ` [PATCH v3 2/2] debugobjects: Allow object pool refill mostly in non-atomic context Waiman Long
2025-06-24  8:28   ` kernel test robot [this message]
2025-06-26 15:22   ` Thomas Gleixner

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=202506201449.f3047c4-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=longman@redhat.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®