[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#364097: marked as done (linux-image-2.6.16-1-686: /proc/cpuinfo reports wrong CPU frequency when using cpufreq since 2.6.16)

Your message dated Thu, 2 Aug 2007 12:40:18 +0200
with message-id <20070802104018.GS9582@stro.at>
and subject line linux-image-2.6.16-1-686: /proc/cpuinfo reports wrong CPU frequency when using cpufreq since 2.6.16
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.16-1-686
Severity: minor

With 2.6.15 and under, /proc/cpuinfo reports true cpu frequency when 
using cpufreq (at least on non-SMP x86)

But since 2.6.16, we only get the target frequency of the current 
governor (ie. I get 1600 MHz instead of 1598.89 or something 
else when my multiplier is 16, no mather if the FSB is 100 or 1000 MHz)

/proc/cpuinfo should report the true speed, so that we know if our CPU 
is overclocked or underclocked.

This is relateted to this commit :

commit 95235ca2c20ac0b31a8eb39e2d599bcc3e9c9a10
Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Date:   Fri Dec 2 10:43:20 2005 -0800

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-z71a
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)

--- End Message ---
--- Begin Message ---
Version: 2.6.18-1

i remember seeing this in older kernels,
but should have been fixed by upstream inbetween.
thus closing


--- End Message ---

Reply to: