[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset

Just checked through the files that ubuntu-bug -p linux created - the dmesg text doesn't show the error - that shows when I boot with the newer kernel

I have added that as an attachment here

Ok so that was a bit of a d'oh moment - if I

sudo cpufreq-selector -g performance

Then it fairly obviously works ok :)

I get current CPU frequency is 2.53 GHz.

BUT on reboot it reverts to the ondemand performance

Also not sure if this is of importance but grep -i nforce /boot/config-`uname -r` with the 2.6.28-7-generic

gives me
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_NFORCE2_S4985=m
CONFIG_X86_CPUFREQ_NFORCE2=m

with the 2.6.28-8-generic, I get

CONFIG_I2C_NFORCE2=m
CONFIG_I2C_NFORCE2_S4985=m
CONFIG_X86_CPUFREQ_NFORCE2=y

I can confirm this bug, this has been around for around a week I guess.

Confirmed on both i386 and amd64 since the cpu governor was set to ondemand on boot. Also confirmed that setting the cpu goverenor to performance fixes system slowdown.

Please, consider reverting the kernel configuration change.

Matthew Garrett tells me on IRC that this message is being printed by the kernel as KERN_ERR rather than KERN_INFO which is why it is appearing on the screen, and should be changed to KERN_INFO.

forestpixie, the slowness you are experiencing, while related to cpufreq, is a different problem. Since Lee and Tommaso confirmed the printing of the message, we'll leave this bug for that. The slowness problem has been reported here - bug 332017

Thanks for reporting this!

A patch was accepted upstream and will be fixed in 2.6.30. Matthew tells me that this fix can be backported easily.

Oops, apparently it hasn't been pushed yet, but it has been accepted. Setting back to Triaged.

I have recreated the patch hinted at and applied it to the latest jaunty kernel. If those who have seen these could confirm that this patch is sufficient to suppress the text and report back here. The kernels are at the URL below:

    http://people.ubuntu.com/~apw/lp332170-jaunty/

I can confirm that solved the problem. Thanks!

On Wed, Feb 25, 2009 at 03:23, Andy Whitcroft <email address hidden> wrote:

> I have recreated the patch hinted at and applied it to the latest jaunty
> kernel. If those who have seen these could confirm that this patch is
> sufficient to suppress the text and report back here. The kernels are
> at the URL below:
>
> http://people.ubuntu.com/~apw/lp332170-jaunty/<http://people.ubuntu.com/%7Eapw/lp332170-jaunty/>
>
> --
> [Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
> https://bugs.launchpad.net/bugs/332170
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mario Limonciello
<email address hidden>

So can I.

Thanks

Change approved by the kernel-team and pushed to the repository. Will be in the next upload.

Thank you.

This bug was fixed in the package linux - 2.6.28-9.31

---------------
linux (2.6.28-9.31) jaunty; urgency=low

  [ Andy Whitcroft ]

  * SAUCE: cpufreq-nforce2: probe failures are not errors
    - LP: #332170
  * SAUCE: mmc: add MODALIAS linkage for MMC/SD devices
    - LP: #30335
  * remove test-suspend script
    - LP: #333856

  [ Kees Cook ]

  * handle relative paths in modules.dep
    Fixes 2.6.28-9.30 FTBS.

  [ Upstream Kernel Changes ]

  * ricoh_mmc: Handle newer models of Ricoh controllers

 -- Tim Gardner <email address hidden> Wed, 11 Mar 2009 08:19:24 -0600

Thank you - all ok here now.