linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: Linux PM List <linux-pm@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Pavel Machek <pavel@ucw.cz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Len Brown <lenb@kernel.org>, Takashi Iwai <tiwai@suse.de>,
	Benoit Goby <benoit@android.com>, Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2][RFC] PM / sleep: Expose DPM watchdog timeout to sysfs
Date: Thu, 11 Aug 2016 20:29:17 +0800	[thread overview]
Message-ID: <cover.1470908324.git.yu.c.chen@intel.com> (raw)

Recently we have a new report that, the harddisk can not
resume on time due to firmware issues, and got a kernel
panic because of DPM watchdog timeout. Since the default
timeout has once been modified from 12 to 60 seconds, we
might still encounter new case which requires a longer timeout,
so expose the value to sysfs and let the users decide which
value is appropriate, meanwhile this can also ease the debugging
process.

The first patch is to force DPM watchdog depending on CONFIG_PM_SLEEP,
thus the second patch which does the actual work, can use
CONFIG_DPM_WATCHDOG safely without checking CONFIG_PM_SLEEP.

Chen Yu (2):
  PM / sleep: Make DPM watchdog depend on PM_SLEEP
  PM / Sleep: Expose DPM watchdog timeout to sysfs

 drivers/base/power/main.c    |  4 +++-
 include/linux/sched/sysctl.h |  4 ++++
 kernel/power/Kconfig         |  2 +-
 kernel/sysctl.c              | 16 ++++++++++++++++
 4 files changed, 24 insertions(+), 2 deletions(-)

-- 
2.7.4


             reply	other threads:[~2016-08-11 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 12:29 Chen Yu [this message]
2016-08-11 12:29 ` [PATCH 1/2][RFC] PM / sleep: Make DPM watchdog depend on PM_SLEEP Chen Yu
2016-08-12  0:40   ` Rafael J. Wysocki
2016-08-11 12:29 ` [PATCH 2/2][RFC] PM / sleep: Expose DPM watchdog timeout to sysfs Chen Yu
2016-08-11 18:54 ` [PATCH 0/2][RFC] " Pavel Machek
2016-08-12  0:39   ` Rafael J. Wysocki
2016-08-12  2:52   ` Chen Yu
2016-08-12  6:33     ` Pavel Machek
2016-08-12 10:49       ` Chen, Yu C
2016-08-12 11:25       ` Rafael J. Wysocki
2016-08-17  3:43         ` Chen Yu
2016-08-18 12:06           ` Pavel Machek
2016-08-18 17:44             ` Chen, Yu C
2016-08-18 18:42               ` Pavel Machek
2016-08-18 22:22                 ` Rafael J. Wysocki
2016-08-18 22:32                   ` Pavel Machek

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=cover.1470908324.git.yu.c.chen@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=benoit@android.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=tiwai@suse.de \
    /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).