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>] [day] [month] [year] [list]
Date:	Wed, 15 Nov 2006 09:35:15 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	"Dhaval Giani" <dhaval.giani@...il.com>
Cc:	<davej@...emonkey.org.uk>, <linux-kernel@...r.kernel.org>
Subject: RE: CPUFREQ does not get enabled

 

>-----Original Message-----
>From: Dhaval Giani [mailto:dhaval.giani@...il.com] 
>Sent: Wednesday, November 15, 2006 9:28 AM
>To: Pallipadi, Venkatesh
>Cc: davej@...emonkey.org.uk; linux-kernel@...r.kernel.org
>Subject: Re: CPUFREQ does not get enabled
>
>Hey
>
>On 11/15/06, Pallipadi, Venkatesh 
><venkatesh.pallipadi@...el.com> wrote:
>>
>> Can you compile in this option
>> # CONFIG_X86_SPEEDSTEP_CENTRINO is not set
>> And try again.
>>
>
>Done and it still does not work. BTW, the help says that
>X86_SPEEDSTEP_CENTRINO is deprecated and to use X86_ACPI_CPUFREQ which
>is why I did not enable it.
>

Yes. It is different in different kernels. If you are using base 2.6.18,
then you still need both the drivers.
If you are using mm (slated to go to base kernel in future) then both
are required.

Couple of things that will help in root causing this:
1) Enable CPU_FREQ_DEBUG and boot with "cpufreq.debug=7" and capture the
dmesg.
2) Capture acpidump (You can find acpidump in latest version of pmtools
here http://www.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/ )
and send the output to me.

Better still, open a bug in bugme.osdl.org in ACPI category. That will
help us to track this failure better and close on it quicker.

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

Powered by blists - more mailing lists