From: Greg KH <gregkh@linuxfoundation.org>
To: josephjang@google.com
Cc: rafael@kernel.org, rjw@rjwysocki.net, pavel@ucw.cz,
len.brown@intel.com, pmladek@suse.com,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
jonglin@google.com, woodylin@google.com, markcheng@google.com
Subject: Re: [PATCH] power: suspend: Add suspend timeout handler
Date: Tue, 20 Oct 2020 10:46:00 +0200 [thread overview]
Message-ID: <20201020084600.GA3838202@kroah.com> (raw)
In-Reply-To: <000000000000011a8805b215d69a@google.com>
On Tue, Oct 20, 2020 at 08:15:38AM +0000, josephjang@google.com wrote:
> > On Tue, Oct 20, 2020 at 02:22:26PM +0800, Joseph Jang wrote:
> > > Add sleep timer and timeout handler to prevent device stuck during
> > suspend/
> > > resume process. The timeout handler will dump disk sleep task at first
> > > round timeout and trigger kernel panic at second round timeout.
> > > The default timer for each round is defined in
> > > CONFIG_PM_SLEEP_TIMER_TIMEOUT.
> > >
> > > Signed-off-by: Joseph Jang <josephjang@google.com>
> > > ---
> > > MAINTAINERS | 2 +
> > > include/linux/console.h | 1 +
> > > include/linux/suspend_timer.h | 90 +++++++++++++++++++++++++++++++++++
>
> > Why is this file in include/linux/ if you only ever call it from one .c
> > file?
>
> I just refer to include/linux/suspend.h and create a new header file in the
> same folder.
> If you have a better location for the new header file, please feel free to
> let me know.
Only put .h files that are needed by different .c files in the
include/linux/ directory. Otherwise it should be local to where the .c
file is.
> > > --- /dev/null
> > > +++ b/include/linux/suspend_timer.h
> > > @@ -0,0 +1,90 @@
> > > +/* SPDX-License-Identifier: GPL-2.0 */
> > > +#ifndef _LINUX_SLEEP_TIMER_H
> > > +#define _LINUX_SLEEP_TIMER_H
> > > +
> > > +#include <linux/sched/debug.h>
> > > +
> > > +#ifdef CONFIG_PM_SLEEP_MONITOR
> > > +struct sleep_timer {
> > > + struct task_struct *tsk;
> > > + struct timer_list timer;
> > > +};
> > > +
> > > +#define DECLARE_SLEEP_TIMER(st) > > + struct sleep_timer st
> > > +
> > > +/**
> > > + * init_sleep_timer - Initialize sleep timer.
> > > + * @st: Sleep timer to initialize.
> > > + * @func: Sleep timer timeout handler.
> > > + */
> > > +static void init_sleep_timer(struct sleep_timer *st, void (*func))
> > > +{
> > > + struct timer_list *timer = &st->timer;
> > > +
> > > + timer_setup(timer, func, 0);
> > > +}
> > > +
> > > +/**
> > > + * start_sleep_timer - Enable sleep timer to monitor suspend thread.
> > > + * @st: Sleep timer to enable.
> > > + */
> > > +static void start_sleep_timer(struct sleep_timer *st)
> > > +{
> > > + struct timer_list *timer = &st->timer;
> > > +
> > > + st->tsk = current;
> > > +
> > > + /* use same timeout value for both suspend and resume */
> > > + timer->expires = jiffies + HZ * CONFIG_PM_SLEEP_TIMER_TIMEOUT;
> > > + add_timer(timer);
> > > +}
> > > +
> > > +/**
> > > + * stop_sleep_timer - Disable sleep timer.
> > > + * @st: sleep timer to disable.
> > > + */
> > > +static void stop_sleep_timer(struct sleep_timer *st)
> > > +{
> > > + struct timer_list *timer = &st->timer;
> > > +
> > > + del_timer_sync(timer);
> > > +}
> > > +
> > > +/**
> > > + * sleep_timeout_handler - sleep timer timeout handler.
> > > + * @t: The timer list that sleep timer depends on.
> > > + *
> > > + * Called when suspend thread has timeout suspending or resuming.
> > > + * Dump all uninterruptible tasks' call stack and call panic() to
> > > + * reboot system in second round timeout.
> > > + */
> > > +static void sleep_timeout_handler(struct timer_list *t)
> > > +{
> > > + struct sleep_timer *st = from_timer(st, t, timer);
> > > + static int timeout_count;
> > > +
> > > + pr_info("Sleep timeout (timer is %d seconds)\n",
> > > + (CONFIG_PM_SLEEP_TIMER_TIMEOUT));
> > > + show_stack(st->tsk, NULL, KERN_EMERG);
> > > + show_state_filter(TASK_UNINTERRUPTIBLE);
> > > +
> > > + if (timeout_count < 1) {
> > > + timeout_count++;
> > > + start_sleep_timer(st);
> > > + return;
> > > + }
> > > +
> > > + if (console_is_suspended())
> > > + resume_console();
> > > +
> > > + panic("Sleep timeout and panic\n");
> > > +}
> > > +#else
> > > +#define DECLARE_SLEEP_TIMER(st)
> > > +#define init_sleep_timer(x, y)
> > > +#define start_sleep_timer(x)
> > > +#define stop_sleep_timer(x)
> > > +#endif
> > > +
> > > +#endif /* _LINUX_SLEEP_TIMER_H */
> > > diff --git a/kernel/power/Kconfig b/kernel/power/Kconfig
> > > index a7320f07689d..9e2b274db0c1 100644
> > > --- a/kernel/power/Kconfig
> > > +++ b/kernel/power/Kconfig
> > > @@ -207,6 +207,21 @@ config PM_SLEEP_DEBUG
> > > def_bool y
> > > depends on PM_DEBUG && PM_SLEEP
> > >
> > > +config PM_SLEEP_MONITOR
> > > + bool "Linux kernel suspend/resume process monitor"
> > > + depends on PM_SLEEP
> > > + help
> > > + This option will enable sleep timer to prevent device stuck
> > > + during suspend/resume process. Sleep timeout handler will dump
> > > + disk sleep task at first round timeout and trigger kernel panic
> > > + at second round timeout. The timer for each round is defined in
> > > + CONFIG_PM_SLEEP_TIMER_TIMEOUT.
>
> > I thought we already had a watchdog for all of this, why not just always
> > add this to that code, for that config option?
>
>
> Yes, we already have DPM_WATCHDOG to monitor device power management.
Great, use that!
> But we really hit the suspend hang issue that DPM_WATCHDOG cannot cover.
What issue is that?
> We propose a wide coverage debug feature like PM_SLEEP_MONITOR which
> not only covers PM but also core PM hang issues.
>
> And DPM_WATCHDOG is for device driver power management in
> drivers/base/power/main.c
> and PM_SLEEP_MONITOR locate is for core power management in
> kernel/power/suspend.c.
> I think it is fine for users to select whether they need device PM only or
> not.
How will a user know which they should use?
Why not just fix whatever is wrong with the watchdog code instead of
creating a new one?
> > And why isn't the watchdog sufficient for you? Why are you "open
> > coding" a watchdog timer logic here at all???
>
> Yes, we refer to DPM_WATCHDOG to extend the watchdog debugging for core PM.
> Because we really hit a real case that was not covered by DPM_WATCHDOG.
Then fix that!
> I think PM_SLEEP_MONITOR is an extension debug feature from DPM_WATCHDOG.
Please just fix the watchdog, as obviously it is not working properly.
Don't create something new because of that.
thanks,
greg k-h
next prev parent reply other threads:[~2020-10-20 8:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 8:15 [PATCH] power: suspend: Add suspend timeout handler josephjang
2020-10-20 8:46 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-20 9:01 josephjang
2020-10-20 9:25 ` Greg KH
2020-10-16 13:33 josephjang
2020-10-16 13:22 josephjang
2020-10-16 13:24 ` Rafael J. Wysocki
2020-10-16 13:25 ` Joseph Jang
2020-10-16 11:35 josephjang
2020-10-16 11:26 josephjang
2020-10-16 3:51 Joseph Jang
2020-10-16 5:44 ` Greg Kroah-Hartman
[not found] ` <CAPaOXERGzo8uF9gh4aAoicEAi_TtHn1M2Yno5LAWQPcWmq_evQ@mail.gmail.com>
2020-10-16 9:03 ` Greg Kroah-Hartman
2020-10-16 9:30 ` Joseph Jang
2020-10-16 9:01 ` Petr Mladek
2020-10-16 9:54 ` Joseph Jang
2020-10-16 13:03 ` Rafael J. Wysocki
2020-10-16 13:07 ` Rafael J. Wysocki
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=20201020084600.GA3838202@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jonglin@google.com \
--cc=josephjang@google.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=markcheng@google.com \
--cc=pavel@ucw.cz \
--cc=pmladek@suse.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=woodylin@google.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.