[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <543F049F.5090605@gaast.net>
Date: Thu, 16 Oct 2014 00:34:55 +0100
From: Wilmer van der Gaast <wilmer@...st.net>
To: Yinghai Lu <yinghai@...nel.org>
CC: Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>,
Rafael Wysocki <rafael.j.wysocki@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Machine crashes right *after* ~successful resume
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 |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists