Power states AMD64x2 broken

[Ken Phillis Jr]

Binary package hint: linux-source-2.6.20

I have issues with loading the Power states for the athlon 64 x2 dual core cpu of mine, here's the information i have relevant to this:

kphillisjr@kphillisjrX64-desktop:/usr/bin$sudo modprobe powernow-k8
FATAL: Error inserting powernow_k8 (/lib/modules/2.6.20-16-lowlatency/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k8.ko): No such device
kphillisjr@kphillisjrX64-desktop:/usr/bin$ cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
kphillisjr@kphillisjrX64-desktop:/usr/bin$ dmesg | tail
[155893.180000] powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ processors (version 2.00.00)
[155893.180000] powernow-k8: MP systems not supported by PSB BIOS structure
[155893.180000] powernow-k8: MP systems not supported by PSB BIOS structure
[156196.211000] cpufreq_conservative: Unknown parameter `cpufreq_ondemand'
[158457.798000] powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ processors (version 2.00.00)
[158457.798000] powernow-k8: MP systems not supported by PSB BIOS structure
[158457.799000] powernow-k8: MP systems not supported by PSB BIOS structure
[158469.658000] powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ processors (version 2.00.00)
[158469.658000] powernow-k8: MP systems not supported by PSB BIOS structure
[158469.659000] powernow-k8: MP systems not supported by PSB BIOS structure

i already found a fix for this, but it involves creating a custom DSDT for the cpu, at which you need to refer to this page to create support:
http://wejp.k.vu/projects/howto_cnq_athlon_64_x2/

[Ken Phillis Jr (kphillisjr)]

i decided to attach a prepared file for this, although i don't know how to load it to test it.

[K Mori (kmori-nospam)]

Go to http://gaugusch.at/kernel.shtml
and download the initrd-add-dsdt script. Do something like:

cd /boot
/usr/bin/iasl -tc <your dsdt dml file>
cp initrd.img-2.6.20-16-generic initrd.img-2.6.20-16-generic-dsdt
initrd-add-dsdt initrd.img-2.6.20-16-generic-dsdt dsdt.aml

Then change your grub menu to point to the new initrd.img file: initrd.img-2.6.20-16-generic-dsdt

I tried this, however I still get the errors. You can confirm you dsdt changes by looking at what's in: /proc/acpi/dsdt after rebooting with the new initrd

[Ken Phillis Jr (kphillisjr)]

I fixed the error... it had something to do with the nvidia raid device... and so i had to change the line that has, "_NVRAIDBUS" to "NVRAIDBUS" and all that's left is a single warning and that's it.

oh and on a small note i don't know which file on that site to download to get the initrd-add-dsdt script.

[K Mori (kmori-nospam)]

The script is here:
http://gaugusch.at/acpi-dsdt-initrd-patches/initrd-add-dsdt

So are you saying that just cleaning up the ACPI error/warnings that you were getting fixed your powernow-k8 problem? I'm also seeing some acpi errors due to incorrect namespace lookups.
Where were you seeing these nvidia raid device errors?

[Ken Phillis Jr (kphillisjr)]

Thanks for the link, but here's what i was talking about:

kphillisjr@kphillisjr-desktop:/home/kphillisjr/Mydata# iasl -tc wejp-dsdt.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20060912 [Dec 6 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a

wejp-dsdt.dsl 584: Method (\_WAK, 1, NotSerialized)
Warning 1079 - ^ Reserved method must return a value (_WAK)

wejp-dsdt.dsl 3491: Name (_HID, "_NVRAIDBUS")
Error 4001 - String must be entirely alphanumeric ^ (_NVRAIDBUS)

ASL Input: wejp-dsdt.dsl - 7167 lines, 234464 bytes, 2644 keywords
Compilation complete. 1 Errors, 1 Warnings, 0 Remarks, 775 Optimizations

Notice that it has an error on line 3491... i had to change that line such that it used NVRAIDBUS instead of _NVRAIDBUS
the warning i have no clue how to fix... oh and also this is done with the compiling of the file i attached earlier in this bug.

[K Mori (kmori-nospam)]

Ok, understood.
I got powernow-k8 working now but it took a hack. Basically, I downloaded the Feisty kernel source (2.6.20-16) and edited the powernow-k8.c file and commented out the lines:
   //if (num_online_cpus() != 1) {
  // printk(KERN_ERR PFX "MP systems not supported by PSB BIOS structure\n");
  // kfree(data);
  // return -ENODEV;
  //}
This allows the driver to get past this non-compliance and finish loading properly. This actually works even with empty "Processor" tables in the dsdt.

Here's my dmesg (first attempt at 16603 was with the original driver, second attempt at 17203 was with the modified driver):

[16603.332000] powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ processors (version 2.00.00)
[16603.332000] powernow-k8: MP systems not supported by PSB BIOS structure
[16603.332000] powernow-k8: MP systems not supported by PSB BIOS structure
[17203.268000] powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ processors (version 2.00.00)
[17203.272000] powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12
[17203.272000] powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x10
[17203.272000] powernow-k8: 2 : fid 0xc (2000 MHz), vid 0xe
[17203.272000] powernow-k8: 3 : fid 0xe (2200 MHz), vid 0xc
[17203.272000] powernow-k8: 4 : fid 0x10 (2400 MHz), vid 0xa
[17203.272000] powernow-k8: 5 : fid 0x11 (2500 MHz), vid 0x9

I attached my compiled powernow-k8 but use it at your own risk.

[Ken Phillis Jr (kphillisjr)]

a bit late, but i got it working however i had to change my system settings a bit, and apply the acpistates, which work... oh and it's worth noting that this bug still exists in Gutsy's 2.6.22 kernel.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[K Mori (kmori-nospam)]

I did 2 incremental upgrades from feisty->gutsy->hardy over the past week and it seems like this issue was fixed in at least the latest kernel.

[ 29.147724] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ processors (2 cpu cores) (version 2.20.00)
[ 29.147595] powernow-k8: 0 : fid 0x11 (2500 MHz), vid 0x9
[ 29.147599] powernow-k8: 1 : fid 0x10 (2400 MHz), vid 0xa
[ 29.147601] powernow-k8: 2 : fid 0xe (2200 MHz), vid 0xc
[ 29.147602] powernow-k8: 3 : fid 0xc (2000 MHz), vid 0xe
[ 29.147604] powernow-k8: 4 : fid 0xa (1800 MHz), vid 0x10
[ 29.147606] powernow-k8: 5 : fid 0x2 (1000 MHz), vid 0x12

The indexes are reversed from what it was before but at least it works.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

Marking this Fix Released per K Mori's previous comment - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/147762/comments/9 .