From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
Gavin Shan <gshan@redhat.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [BUG] WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:493
Date: Tue, 12 Oct 2021 15:19:34 -0400 [thread overview]
Message-ID: <20211012151934.0f4aa9f4@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wg6fw130AkO72GPFow9PHvP9odnC5LZ0UaY9bJQuF-C5A@mail.gmail.com>
On Tue, 12 Oct 2021 12:15:40 -0700
Linus Torvalds <torvalds@linux-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
next prev parent reply other threads:[~2021-10-12 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 18:11 Steven Rostedt
2021-10-12 18:34 ` Linus Torvalds
2021-10-12 18:55 ` Steven Rostedt
2021-10-12 19:15 ` Linus Torvalds
2021-10-12 19:19 ` Steven Rostedt [this message]
2021-10-13 21:37 ` Steven Rostedt
2021-10-22 12:38 ` Steven Rostedt
2021-10-22 19:34 ` Linus Torvalds
2021-10-22 21:19 ` Steven Rostedt
2021-11-18 16:47 ` Steven Rostedt
2021-11-18 18:33 ` Linus Torvalds
2021-11-18 18:52 ` Steven Rostedt
2021-11-22 6:31 ` Anshuman Khandual
2021-10-13 4:10 ` Anshuman Khandual
2021-10-13 14:27 ` Steven Rostedt
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=20211012151934.0f4aa9f4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gshan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®