From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: "Bjørn Mork" <bjorn@mork.no>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
cpufreq@vger.kernel.org
Subject: Re: Resume regression on MBA2,1 triggered by 2167e2399dc5e69c62db56d933e9c8cbe107620a
Date: Tue, 10 Dec 2013 17:25:29 -0800 [thread overview]
Message-ID: <20131211012529.GA6354@kroah.com> (raw)
In-Reply-To: <20131211010852.09ddf512@neptune.home>
On Wed, Dec 11, 2013 at 01:08:52AM +0100, Bruno Prémont wrote:
> Hi Bjørn, Rafael,
>
> I have bisected failing resume from S3 on my MBA2,1 to be caused by
> the following patch (introduced between 3.13-rc2 and 3.13-rc3 - rc2
> resuming as expected, rc3 failing to resume).
>
> Unfortunately I have no trace for the failing resume though CPU seems
> to not be busy as fan does not start blowing (even when waiting more
> than 10 minutes for the resume to eventually proceed which it does not).
>
> Kernel config and dmesg are attached (gzip compressed).
>
> commit 2167e2399dc5e69c62db56d933e9c8cbe107620a
> Author: Bjørn Mork <bjorn@mork.no>
> Date: Tue Dec 3 12:14:32 2013 +0100
> Subject: cpufreq: fix garbage kobjects on errors during suspend/resume
This has already been reverted in Linus's tree, see commit
d4faadd5d5b368a7051fef374ee933ec3606713b for the details.
Does Linus's tree still have the same problem for you?
thanks,
greg k-h
next parent reply other threads:[~2013-12-11 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131211010852.09ddf512@neptune.home>
2013-12-11 1:25 ` Greg Kroah-Hartman [this message]
2013-12-12 12:38 ` Resume regression on MBA2,1 triggered by 2167e2399dc5e69c62db56d933e9c8cbe107620a Bruno Prémont
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=20131211012529.GA6354@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bjorn@mork.no \
--cc=bonbons@linux-vserver.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@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