linux-kernel - Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver

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]

Message-Id: <200705162039.02379.prakash@punnoor.de>
Date:	Wed, 16 May 2007 20:38:58 +0200
From:	Prakash Punnoor <prakash@...noor.de>
To:	Joshua Hoblitt <jhoblitt@....hawaii.edu>
Cc:	LKML <linux-kernel@...r.kernel.org>, trivial@...nel.org
Subject: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver

Am Mittwoch 16 Mai 2007 schrieb Joshua Hoblitt:
> Hello,
>
> Below is a one line patch to possibly fix this bug:
>
> http://bugs.gentoo.org/show_bug.cgi?id=178585
> http://bugzilla.kernel.org/show_bug.cgi?id=8075
>
> If the kernel is configured with:
>
> CONFIG_X86_POWERNOW_K8=y
> CONFIG_X86_ACPI_CPUFREQ=m
>
> Which is currently an allowed configuration, the powernow-k8 driver on
> an SMP system will fail with a warning like:

NAK. I have an Athlon X2 and it works for me w/o the P states driver compiled 
in.

YOu probably should ask the vendor to fix the bios or simply compile in the p 
states driver additionally w/o forcing the user to do it.

Maybe you want to give a hint in the p states driver help text?
-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

Download attachment "signature.asc " of type "application/pgp-signature" (190 bytes)