All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Song Chen <chensong_2000@189.cn>, Andrew Halaney <ahalaney@redhat.com>
Cc: Derek Barbosa <debarbos@redhat.com>,
	pmladek@suse.com, rostedt@goodmis.org, senozhatsky@chromium.org,
	linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	williams@redhat.com, jlelli@redhat.com
Subject: Re: a question about how to debug this case in ftrace
Date: Wed, 26 Jun 2024 09:31:03 +0206	[thread overview]
Message-ID: <8734p0jhdc.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <e6b0ba9e-e8f6-4c42-9f63-e3b67d7edbf0@189.cn>

On 2024-06-26, Song Chen <chensong_2000@189.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

  reply	other threads:[~2024-06-26  7:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 15:20 Derek Barbosa
2024-06-25  1:36 ` a question about how to debug this case in ftrace Song Chen
2024-06-25 13:20   ` Andrew Halaney
2024-06-25 13:44     ` Steven Rostedt
2024-06-25 14:09       ` John Ogness
2024-06-26  2:17       ` Song Chen
2024-06-26  2:06     ` Song Chen
2024-06-26  2:12       ` Song Chen
2024-06-26  7:25         ` John Ogness [this message]
2024-06-26  8:26           ` Song Chen
2024-06-26 14:50             ` Steven Rostedt
2024-06-27  2:26               ` Song Chen

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=8734p0jhdc.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=ahalaney@redhat.com \
    --cc=chensong_2000@189.cn \
    --cc=debarbos@redhat.com \
    --cc=jlelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=williams@redhat.com \
    /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.