kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

BearTM, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one at the top) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/379873

Title:
  CPU Frequency Scaling Monitor reports incorrect CPU speeds when
  overclocked

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The reported frequencies of an overclocked Core 2 Duo are incorrect.
  Benchmarking and performance testing can confirm that the CPU is
  running at the overclocked speeds, but the values reported through
  cpuinfo are the standard stock speeds.

  CPU has been overclocked from stock 3.00GHz to 3.60GHz. This can be
  confirmed through dmidecode (output attached). The issue is that
  cpuinfo (and related utilities) all report the stock CPU speeds
  instead. This is only a visual/reporting issue. The CPU is still
  throttling correctly, and the speed is correct as per the overclocking
  ratio.

  i.e. (tested and confirmed in benchmarks & Bogomips)
  Reported 2.00Ghz = (3.6/3.0 * 2.0) = 2.40GHz True Clock Speed
  Reported 3.00Ghz = (3.6/3.0 * 3.0) = 3.60GHz True Clock Speed

  There are a few reports of this in the Ubuntu forums, however no
  resolution had been found. I have updated the BIOS on my motherboard
  (ASUS P5Q) to the latest available, with no changes. All other BIOS
  options are per standard - allowing CPU throttling/etc.

  Bug #132403 makes reference to this similar issue, but this is not a
  BIOS problem, only a reporting problem.

  Compare:
  cat  /proc/cpuinfo
  cpufreq-info
  dmidecode --type processor

  Only dmidecode is reporting the correct CPU speed as set in the BIOS.

  Regards,
      Robert.
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: cpufrequtils 006-2
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_NZ.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
  Tags: lucid
  Uname: Linux 2.6.32-24-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379873/+subscriptions