From: Guenter Roeck <linux@roeck-us.net>
To: "Mehrtens, Hauke" <hauke.mehrtens@intel.com>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: print active stack on watchdog pre timeout for separate irq stack
Date: Thu, 14 Feb 2019 14:10:34 -0800 [thread overview]
Message-ID: <20190214221034.GA11494@roeck-us.net> (raw)
In-Reply-To: <9231D502B07C5E4A8B32D5115C9F19991F89C484@IRSMSX108.ger.corp.intel.com>
On Thu, Feb 14, 2019 at 09:27:17AM +0000, Mehrtens, Hauke wrote:
> Hi,
>
> We would like to print the stack of the currently active kernel thread from the interrupt handler when the watchdog pre timeout interrupt for our watchdog is triggered, currently we have a WARN_ONCE() in the code of the interrupt handler, but this only prints the interrupt stack, which is pretty boring. On MIPS the interrupts are handled on a separate stack and not on top of the stack of the current active kernel thread to avoid stack overflows. Is there some function which would print the stack trace of the current active kernel thread in addition or instead of the interrupt stack inside of an interrupt?
>
> The kernel also has these pre timeout handlers, but they also seem to be affected by this problem:
> https://elixir.bootlin.com/linux/v5.0-rc6/source/drivers/watchdog/pretimeout_panic.c
>
Not sure I understand. Are you saying that panic() doesn't help either ?
If that is correct, I have no idea what else could be done.
Guenter
next prev parent reply other threads:[~2019-02-14 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 9:27 print active stack on watchdog pre timeout for separate irq stack Mehrtens, Hauke
2019-02-14 22:10 ` Guenter Roeck [this message]
2019-02-15 19:28 ` Paul Burton
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=20190214221034.GA11494@roeck-us.net \
--to=linux@roeck-us.net \
--cc=hauke.mehrtens@intel.com \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).