From: kernel test robot <oliver.sang@intel.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Mike Rapoport <rppt@kernel.org>, <oliver.sang@intel.com>
Subject: [rppt:hugetlb-init/v0] [dev] 76602f76e0: kernel_BUG_at_arch/x86/mm/init_32.c
Date: Mon, 29 Dec 2025 14:10:12 +0800 [thread overview]
Message-ID: <202512291348.f898b0e5-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel_BUG_at_arch/x86/mm/init_32.c" on:
commit: 76602f76e089f4ee2c930724377963f43d513b47 ("dev: call arch_zone_limits_init() from mm initialization")
https://git.kernel.org/cgit/linux/kernel/git/rppt/linux.git hugetlb-init/v0
in testcase: boot
config: i386-randconfig-011-20251225
compiler: clang-20
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+------------------------------------------+------------+------------+
| | b7e81cbba5 | 76602f76e0 |
+------------------------------------------+------------+------------+
| boot_successes | 21 | 0 |
| boot_failures | 0 | 12 |
| kernel_BUG_at_arch/x86/mm/init_32.c | 0 | 12 |
| Oops:invalid_opcode:#[##] | 0 | 12 |
| EIP:arch_mm_preinit | 0 | 12 |
| Kernel_panic-not_syncing:Fatal_exception | 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/202512291348.f898b0e5-lkp@intel.com
[ 0.234917][ T0] ------------[ cut here ]------------
[ 0.236290][ T0] kernel BUG at arch/x86/mm/init_32.c:689!
[ 0.237768][ T0] Oops: invalid opcode: 0000 [#1]
[ 0.238916][ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.19.0-rc1-00022-g76602f76e089 #1 PREEMPT(undef) c8d24fbcd25ff6aea7081c5f4582d232be127691
[ 0.242532][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 0.245122][ T0] EIP: arch_mm_preinit (arch/x86/mm/init_32.c:689)
[ 0.246338][ T0] Code: c5 fd 83 c4 08 5d 31 c0 31 c9 31 d2 c3 90 90 90 e8 87 87 ce fd 55 89 e5 e8 bb d7 fe ff 83 3d bc 76 ba c3 00 74 04 5d 31 c0 c3 <0f> 0b b8 38 ab e0 c2 e8 1a b6 c6 fd 90 90 e8 5f 87 ce fd 55 89 e5
All code
========
0: c5 fd 83 (bad)
3: c4 (bad)
4: 08 5d 31 or %bl,0x31(%rbp)
7: c0 31 c9 shlb $0xc9,(%rcx)
a: 31 d2 xor %edx,%edx
c: c3 ret
d: 90 nop
e: 90 nop
f: 90 nop
10: e8 87 87 ce fd call 0xfffffffffdce879c
15: 55 push %rbp
16: 89 e5 mov %esp,%ebp
18: e8 bb d7 fe ff call 0xfffffffffffed7d8
1d: 83 3d bc 76 ba c3 00 cmpl $0x0,-0x3c458944(%rip) # 0xffffffffc3ba76e0
24: 74 04 je 0x2a
26: 5d pop %rbp
27: 31 c0 xor %eax,%eax
29: c3 ret
2a:* 0f 0b ud2 <-- trapping instruction
2c: b8 38 ab e0 c2 mov $0xc2e0ab38,%eax
31: e8 1a b6 c6 fd call 0xfffffffffdc6b650
36: 90 nop
37: 90 nop
38: e8 5f 87 ce fd call 0xfffffffffdce879c
3d: 55 push %rbp
3e: 89 e5 mov %esp,%ebp
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: b8 38 ab e0 c2 mov $0xc2e0ab38,%eax
7: e8 1a b6 c6 fd call 0xfffffffffdc6b626
c: 90 nop
d: 90 nop
e: e8 5f 87 ce fd call 0xfffffffffdce8772
13: 55 push %rbp
14: 89 e5 mov %esp,%ebp
[ 0.250972][ T0] EAX: 00000000 EBX: 00020800 ECX: 00000000 EDX: 00000000
[ 0.252639][ T0] ESI: 00000000 EDI: ffffffff EBP: c2dd7f78 ESP: c2dd7f78
[ 0.254325][ T0] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00210046
[ 0.255951][ T0] CR0: 80050033 CR2: 00000000 CR3: 034b1000 CR4: 00000090
[ 0.256842][ T0] Call Trace:
[ 0.257250][ T0] mm_core_init (mm/mm_init.c:2706)
[ 0.257783][ T0] start_kernel (init/main.c:1068)
[ 0.258342][ T0] i386_start_kernel (arch/x86/kernel/head32.c:79)
[ 0.258931][ T0] startup_32_smp (arch/x86/kernel/head_32.S:293)
[ 0.259518][ T0] Modules linked in:
[ 0.260018][ T0] ---[ end trace 0000000000000000 ]---
[ 0.260657][ T0] EIP: arch_mm_preinit (arch/x86/mm/init_32.c:689)
[ 0.261245][ T0] Code: c5 fd 83 c4 08 5d 31 c0 31 c9 31 d2 c3 90 90 90 e8 87 87 ce fd 55 89 e5 e8 bb d7 fe ff 83 3d bc 76 ba c3 00 74 04 5d 31 c0 c3 <0f> 0b b8 38 ab e0 c2 e8 1a b6 c6 fd 90 90 e8 5f 87 ce fd 55 89 e5
All code
========
0: c5 fd 83 (bad)
3: c4 (bad)
4: 08 5d 31 or %bl,0x31(%rbp)
7: c0 31 c9 shlb $0xc9,(%rcx)
a: 31 d2 xor %edx,%edx
c: c3 ret
d: 90 nop
e: 90 nop
f: 90 nop
10: e8 87 87 ce fd call 0xfffffffffdce879c
15: 55 push %rbp
16: 89 e5 mov %esp,%ebp
18: e8 bb d7 fe ff call 0xfffffffffffed7d8
1d: 83 3d bc 76 ba c3 00 cmpl $0x0,-0x3c458944(%rip) # 0xffffffffc3ba76e0
24: 74 04 je 0x2a
26: 5d pop %rbp
27: 31 c0 xor %eax,%eax
29: c3 ret
2a:* 0f 0b ud2 <-- trapping instruction
2c: b8 38 ab e0 c2 mov $0xc2e0ab38,%eax
31: e8 1a b6 c6 fd call 0xfffffffffdc6b650
36: 90 nop
37: 90 nop
38: e8 5f 87 ce fd call 0xfffffffffdce879c
3d: 55 push %rbp
3e: 89 e5 mov %esp,%ebp
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: b8 38 ab e0 c2 mov $0xc2e0ab38,%eax
7: e8 1a b6 c6 fd call 0xfffffffffdc6b626
c: 90 nop
d: 90 nop
e: e8 5f 87 ce fd call 0xfffffffffdce8772
13: 55 push %rbp
14: 89 e5 mov %esp,%ebp
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251229/202512291348.f898b0e5-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-29 6:10 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=202512291348.f898b0e5-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=rppt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox