[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211012151934.0f4aa9f4@gandalf.local.home>
Date: Tue, 12 Oct 2021 15:19:34 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: 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>,
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
On Tue, 12 Oct 2021 12:15:40 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> Or it's something specific to your setup, but that sounds unlikely.
>
> You might add some debugging to the x86 pud_set_huge() function,
> something like the attached (obviously entirely untested) patch.
I'll add this to the patches that get applied before my tests run (which
mostly just disable things unrelated to my code, like i915 warnings :-p)
But my box is continuing its test suite, so I'll add it when it finishes,
and then run more tests to try to trigger it again.
-- Steve
Powered by blists - more mailing lists