[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj2SbVnsO7yxgaD20HBaH=0rNM60nD92+BDSwQxofd9SQ@mail.gmail.com>
Date: Tue, 12 Oct 2021 11:34:19 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>
Cc: LKML <linux-kernel@...r.kernel.org>, Gavin Shan <gshan@...hat.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Gerald Schaefer <gerald.schaefer@...ux.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [BUG] WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:493
Adding x86 people (VM in particular). The tests were written primarily
for ARM, but should work on x86 too.
That warning seems to be due to pud_set_huge() failing (the "line 438"
one I don't know what it is - there's no warning on that line in my
tree, so I worry a bit that Steven has other things in his tree).
On x86, that can fail due to mtrr differences, or if there's already
an entry there. Neither _should_ be an issue during the boot-time
tests, but who knows..
Or there's something wrong with the tests. The fact that it's not
repeatable despite being a boot-time thing is a bit odd.
Linus
On Tue, Oct 12, 2021 at 11:11 AM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> My tests have been triggering on this every so often. My code is based on
> v5.15-rc3. Note, this is not fully reproducible.
>
> I also get errors an mm/debug_vm_pgtable.c:438
>
> And it also triggers the WARN_ON()s after that as well.
>
> Always happens at the debug_vm_pgtable() during boot up.
>
> Here's the last splat:
>
> ------------[ cut here ]------------
> WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:492 debug_vm_pgtable+0x1312/0x1693
> Modules linked in:
> CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.15.0-rc3-test+ #24
> Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
> RIP: 0010:debug_vm_pgtable+0x1312/0x1693
> Code: 38 ff ff ff 48 c7 00 00 00 00 00 48 8b 75 b8 48 8b 95 78 ff ff ff 48 8b bd 38 ff ff ff 48 c1 e6 0c e8 62 4e 62 fe 85 c0 75 02 <0f> 0b 48 8b bd 38 ff ff ff e8 e0 50 62 fe 85 c0 75 02 0f 0b 48 8b
> RSP: 0000:ffffa1eac0033da8 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: bffffffffffffff7 RCX: 0000000000000000
> RDX: ffffffffffe00000 RSI: ffffffff8bb477d0 RDI: 0000000000000007
> RBP: ffffa1eac0033e98 R08: ffffa1eac0033d23 R09: 000000021ee00000
> R10: 000000021effffff R11: 0000000000000000 R12: ffff8cf1436da538
> R13: 00003e8b00000000 R14: 000fffffffe00000 R15: 0000000000000027
> FS: 0000000000000000(0000) GS:ffff8cf256800000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000020f612001 CR4: 00000000001706e0
> Call Trace:
> ? destroy_args+0x281/0x281
> do_one_initcall+0x68/0x2d0
> ? rcu_read_lock_sched_held+0x46/0x80
> kernel_init_freeable+0x1a5/0x1f4
> ? rest_init+0x280/0x280
> kernel_init+0x1a/0x120
> ret_from_fork+0x22/0x30
> irq event stamp: 880991
> hardirqs last enabled at (881001): [<ffffffff8a1096ef>] __up_console_sem+0x6f/0x80
> hardirqs last disabled at (881016): [<ffffffff8a1096d4>] __up_console_sem+0x54/0x80
> softirqs last enabled at (881014): [<ffffffff8a097033>] irq_exit_rcu+0xa3/0xd0
> softirqs last disabled at (881009): [<ffffffff8a097033>] irq_exit_rcu+0xa3/0xd0
> ---[ end trace 731534acace262b5 ]---
> ------------[ cut here ]------------
> WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:493 debug_vm_pgtable+0x1324/0x1693
> Modules linked in:
> CPU: 3 PID: 1 Comm: swapper/0 Tainted: G W 5.15.0-rc3-test+ #24
> Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
> RIP: 0010:debug_vm_pgtable+0x1324/0x1693
> Code: 78 ff ff ff 48 8b bd 38 ff ff ff 48 c1 e6 0c e8 62 4e 62 fe 85 c0 75 02 0f 0b 48 8b bd 38 ff ff ff e8 e0 50 62 fe 85 c0 75 02 <0f> 0b 48 8b 85 38 ff ff ff 48 8b 00 48 a9 9f ff ff ff 74 02 0f 0b
> RSP: 0000:ffffa1eac0033da8 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: bffffffffffffff7 RCX: 0000000000000000
> RDX: ffffffffffe00000 RSI: ffffffff8bb477d0 RDI: ffff8cf1436db160
> RBP: ffffa1eac0033e98 R08: 0000000000000000 R09: 000000021ee00000
> R10: 000000021effffff R11: 0000000000000000 R12: ffff8cf1436da538
> R13: 00003e8b00000000 R14: 000fffffffe00000 R15: 0000000000000027
> FS: 0000000000000000(0000) GS:ffff8cf256800000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000020f612001 CR4: 00000000001706e0
> Call Trace:
> ? destroy_args+0x281/0x281
> do_one_initcall+0x68/0x2d0
> ? rcu_read_lock_sched_held+0x46/0x80
> kernel_init_freeable+0x1a5/0x1f4
> ? rest_init+0x280/0x280
> kernel_init+0x1a/0x120
> ret_from_fork+0x22/0x30
> irq event stamp: 881327
> hardirqs last enabled at (881337): [<ffffffff8a1096ef>] __up_console_sem+0x6f/0x80
> hardirqs last disabled at (881352): [<ffffffff8a1096d4>] __up_console_sem+0x54/0x80
> softirqs last enabled at (881350): [<ffffffff8a097033>] irq_exit_rcu+0xa3/0xd0
> softirqs last disabled at (881345): [<ffffffff8a097033>] irq_exit_rcu+0xa3/0xd0
> ---[ end trace 731534acace262b6 ]---
>
> Config attached (this is x86_64).
>
> -- Steve
Powered by blists - more mailing lists