| 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
| ||
|
Message-ID: <20061026190142.GA31153@amd64.of.nowhere> Date: Thu, 26 Oct 2006 21:01:42 +0200 From: thunder7@...all.nl To: Inter filmati <interfc@...py.it> Cc: linux-kernel@...r.kernel.org Subject: Re: cpufreq/powernowd limiting CPU frequency on kernels >=2.6.16 From: Inter filmati <interfc@...py.it> Date: Thu, Oct 26, 2006 at 07:59:41PM +0200 > > > >If you care about that changed, try to find out what patch caused this, > >but in general, there's no support for overclocking in the kernel, and > >bugreports from overclocked systems are frowned upon. > > > It would be kind to find out why the problem seems to show only from 2.6.16 > and not before, unfortunately I ain't so skilled to investigate into > cpufreq source. > You could start by trying 2.6.16-rc1, -rc2, -rc3 and find out in which kernel it changed. Then, read the changelog for that patch to find out what changed in the cpufreq driver. So far, no great skill required. Then, post here, mentioning which patch caused the different behaviour. Jurriaan -- Despite the best efforts of a quantum bigfoot drive (yes I know everyone told me they suck, now I know they were right) 2.1.109ac1 is now available Alan Cox announcing Linux 2.1.109ac1 Debian (Unstable) GNU/Linux 2.6.18-mm3 2x5042 bogomips load 0.91 - 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