From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Ard Biesheuvel" <ardb@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
kernel@pengutronix.de, Steven Rostedt <rostedt@goodmis.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: FUNCTION_GRAPH_TRACER + UNWINDER_FRAME_POINTER broken on arm
Date: Mon, 27 May 2024 10:39:14 +0200 [thread overview]
Message-ID: <760b454b-e1ae-4266-95bf-fa51ca901ad4@leemhuis.info> (raw)
In-Reply-To: <alp44tukzo6mvcwl4ke4ehhmojrqnv6xfcdeuliybxfjfvgd3e@gpjvwj33cc76>
On 25.05.24 09:59, Uwe Kleine-König wrote:
>
> With FUNCTION_GRAPH_TRACER=y and CONFIG_UNWINDER_FRAME_POINTER=y I
> experience the following issue:
>
> # echo function_graph > /sys/kernel/tracing/current_tracer
> [ 303.812295] Kernel panic - not syncing: �e
> [ 303.816738] ---[ end Kernel panic - not syncing: �e ]---
>
> This reproduces reliably on v6.9 (on an i.MX25 based machine).
>
> Bisection points on v5.18-rc1~150^2~7^2~6 ("ARM: ftrace: enable
> HAVE_FUNCTION_GRAPH_FP_TEST").
>
> #regzbot introduced: 953f534a7ed6b725d4f101d2949393acc9262880
Thx for involving regzbot.
> I didn't try to understand the issue yet, but just disabled
> UNWINDER_FRAME_POINTER for now, which makes the problem disappear.
> Disabling CONFIG_DYNAMIC_FTRACE is another option to work around the
> problem.
TWIMC: I had a quick off-list chat with Uwe and pointed him to an
earlier thread about problems caused by that commit that might or might
contain an solution for the problem:
https://lore.kernel.org/all/d870c149-4363-43de-b0ea-7125dec5608e@broadcom.com/
He plans to look into this and report back.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-27 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 7:59 FUNCTION_GRAPH_TRACER + UNWINDER_FRAME_POINTER broken on arm Uwe Kleine-König
2024-05-27 8:39 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-05-27 8:42 ` Thorsten Leemhuis
2024-05-27 9:18 ` Arnd Bergmann
2024-05-27 12:25 ` Uwe Kleine-König
2024-05-27 13:33 ` Arnd Bergmann
2024-05-27 22:56 ` 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=760b454b-e1ae-4266-95bf-fa51ca901ad4@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=u.kleine-koenig@pengutronix.de \
/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