From: kernel test robot <oliver.sang@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [jimc:dd-drm-fix] [dyndbg] 80a26374d2: BUG:sleeping_function_called_from_invalid_context_at_include/linux/sched/mm.h
Date: Wed, 28 Jan 2026 22:12:50 +0800 [thread overview]
Message-ID: <202601282112.3e252f09-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "BUG:sleeping_function_called_from_invalid_context_at_include/linux/sched/mm.h" on:
commit: 80a26374d24c6a7ca964ad427e3a54852f0803b8 ("dyndbg: walk dd_mod_map intervals in dynamic_debug_init()")
https://github.com/jimc/linux.git dd-drm-fix
in testcase: boot
config: i386-randconfig-012-20260127
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-------------------------------------------------------------------------------+------------+------------+
| | bd091f80c8 | 80a26374d2 |
+-------------------------------------------------------------------------------+------------+------------+
| BUG:sleeping_function_called_from_invalid_context_at_include/linux/sched/mm.h | 0 | 12 |
+-------------------------------------------------------------------------------+------------+------------+
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/202601282112.3e252f09-lkp@intel.com
[ 0.666972][ T1] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:323
[ 0.668055][ T1] in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0
[ 0.669517][ T1] preempt_count: 0, expected: 0
[ 0.670309][ T1] RCU nest depth: 1, expected: 0
[ 0.671155][ T1] 1 lock held by swapper/0/1:
[ 0.672117][ T1] #0: b2887bcc (rcu_read_lock){....}-{1:3}, at: dynamic_debug_init (lib/dynamic_debug.c:1797)
[ 0.673765][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.19.0-rc7-00040-g80a26374d24c #1 PREEMPT(lazy) e69b6cee1a878dce1581dfa5f5bb5383e6db0395
[ 0.676021][ T1] Call Trace:
[ 0.676021][ T1] dump_stack_lvl (lib/dump_stack.c:123 (discriminator 1))
[ 0.676021][ T1] dump_stack (lib/dump_stack.c:130)
[ 0.676021][ T1] __might_resched (kernel/sched/core.c:8830)
[ 0.676021][ T1] ? mtree_store_range (lib/maple_tree.c:5938)
[ 0.676021][ T1] __might_sleep (kernel/sched/core.c:8759 (discriminator 17))
[ 0.676021][ T1] __kmalloc_cache_noprof (include/linux/kernel.h:61 include/linux/sched/mm.h:323 mm/slub.c:4904 mm/slub.c:5239 mm/slub.c:5775)
[ 0.676021][ T1] ? ddebug_add_module (include/linux/slab.h:957 (discriminator 3) include/linux/slab.h:1094 (discriminator 3) lib/dynamic_debug.c:1577 (discriminator 3))
[ 0.676021][ T1] ddebug_add_module (include/linux/slab.h:957 (discriminator 3) include/linux/slab.h:1094 (discriminator 3) lib/dynamic_debug.c:1577 (discriminator 3))
[ 0.676021][ T1] dynamic_debug_init (lib/dynamic_debug.c:1811)
[ 0.676021][ T1] ? dynamic_debug_init_control (lib/dynamic_debug.c:1769)
[ 0.676021][ T1] do_one_initcall (init/main.c:1378)
[ 0.676021][ T1] ? __register_sysctl_init (fs/proc/proc_sysctl.c:1467)
[ 0.676021][ T1] ? rest_init (init/main.c:1570)
[ 0.676021][ T1] ? init_mm_internals (mm/vmstat.c:2304)
[ 0.676021][ T1] ? rest_init (init/main.c:1570)
[ 0.676021][ T1] kernel_init_freeable (init/main.c:1483 init/main.c:1677)
[ 0.676021][ T1] kernel_init (init/main.c:1580)
[ 0.676021][ T1] ret_from_fork (arch/x86/kernel/process.c:164)
[ 0.676021][ T1] ? rest_init (init/main.c:1570)
[ 0.676021][ T1] ret_from_fork_asm (arch/x86/entry/entry_32.S:737)
[ 0.676021][ T1] entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 0.676134][ T1]
[ 0.676575][ T1] =============================
[ 0.677188][ T1] [ BUG: Invalid wait context ]
[ 0.677997][ T1] 6.19.0-rc7-00040-g80a26374d24c #1 Tainted: G W
[ 0.679361][ T1] -----------------------------
[ 0.680021][ T1] swapper/0/1 is trying to lock:
[ 0.680021][ T1] b29409d4 (ddebug_lock){....}-{4:4}, at: ddebug_add_module (include/linux/list.h:191 lib/dynamic_debug.c:1601)
[ 0.680021][ T1] other info that might help us debug this:
[ 0.680021][ T1] context-{5:5}
[ 0.680021][ T1] 1 lock held by swapper/0/1:
[ 0.680021][ T1] #0: b2887bcc (rcu_read_lock){....}-{1:3}, at: dynamic_debug_init (lib/dynamic_debug.c:1797)
[ 0.680021][ T1] stack backtrace:
[ 0.680021][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G W 6.19.0-rc7-00040-g80a26374d24c #1 PREEMPT(lazy) e69b6cee1a878dce1581dfa5f5bb5383e6db0395
[ 0.680021][ T1] Tainted: [W]=WARN
[ 0.680021][ T1] Call Trace:
[ 0.680021][ T1] dump_stack_lvl (lib/dump_stack.c:124)
[ 0.680021][ T1] dump_stack (lib/dump_stack.c:130)
[ 0.680021][ T1] __lock_acquire (kernel/locking/lockdep.c:4832 kernel/locking/lockdep.c:4902 kernel/locking/lockdep.c:5187)
[ 0.680021][ T1] ? trace_preempt_on (kernel/trace/trace_preemptirq.c:122)
[ 0.680021][ T1] lock_acquire (kernel/locking/lockdep.c:470 kernel/locking/lockdep.c:5870)
[ 0.680021][ T1] ? ddebug_add_module (include/linux/list.h:191 lib/dynamic_debug.c:1601)
[ 0.680021][ T1] ? __mutex_lock (kernel/locking/mutex.c:614 kernel/locking/mutex.c:776)
[ 0.680021][ T1] __mutex_lock (arch/x86/include/asm/jump_label.h:37 include/trace/events/lock.h:95 kernel/locking/mutex.c:616 kernel/locking/mutex.c:776)
[ 0.680021][ T1] ? ddebug_add_module (include/linux/list.h:191 lib/dynamic_debug.c:1601)
[ 0.680021][ T1] ? ddebug_condense_sites (lib/dynamic_debug.c:1555)
[ 0.680021][ T1] ? ddebug_get_filename (lib/dynamic_debug.c:1520)
[ 0.680021][ T1] mutex_lock_nested (kernel/locking/mutex.c:829)
[ 0.680021][ T1] ? ddebug_add_module (include/linux/list.h:191 lib/dynamic_debug.c:1601)
[ 0.680021][ T1] ddebug_add_module (include/linux/list.h:191 lib/dynamic_debug.c:1601)
[ 0.680021][ T1] dynamic_debug_init (lib/dynamic_debug.c:1811)
[ 0.680021][ T1] ? dynamic_debug_init_control (lib/dynamic_debug.c:1769)
[ 0.680021][ T1] do_one_initcall (init/main.c:1378)
[ 0.680021][ T1] ? __register_sysctl_init (fs/proc/proc_sysctl.c:1467)
[ 0.680021][ T1] ? rest_init (init/main.c:1570)
[ 0.680021][ T1] ? init_mm_internals (mm/vmstat.c:2304)
[ 0.680021][ T1] ? rest_init (init/main.c:1570)
[ 0.680021][ T1] kernel_init_freeable (init/main.c:1483 init/main.c:1677)
[ 0.680021][ T1] kernel_init (init/main.c:1580)
[ 0.680021][ T1] ret_from_fork (arch/x86/kernel/process.c:164)
[ 0.680021][ T1] ? rest_init (init/main.c:1570)
[ 0.680021][ T1] ret_from_fork_asm (arch/x86/entry/entry_32.S:737)
[ 0.680021][ T1] entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 0.684801][ T1] Memory: 2985172K/3145208K available (15891K kernel code, 5186K rwdata, 5772K rodata, 1056K init, 7324K bss, 154192K reserved, 0K cma-reserved, 1978248K highmem)
[ 0.688021][ T1] devtmpfs: initialized
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260128/202601282112.3e252f09-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-28 14:13 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=202601282112.3e252f09-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=jim.cromie@gmail.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ukaszb@chromium.org \
/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.