Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'cpufreq'

This is an experimental report containing PRs for tag 'cpufreq' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'cpufreq':
SSubmittedTrackerResp.Description
o2014/05/02amd64/189267amd64[cpufreq] AMD Kabini (AM1/FM1Sb) Frequency Switching Causes Crash
o2013/07/16kern/180588[cpufreq] [patch] cpufreq cannot be loaded as kernel module
o2012/02/21kern/165381acpi[cpufreq] powerd(8) eats CPUs for breakfast
o2010/05/09kern/146436[cpufreq] [panic] Panic when changing profile to economy
o2010/01/25kern/143227[panic] [cpufreq] free: address has not been allocated.
o2009/11/18kern/140658[cpufreq] dev.cpu.0.cx_lowest=C3 from /etc/sysctl.conf or /boot/loader.conf does not apply at boot when cpufreq used as module outside kernel
o2009/11/07kern/140361[cpufreq] speed-stepping broken on PhenomII (acpi?)
o2009/09/24i386/139115i386[cpufreq] low cpu frequency reported [regression]
o2008/03/16kern/121768[cpufreq] cpufreq module RELENG_6 -> 7 regressions on ASUS M5A notebook [regression]
o2006/02/24kern/93790[cpufreq] cpufreq missing frequencies
10 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.