linux-kernel - Re: 2.6.31-rc2+: Interrupts enabled after cpufreq

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 11 Jul 2009 16:33:13 +0200
From:	Marcin Slusarz <marcin.slusarz@...il.com>
To:	Dave Jones <davej@...hat.com>,
	Marcin Slusarz <marcin.slusarz@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PM List <linux-pm@...ts.linux-foundation.org>,
	cpufreq@...r.kernel.org,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: 2.6.31-rc2+: Interrupts enabled after cpufreq_suspend

Dave Jones wrote:
> On Fri, Jul 10, 2009 at 03:25:11PM -0400, Dave Jones wrote:
> 
>  >     [PATCH] Add suspend method to cpufreq core
>  >     
>  >     In order to properly fix some issues with cpufreq vs. sleep on
>  >     PowerBooks, I had to add a suspend callback to the pmac_cpufreq driver.
>  >     I must force a switch to full speed before sleep and I switch back to
>  >     previous speed on resume.
>  > 
>  > 
>  > Ben, is there something better we can do here ?
>  > 
>  > I really don't want to add an #ifdef __powerpc__ to core code if we can help it.
>  > I'd rather we didn't call into driver guts at all from the suspend path.
> 
> Marcin,
>  Unless we get a better solution proposed, try running with this, which just
> skips doing all that code entirely.

Now it produces only:
powernow-k8: error - out of sync, fix 0x2 0xc, vid 0x12 0x6
(arch/x86/kernel/cpu/cpufreq/powernow-k8.c: powernowk8_target)
but works fine.

If it's nothing to worry about, you can add:
Tested-by: Marcin Slusarz <marcin.slusarz@...il.com>

Thanks,
Marcin
--
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/