[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wi26+UnKf59XjPbGssqS+quapnED1QGNW1mVDtEiuakdQ@mail.gmail.com>
Date: Sun, 3 Aug 2025 12:10:56 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>,
Juri Lelli <juri.lelli@...hat.com>, Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>, Mel Gorman <mgorman@...e.de>, Tejun Heo <tj@...nel.org>,
Valentin Schneider <vschneid@...hat.com>, Shrikanth Hegde <sshegde@...ux.ibm.com>
Subject: Re: [GIT PULL] Scheduler updates for v6.17
On Sat, 2 Aug 2025 at 12:46, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> You could try to enable function tracer and stop the trace with the patch
> below and see where it happened.
>
> # echo function > /sys/kernel/tracing/current_tracer
> # echo 1 > /sys/kernel/tracing/tracing_on
>
> After it happens you can take a look at:
>
> # cat /sys/kernel/tracing/trace
Note that when this happens, the machine is dead.
It seems to be alive enough to get this logged, but it's dead from a
functional standpoint. There's no "when it happens, do this".
Linus
Powered by blists - more mailing lists