From: Aaron Lu <aaron.lu@intel.com>
To: linux-pm@vger.kernel.org
Cc: Mark Scott <markcscott@talktalk.net>,
Takashi Iwai <tiwai@suse.de>, Benoit Goby <benoit@android.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: commit 70fea60d888d caused s2ram regression with WD disk
Date: Mon, 15 Jun 2015 10:55:36 +0800 [thread overview]
Message-ID: <20150615025536.GA26473@aaronlu.sh.intel.com> (raw)
Hi,
As explained by Takashi:
"
So this looks like the cause. The recent kernel has a watchdog for
async resume workers, and if it expires, it panics. This explains why
3.12 worked; the watchdog was introduced since 3.13.
The timeout length is unfortunately fixed in Kconfig, set to 12 as
default. And this seems too short. We should extend this to at least a
minute, I suppose. Also, it'd be better to be dynamically
configuratble.
"
https://bugzilla.opensuse.org/show_bug.cgi?id=934397#c5
The upstream bug page is here:
https://bugzilla.kernel.org/show_bug.cgi?id=91921
Since Benoit isn't registered there, I write the email for discussion.
Regards,
Aaron
next reply other threads:[~2015-06-15 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 2:55 Aaron Lu [this message]
2015-06-15 11:31 ` commit 70fea60d888d caused s2ram regression with WD disk Takashi Iwai
2015-06-15 23: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=20150615025536.GA26473@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=benoit@android.com \
--cc=linux-pm@vger.kernel.org \
--cc=markcscott@talktalk.net \
--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).