mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kiko Piris <kernel@pirispons.net>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, srivatsa.bhat@linux.vnet.ibm.com
Subject: 3.10.1 cpufreq suspend/resume regression still present in 3.10.2
Date: Mon, 22 Jul 2013 17:16:53 +0200	[thread overview]
Message-ID: <20130722151653.GA7213@sacarino.pirispons.net> (raw)

Hi,

linux-3.10.1 introduced a regression in cpufreq breaking suspend/resume
cycle for some people [1].

There were also some other threads about it in lkml.

I see 3.10.2-stable was released some days ago. I couldn’t see anything
about fixing this regression reported in the changelog.

And to be 110% certain, I compiled it and tried suspending/resuming;
it’s still broken.

Is this going to be fixed in 3.10 stable branch?

Thank you very much in advance.


[1] first commit that bisect informed as introducing the regression:

| commit c02527487f0c8feb578c0394ad481a97f26d3bd2
| Author: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
| Date:   Mon Jul 1 00:40:55 2013 +0200
|
|     cpufreq: Fix cpufreq regression after suspend/resume
|
|     commit f51e1eb63d9c28cec188337ee656a13be6980cfd upstream.

https://groups.google.com/forum/#!topic/linux.kernel/LUi1pFCxbSI

-- 
Kiko

             reply	other threads:[~2013-07-22 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 15:16 Kiko Piris [this message]
2013-07-22 15:22 ` Srivatsa S. Bhat
2013-07-22 16:53   ` Greg KH
2013-07-22 16:57     ` Srivatsa S. Bhat
2013-07-22 15:34 ` Paul Bolle
2013-07-22 15:54   ` Kiko Piris
2013-07-22 15:59     ` Srivatsa S. Bhat
2013-07-22 16:12       ` Paul Bolle
2013-07-22 16:38         ` Srivatsa S. Bhat
2013-07-22 17:05         ` Kiko Piris
2013-07-22 20:52       ` Kiko Piris
2013-07-23  8:16         ` Srivatsa S. Bhat

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=20130722151653.GA7213@sacarino.pirispons.net \
    --to=kernel@pirispons.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.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
all inboxes | Powered by JetHome®