From: kernel test robot <oliver.sang@intel.com>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [linyunsheng:pcp_test] 8991ea0d3b: kernel_BUG_at_mm/page_alloc.c
Date: Mon, 26 Feb 2024 22:38:10 +0800 [thread overview]
Message-ID: <202402262127.e8ae2f80-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel_BUG_at_mm/page_alloc.c" on:
commit: 8991ea0d3bba6e332066006c4d225a8ed579c715 ("pcp page split")
https://github.com/gestionlin/linux.git pcp_test
in testcase: boot
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)
+------------------------------------------+------------+------------+
| | 1eaa1d5e01 | 8991ea0d3b |
+------------------------------------------+------------+------------+
| boot_successes | 13 | 0 |
| boot_failures | 0 | 13 |
| kernel_BUG_at_mm/page_alloc.c | 0 | 13 |
| invalid_opcode:#[##] | 0 | 13 |
| RIP:__rmqueue_pcplist_split | 0 | 13 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 13 |
+------------------------------------------+------------+------------+
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/202402262127.e8ae2f80-lkp@intel.com
[ 8.841950][ T0] ------------[ cut here ]------------
[ 8.842971][ T0] kernel BUG at mm/page_alloc.c:2842!
[ 8.843990][ T0] invalid opcode: 0000 [#1] SMP
[ 8.844869][ T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.0-rc5-00331-g8991ea0d3bba #1
[ 8.845853][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 8.845853][ T0] RIP: __rmqueue_pcplist_split+0x3d5/0x440
[ 8.845853][ T0] Code: 8b 4c 24 28 4c 8b 44 24 20 8b 4c 24 18 44 8b 54 24 14 48 8b 3c 24 e9 5e fe ff ff 48 c7 c6 18 d7 f8 88 4c 89 f7 e8 eb a6 fc ff <0f> 0b 44 89 ca 44 89 ee 4c 89 f7 4c 89 44 24 18 89 4c 24 14 44 89
All code
========
0: 8b 4c 24 28 mov 0x28(%rsp),%ecx
4: 4c 8b 44 24 20 mov 0x20(%rsp),%r8
9: 8b 4c 24 18 mov 0x18(%rsp),%ecx
d: 44 8b 54 24 14 mov 0x14(%rsp),%r10d
12: 48 8b 3c 24 mov (%rsp),%rdi
16: e9 5e fe ff ff jmp 0xfffffffffffffe79
1b: 48 c7 c6 18 d7 f8 88 mov $0xffffffff88f8d718,%rsi
22: 4c 89 f7 mov %r14,%rdi
25: e8 eb a6 fc ff call 0xfffffffffffca715
2a:* 0f 0b ud2 <-- trapping instruction
2c: 44 89 ca mov %r9d,%edx
2f: 44 89 ee mov %r13d,%esi
32: 4c 89 f7 mov %r14,%rdi
35: 4c 89 44 24 18 mov %r8,0x18(%rsp)
3a: 89 4c 24 14 mov %ecx,0x14(%rsp)
3e: 44 rex.R
3f: 89 .byte 0x89
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: 44 89 ca mov %r9d,%edx
5: 44 89 ee mov %r13d,%esi
8: 4c 89 f7 mov %r14,%rdi
b: 4c 89 44 24 18 mov %r8,0x18(%rsp)
10: 89 4c 24 14 mov %ecx,0x14(%rsp)
14: 44 rex.R
15: 89 .byte 0x89
[ 8.845853][ T0] RSP: 0000:ffffffff89403bc0 EFLAGS: 00010296
[ 8.845853][ T0] RAX: 0000000000000000 RBX: ffffea0004119e08 RCX: ffffffff89403b34
[ 8.845853][ T0] RDX: 0000000000000001 RSI: ffffffff8984d940 RDI: ffffffff89462890
[ 8.845853][ T0] RBP: ffff88842fc32bc0 R08: 0000000000000000 R09: 0000000000000002
[ 8.845853][ T0] R10: 00000000a5fa65bd R11: 00000000f812dbd9 R12: 0000000000000004
[ 8.845853][ T0] R13: ffff88842fc32c38 R14: ffffea0004119e00 R15: 0000000000000001
[ 8.845853][ T0] FS: 0000000000000000(0000) GS:ffff88842fc00000(0000) knlGS:0000000000000000
[ 8.845853][ T0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 8.845853][ T0] CR2: ffff88843ffff000 CR3: 000000039d68c000 CR4: 00000000000406f0
[ 8.845853][ T0] Call Trace:
[ 8.845853][ T0] <TASK>
[ 8.845853][ T0] ? die (arch/x86/kernel/dumpstack.c:421 arch/x86/kernel/dumpstack.c:434 arch/x86/kernel/dumpstack.c:447)
[ 8.845853][ T0] ? do_trap (arch/x86/kernel/traps.c:113 arch/x86/kernel/traps.c:154)
[ 8.845853][ T0] ? __rmqueue_pcplist_split+0x3d5/0x440
[ 8.845853][ T0] ? do_error_trap (arch/x86/include/asm/traps.h:58 arch/x86/kernel/traps.c:175)
[ 8.845853][ T0] ? __rmqueue_pcplist_split+0x3d5/0x440
[ 8.845853][ T0] ? exc_invalid_op (arch/x86/kernel/traps.c:266)
[ 8.845853][ T0] ? __rmqueue_pcplist_split+0x3d5/0x440
[ 8.845853][ T0] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:568)
[ 8.845853][ T0] ? __rmqueue_pcplist_split+0x3d5/0x440
[ 8.845853][ T0] rmqueue+0x476/0x1780
[ 8.845853][ T0] ? free_unref_page (arch/x86/include/asm/preempt.h:84 mm/page_alloc.c:2509)
[ 8.845853][ T0] ? __lock_release+0x67/0x180
[ 8.845853][ T0] ? validate_chain (kernel/locking/lockdep.c:3762 kernel/locking/lockdep.c:3782 kernel/locking/lockdep.c:3837)
[ 8.845853][ T0] get_page_from_freelist (mm/page_alloc.c:3391)
[ 8.845853][ T0] __alloc_pages (mm/page_alloc.c:4654)
[ 8.845853][ T0] allocate_slab (include/linux/gfp.h:238 include/linux/gfp.h:261 mm/slub.c:2190 mm/slub.c:2354)
[ 8.845853][ T0] slab_alloc_node+0x13e/0x2c0
[ 8.845853][ T0] kmalloc_trace (mm/slub.c:4010)
[ 8.845853][ T0] kernfs_create_root (fs/kernfs/dir.c:959)
[ 8.845853][ T0] sysfs_init (fs/sysfs/mount.c:101)
[ 8.845853][ T0] ? sysfs_init (fs/sysfs/mount.c:101)
[ 8.845853][ T0] mnt_init (fs/namespace.c:5186)
[ 8.845853][ T0] vfs_caches_init (fs/dcache.c:3184)
[ 8.845853][ T0] start_kernel (init/main.c:1057)
[ 8.845853][ T0] x86_64_start_reservations (arch/x86/kernel/head64.c:543)
[ 8.845853][ T0] x86_64_start_kernel (arch/x86/kernel/head64.c:485 (discriminator 17))
[ 8.845853][ T0] secondary_startup_64_no_verify (arch/x86/kernel/head_64.S:461)
[ 8.845853][ T0] </TASK>
[ 8.845853][ T0] Modules linked in:
[ 8.845862][ T0] ---[ end trace 0000000000000000 ]---
[ 8.846851][ T0] RIP: __rmqueue_pcplist_split+0x3d5/0x440
[ 8.848228][ T0] Code: 8b 4c 24 28 4c 8b 44 24 20 8b 4c 24 18 44 8b 54 24 14 48 8b 3c 24 e9 5e fe ff ff 48 c7 c6 18 d7 f8 88 4c 89 f7 e8 eb a6 fc ff <0f> 0b 44 89 ca 44 89 ee 4c 89 f7 4c 89 44 24 18 89 4c 24 14 44 89
All code
========
0: 8b 4c 24 28 mov 0x28(%rsp),%ecx
4: 4c 8b 44 24 20 mov 0x20(%rsp),%r8
9: 8b 4c 24 18 mov 0x18(%rsp),%ecx
d: 44 8b 54 24 14 mov 0x14(%rsp),%r10d
12: 48 8b 3c 24 mov (%rsp),%rdi
16: e9 5e fe ff ff jmp 0xfffffffffffffe79
1b: 48 c7 c6 18 d7 f8 88 mov $0xffffffff88f8d718,%rsi
22: 4c 89 f7 mov %r14,%rdi
25: e8 eb a6 fc ff call 0xfffffffffffca715
2a:* 0f 0b ud2 <-- trapping instruction
2c: 44 89 ca mov %r9d,%edx
2f: 44 89 ee mov %r13d,%esi
32: 4c 89 f7 mov %r14,%rdi
35: 4c 89 44 24 18 mov %r8,0x18(%rsp)
3a: 89 4c 24 14 mov %ecx,0x14(%rsp)
3e: 44 rex.R
3f: 89 .byte 0x89
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: 44 89 ca mov %r9d,%edx
5: 44 89 ee mov %r13d,%esi
8: 4c 89 f7 mov %r14,%rdi
b: 4c 89 44 24 18 mov %r8,0x18(%rsp)
10: 89 4c 24 14 mov %ecx,0x14(%rsp)
14: 44 rex.R
15: 89 .byte 0x89
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240226/202402262127.e8ae2f80-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-26 14:38 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=202402262127.e8ae2f80-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=linyunsheng@huawei.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).