linux-kernel - 3.10.1 cpufreq suspend/resume regression still present in 3.10.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130722151653.GA7213@sacarino.pirispons.net>
Date:	Mon, 22 Jul 2013 17:16:53 +0200
From:	Kiko Piris <kernel@...ispons.net>
To:	linux-kernel@...r.kernel.org
Cc:	gregkh@...uxfoundation.org, srivatsa.bhat@...ux.vnet.ibm.com
Subject: 3.10.1 cpufreq suspend/resume regression still present in 3.10.2

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@...ux.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
--
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/