[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8734p0jhdc.fsf@jogness.linutronix.de>
Date: Wed, 26 Jun 2024 09:31:03 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Song Chen <chensong_2000@....cn>, Andrew Halaney <ahalaney@...hat.com>
Cc: Derek Barbosa <debarbos@...hat.com>, pmladek@...e.com,
rostedt@...dmis.org, senozhatsky@...omium.org,
linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
williams@...hat.com, jlelli@...hat.com
Subject: Re: a question about how to debug this case in ftrace
On 2024-06-26, Song Chen <chensong_2000@....cn> wrote:
> ohh, by the way, i'm curious why softlockup/hardlockup/hungtask don't
> have ftrace dump as well as rcu stall, or is it possible to add a
> parameter in cmdline to redirect
> softlockup/hardlockup/hungtask/rcustall warning either to ftrace or
> printk.
Are you aware of the printk:console ftrace event? If you enable it, all
printk output also goes into the ftrace buffers.
John Ogness
Powered by blists - more mailing lists