From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2E0CDC433EF for ; Tue, 12 Oct 2021 19:19:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 079046101D for ; Tue, 12 Oct 2021 19:19:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233977AbhJLTVl (ORCPT ); Tue, 12 Oct 2021 15:21:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:37658 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232486AbhJLTVj (ORCPT ); Tue, 12 Oct 2021 15:21:39 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7DBA360F3A; Tue, 12 Oct 2021 19:19:36 +0000 (UTC) Date: Tue, 12 Oct 2021 15:19:34 -0400 From: Steven Rostedt To: Linus Torvalds Cc: Dave Hansen , Andy Lutomirski , Peter Zijlstra , Thomas Gleixner , Borislav Petkov , LKML , Gavin Shan , Anshuman Khandual , Christophe Leroy , Gerald Schaefer , Andrew Morton , "the arch/x86 maintainers" Subject: Re: [BUG] WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:493 Message-ID: <20211012151934.0f4aa9f4@gandalf.local.home> In-Reply-To: References: <20211012141131.3c9a2eb1@gandalf.local.home> <20211012145540.343541e9@gandalf.local.home> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 12 Oct 2021 12:15:40 -0700 Linus Torvalds 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