From: Pavel Machek <pavel@ucw.cz>
To: Chen Yu <yu.c.chen@intel.com>
Cc: Linux PM List <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Len Brown <lenb@kernel.org>, Takashi Iwai <tiwai@suse.de>,
Benoit Goby <benoit@android.com>
Subject: Re: [PATCH 0/2][RFC] PM / sleep: Expose DPM watchdog timeout to sysfs
Date: Fri, 12 Aug 2016 08:33:12 +0200 [thread overview]
Message-ID: <20160812063312.GD30992@amd> (raw)
In-Reply-To: <20160812025225.GA12238@sharon>
Hi!
> > > 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.
> >
> > Kernel should just work. User should not have to configure random
> > knobs to have working suspend/hibernation.
> >
> > We do not want "CONFIG_BREAK_SUSPEND" so I believe we don't want
> > "CONFIG_DPM_WATCHDOG". If normal users select it and it breaks their
> > system, make it depend on "CONFIG_EXPERT" or hide it in some other
> > way or maybe remove it from Kconfig altogether.
> >
> > Or maybe CONFIG_DPM_WATCHDOG should contain numeric value that user
> > has to select?
> >
> Yes, if people select it then they have the risk to break their system,
> and the original thought of the patch is to behave like a diagnosis to
> make it easier for the users to figure it out, how much time it takes
> to suspend/resume a bogus peripheral, without recomping the kernel.
> -- currently the timeout value for CONFIG_DPM_WATCHDOG can be adjusted
> by menuconfig, but bug reporter might have to recompile the kernel
> to confirm, and it takes some time to get a feedback from them, so...
Please don't add sysfs knobs for this. People should not need to
adjust sysfs files to get working kernel.
You can for example make the default 120 seconds.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-08-12 6:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 12:29 [PATCH 0/2][RFC] PM / sleep: Expose DPM watchdog timeout to sysfs Chen Yu
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 [this message]
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=20160812063312.GD30992@amd \
--to=pavel@ucw.cz \
--cc=benoit@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.de \
--cc=yu.c.chen@intel.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 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).