From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: boot flooded with unwind: Index not found
Date: Wed, 2 Mar 2022 11:12:35 +0000 [thread overview]
Message-ID: <Yh9RI64fThQfnJgS@shell.armlinux.org.uk> (raw)
In-Reply-To: <Yh9CbcrfDvN2Z9Y9@Red>
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!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: boot flooded with unwind: Index not found
Date: Wed, 2 Mar 2022 11:12:35 +0000 [thread overview]
Message-ID: <Yh9RI64fThQfnJgS@shell.armlinux.org.uk> (raw)
In-Reply-To: <Yh9CbcrfDvN2Z9Y9@Red>
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!
next prev parent reply other threads:[~2022-03-02 11:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 15:48 boot flooded with unwind: Index not found Corentin Labbe
2022-03-01 15:48 ` Corentin Labbe
2022-03-01 15:49 ` Russell King (Oracle)
2022-03-01 15:49 ` Russell King (Oracle)
2022-03-01 16:37 ` Ard Biesheuvel
2022-03-01 16:37 ` Ard Biesheuvel
2022-03-01 16:52 ` Ard Biesheuvel
2022-03-01 16:52 ` Ard Biesheuvel
2022-03-01 18:19 ` Corentin Labbe
2022-03-01 18:19 ` Corentin Labbe
2022-03-02 8:39 ` Corentin Labbe
2022-03-02 8:39 ` Corentin Labbe
2022-03-02 8:44 ` Ard Biesheuvel
2022-03-02 8:44 ` Ard Biesheuvel
2022-03-02 8:55 ` Corentin Labbe
2022-03-02 9:45 ` Ard Biesheuvel
2022-03-02 9:45 ` Ard Biesheuvel
2022-03-02 10:09 ` Corentin Labbe
2022-03-02 10:09 ` Corentin Labbe
2022-03-02 11:12 ` Russell King (Oracle) [this message]
2022-03-02 11:12 ` Russell King (Oracle)
2022-03-02 11:19 ` Ard Biesheuvel
2022-03-02 11:19 ` Ard Biesheuvel
2022-03-02 11:22 ` Russell King (Oracle)
2022-03-02 11:22 ` Russell King (Oracle)
2022-03-09 0:01 ` Russell King (Oracle)
2022-03-09 0:01 ` Russell King (Oracle)
2022-03-09 1:08 ` Russell King (Oracle)
2022-03-09 1:08 ` Russell King (Oracle)
2022-03-09 7:20 ` Ard Biesheuvel
2022-03-09 7:20 ` Ard Biesheuvel
2022-03-01 18:16 ` Corentin Labbe
2022-03-01 18:16 ` Corentin Labbe
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=Yh9RI64fThQfnJgS@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=clabbe.montjoie@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.