** Description changed:

- With one of the updates I got 19/2/09 I started to get this error
- shortly (1.44 secs) after grub starts the boot
+ After Jaunty updates on Feb 19, 2009, this message appears at boot:
  
  cpufreq: No nForce2 chipset
  
- Rest of dmesg appears to be normal - but is available if necessary
- 
- after booting, it is ok with the previous kernel
- 
- With some help from others and using cpufreq-info I go this - attached
- terminal output. Processor should be working at 2.53GHz - appears to be
- 317MHz
- 
- analyzing CPU 0:
-   driver: p4-clockmod
-   CPUs which need to switch frequency at the same time: 0
-   hardware limits: 317 MHz - 2.53 GHz
-   available frequency steps: 317 MHz, 633 MHz, 950 MHz, 1.27 GHz, 1.58 GHz, 
1.90 GHz, 2.22 GHz, 2.53 GHz
-   available cpufreq governors: conservative, userspace, powersave, ondemand, 
performance
-   current policy: frequency should be within 317 MHz and 2.53 GHz.
-                   The governor "ondemand" may decide which speed to use
-                   within this range.
-   current CPU frequency is 317 MHz.
-   cpufreq stats: 317 MHz:0.00%, 633 MHz:0.00%, 950 MHz:0.00%, 1.27 GHz:0.00%, 
1.58 GHz:0.00%, 1.90 GHz:0.00%, 2.22 GHz:0.00%, 2.53 GHz:0.00%  (115)
+ This is due to the message being printed with KERN_ERR instead of
+ KERN_INFO, but is harmless.
  
  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  MachineType:
   
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-7-generic 2.6.28-7.20
  ProcCmdLine: root=UUID=f5e30d80-d2e5-4d9e-b359-887f2644403f ro quiet splash
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-7.20-generic
  SourcePackage: linux

-- 
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to