From: Wilmer van der Gaast <wilmer@gaast.net>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Machine crashes right *after* ~successful resume
Date: Thu, 16 Oct 2014 00:34:55 +0100 [thread overview]
Message-ID: <543F049F.5090605@gaast.net> (raw)
In-Reply-To: <CAE9FiQV9t0bCfUy5Fichdk=04ruEVxGv-LUK1xxZjCrasAOACg@mail.gmail.com>
Hello Yinghai,
On 15-10-14 19:39, Yinghai Lu wrote:
>
> so third resume will not work? that is strange.
> second and third should not use same code path...
>
Always exactly the third time, yes. Seems strange indeed. :-( I was
under the impression that on each resume, completion time of device
resumes was growing, and wondered whether that could be related. However
looking back at my logs, this is not consistent, in some cases the time
is constant.
Anyway, your patch works! Had to tweak it slightly to apply cleanly to
the 3.17 tarball I have, but my machine now went through eleven
successful suspend+resume cycles again.
Is there anything I can do now to find out why your change is causing my
machine to crash?
Thank you!
Wilmer v/d Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
next prev parent reply other threads:[~2014-10-15 23:35 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 23:20 Machine crashes right *after* ~successful resume Wilmer van der Gaast
2014-10-12 14:30 ` Pavel Machek
2014-10-12 15:49 ` Wilmer van der Gaast
2014-10-12 20:40 ` Pavel Machek
2014-10-12 23:47 ` Wilmer van der Gaast
2014-10-13 15:06 ` Rafael J. Wysocki
2014-10-15 11:16 ` Wilmer van der Gaast
2014-10-15 13:58 ` Bjorn Helgaas
2014-10-15 18:39 ` Yinghai Lu
2014-10-15 23:34 ` Wilmer van der Gaast [this message]
2014-10-16 4:32 ` Yinghai Lu
2014-10-16 9:36 ` Wilmer van der Gaast
2014-10-16 16:36 ` Yinghai Lu
2014-10-16 21:08 ` Wilmer van der Gaast
2014-10-18 21:28 ` Yinghai Lu
2014-10-18 23:57 ` Wilmer van der Gaast
2014-10-19 4:29 ` Yinghai Lu
2014-10-19 10:48 ` Wilmer van der Gaast
2014-10-21 21:40 ` Wilmer van der Gaast
2014-10-21 23:15 ` Yinghai Lu
2014-10-22 12:53 ` Wilmer van der Gaast
2014-10-26 21:53 ` Yinghai Lu
2014-10-27 10:50 ` Wilmer van der Gaast
2014-10-27 18:23 ` Yinghai Lu
2014-10-27 22:22 ` Wilmer van der Gaast
2014-10-27 23:41 ` Yinghai Lu
2014-10-28 0:03 ` Wilmer van der Gaast
2014-10-28 1:12 ` Yinghai Lu
2014-10-28 4:03 ` Yinghai Lu
2014-10-28 10:23 ` Wilmer van der Gaast
2014-10-28 23:34 ` Wilmer van der Gaast
2014-10-29 5:17 ` Yinghai Lu
2014-10-29 9:37 ` Wilmer van der Gaast
2014-10-30 0:53 ` Yinghai Lu
2014-10-30 10:36 ` Wilmer van der Gaast
2014-10-30 16:57 ` Yinghai Lu
2014-10-30 21:54 ` Wilmer van der Gaast
2014-10-30 23:02 ` Yinghai Lu
2014-10-30 23:24 ` Wilmer van der Gaast
2014-10-31 0:43 ` Yinghai Lu
2014-10-31 2:13 ` Yinghai Lu
2014-10-31 9:39 ` Wilmer van der Gaast
2014-10-31 16:11 ` Yinghai Lu
2014-10-31 21:13 ` Wilmer van der Gaast
2014-10-31 21:22 ` Yinghai Lu
2014-10-31 23:18 ` Yinghai Lu
2014-11-01 0:00 ` Wilmer van der Gaast
2014-11-01 2:10 ` Yinghai Lu
2014-11-02 23:16 ` Wilmer van der Gaast
2014-10-27 21:21 ` Pavel Machek
2014-10-19 8:07 ` 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=543F049F.5090605@gaast.net \
--to=wilmer@gaast.net \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=yinghai@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).