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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DC0EC433EF for ; Wed, 2 Mar 2022 11:12:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239908AbiCBLNg (ORCPT ); Wed, 2 Mar 2022 06:13:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229973AbiCBLNb (ORCPT ); Wed, 2 Mar 2022 06:13:31 -0500 Received: from pandora.armlinux.org.uk (pandora.armlinux.org.uk [IPv6:2001:4d48:ad52:32c8:5054:ff:fe00:142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 71FA025CC for ; Wed, 2 Mar 2022 03:12:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=xOjxxbjIvHJEQNgG9MHTzXo9CLrsd8jMw0niJ2NBupE=; b=JC3WTs6K5N5U0vX4VYEytwdASQ URkqrzIMyreoN305X2fZbNGjjihzsrNblNn/2BpTNiQUCrYCj9oEF3aSIO9fMGq/JLDxHNBfXiQje X4bpI3aLp105qQe4S4pcbaEO67Bzus93kIgQeste+JjG8yjmLQvwtZbs3WiwwqbJK0bXl15tRmRzx WubZkhcwNZR4+mXRY7LcP7ZWs+sn0OQavK183X+yMrz4GceNfnPwt6BGFNVBuS42j5i/HTq1jdXNq vf2beZ7wnaZ2OSHqOY0HHcKw+L1N9/n1HrbUorMq6WXtN6ENY7uhSWapZCzjv4BsoQfEPG/jNWcaI KzXvdE8Q==; Received: from shell.armlinux.org.uk ([fd8f:7570:feb6:1:5054:ff:fe00:4ec]:57590) by pandora.armlinux.org.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nPMuL-0002JR-9v; Wed, 02 Mar 2022 11:12:37 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.94.2) (envelope-from ) id 1nPMuJ-00085T-Gt; Wed, 02 Mar 2022 11:12:35 +0000 Date: Wed, 2 Mar 2022 11:12:35 +0000 From: "Russell King (Oracle)" To: Corentin Labbe Cc: Ard Biesheuvel , Linus Walleij , Arnd Bergmann , Linux ARM , Linux Kernel Mailing List Subject: Re: boot flooded with unwind: Index not found Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Russell King (Oracle) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 02, 2022 at 11:09:49AM +0100, Corentin Labbe wrote: > The crash disappeared (but the suspicious RCU usage is still here). As the trace on those is: [ 0.239629] unwind_backtrace from show_stack+0x10/0x14 [ 0.239654] show_stack from init_stack+0x1c54/0x2000 unwind_backtrace() and show_stack() are both C code, the compiler will emit the unwind information for it. show_stack() isn't called from assembly code, only from C code, so the next function's unwind information should also be generated by the compiler. However, init_stack is not a function - it's an array of unsigned long. There is no way this should appear in the trace, and this suggests that the unwind of show_stack() has gone wrong. I don't see anything obvious in Ard's changes that would cause that though. Did it used to work fine with previous versions of linux-next - those versions where we had Ard's "arm-vmap-stacks-v6" tag merged in (commit 2fa394824493) and did this only appear when I merged "arm-ftrace-for-rmk" (commit 74aaaa1e9bba) ? Did merging "arm-ftrace-for-rmk" cause any change in your .config? -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!