powernow-k8 still not working, patch availlable?

Michael Steinhauser

13 Sep 2006 13 Sep '06

09:46

I´m running an AMD64 with kernel 2.6.16.21-0.13 default. With dmesg I get the following warning: Aug 27 08:10:18 egal kernel: ACPI Warning (acpi_utils-0065): Invalid package argument [20060127] Aug 27 08:10:18 egal kernel: ACPI Exception (acpi_processor-0274): AE_BAD_PARAMETER, Invalid _PSS data [20060127] Aug 27 08:10:18 egal kernel: cpu_init done, current fid 0xe, vid 0x0 Aug 27 08:10:18 egal kernel: powernow-k8: ph2 null fid transition 0xe Aug 27 08:10:20 egal kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } Aug 27 08:10:20 egal kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } Aug 27 08:10:20 egal kernel: ide: failed opcode was: 0xef Aug 27 08:10:24 egal kernel: powernow-k8: internal error - pending bit very stuck - no further pstate changes possible Aug 27 08:10:24 egal kernel: powernow-k8: transition frequency failed. I postet this before an was told this is because of the Invalid_Pss data. Now I found this bug on bugzilla.kernel.org number 6782 for kernel 2.6.17-mm5 as resolved.PATCH_ALREADY_AVAILABLE http://bugzilla.kernel.org/show_bug.cgi?id=6782. Is this patch available for Suse 10.1 or will it be fixed in a new Kernel-Version? Thank you Michael

Show replies by date

Dittmann, Werner

13 Sep 13 Sep

10:28

New subject: AW: [suse-amd64] powernow-k8 still not working, patch availlable?

Some time ago I had a similar problem (GigaByte Nvidia borad). Was solved with an update of the BIOS. After that the kernal could acces/use the powernow data. Regards, Werner

...

-----Ursprüngliche Nachricht----- Von: mistr.rot@web.de [mailto:mistr.rot@web.de] Gesendet: Mittwoch, 13. September 2006 11:47 An: suse-amd64@suse.com Betreff: [suse-amd64] powernow-k8 still not working, patch availlable?

I´m running an AMD64 with kernel 2.6.16.21-0.13 default. With dmesg I get the following warning: Aug 27 08:10:18 egal kernel: ACPI Warning (acpi_utils-0065): Invalid package argument [20060127] Aug 27 08:10:18 egal kernel: ACPI Exception (acpi_processor-0274): AE_BAD_PARAMETER, Invalid _PSS data [20060127] Aug 27 08:10:18 egal kernel: cpu_init done, current fid 0xe, vid 0x0 Aug 27 08:10:18 egal kernel: powernow-k8: ph2 null fid transition 0xe Aug 27 08:10:20 egal kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } Aug 27 08:10:20 egal kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } Aug 27 08:10:20 egal kernel: ide: failed opcode was: 0xef Aug 27 08:10:24 egal kernel: powernow-k8: internal error - pending bit very stuck - no further pstate changes possible Aug 27 08:10:24 egal kernel: powernow-k8: transition frequency failed.

I postet this before an was told this is because of the Invalid_Pss data.

Now I found this bug on bugzilla.kernel.org number 6782 for kernel 2.6.17-mm5 as resolved.PATCH_ALREADY_AVAILABLE http://bugzilla.kernel.org/show_bug.cgi?id=6782.

Is this patch available for Suse 10.1 or will it be fixed in a new Kernel-Version?

Thank you Michael

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

Langsdorf, Mark

15:36

New subject: [suse-amd64] powernow-k8 still not working, patch availlable?

...

Aug 27 08:10:24 egal kernel: powernow-k8: internal error - pending bit very stuck - no further pstate changes possible Aug 27 08:10:24 egal kernel: powernow-k8: transition frequency failed.

I postet this before an was told this is because of the Invalid_Pss data.

Unlikely. For some reason, the transitions are failing on the hardware side. It could be a _PSS issue, but I doubt it. What fid/vid table are you getting when the driver starts up? -Mark Langsdorf AMD, Inc.

Michael Steinhauser

16:42

New subject: [suse-amd64] powernow-k8 still not working, patch availlable?

Langsdorf, Mark schrieb:

...

...
Aug 27 08:10:24 egal kernel: powernow-k8: internal error - pending bit very stuck - no further pstate changes possible Aug 27 08:10:24 egal kernel: powernow-k8: transition frequency failed.

I postet this before an was told this is because of the Invalid_Pss data.

Unlikely. For some reason, the transitions are failing on the hardware side. It could be a _PSS issue, but I doubt it.

What fid/vid table are you getting when the driver starts up?

-Mark Langsdorf AMD, Inc.

Hi, here I put some lines of /var/log/messages, showing the startup of powernow-k8: Sep 13 18:08:44 egal kernel: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.2) Sep 13 18:08:44 egal kernel: ACPI Warning (acpi_utils-0065): Invalid package argument [20060127] Sep 13 18:08:44 egal kernel: ACPI Exception (acpi_processor-0274): AE_BAD_PARAMETER, Invalid _PSS data [20060127] Sep 13 18:08:44 egal kernel: powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV) Sep 13 18:08:44 egal kernel: powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa (1300 mV) Sep 13 18:08:44 egal kernel: powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x6 (1400 mV) Sep 13 18:08:44 egal kernel: powernow-k8: 3 : fid 0xe (2200 MHz), vid 0x2 (1500 mV) Sep 13 18:08:44 egal kernel: cpu_init done, current fid 0xe, vid 0x0 Sep 13 18:08:44 egal kernel: powernow-k8: ph2 null fid transition 0xe Sep 13 18:08:44 egal rcpowersaved: s2ram does not know your machine. See 's2ram -i' for details. (127) Sep 13 18:08:44 egal rcpowersaved: Use SUSPEND2RAM_FORCE=yes to override this detection. In boot.msg I get this line after loading scsi-subsystem: <7>Losing some ticks... checking if CPU frequency changed. Hope it helps Michael

Michael Steinhauser

17:21

New subject: [suse-amd64] powernow-k8 still not working, patch availlable?

Hi, after sending the last mail I got a returned mail from the mail delivery subsystem. In the mail it reads something like this: The original message was received at Wed, 13 Sep 2006 18:54:39 +0200 (MEST) from [87.245.121.234] ----- The following addresses had permanent fatal errors ----- (reason: 550 <81.169.145.181> is blacklisted (RBL)) ----- Transcript of session follows ----- ... while talking to mail.messaging.ch.:

...

...
...
...
...
...
MAIL From: SIZE=4136 BODY=7BIT

<<< 550 <81.169.145.181> is blacklisted (RBL) 554 5.0.0 Service unavailable

Has this to say anything for me?

Dieter Kluenter

14 Sep 14 Sep

07:21

New subject: [suse-amd64] powernow-k8 still not working, patch availlable?

Michael Steinhauser writes:

...

Hi, after sending the last mail I got a returned mail from the mail delivery subsystem. In the mail it reads something like this:

The original message was received at Wed, 13 Sep 2006 18:54:39 +0200 (MEST) from [87.245.121.234]

----- The following addresses had permanent fatal errors ----- (reason: 550 <81.169.145.181> is blacklisted (RBL))

----- Transcript of session follows ----- ... while talking to mail.messaging.ch.:

...
...
...
...
...
> MAIL From: SIZE=4136 BODY=7BIT

<<< 550 <81.169.145.181> is blacklisted (RBL) 554 5.0.0 Service unavailable

Has this to say anything for me?

*Yes* the address is blacklisted, i just tested it. http://openrbl.org/client/ -Dieter -- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6

Michael Steinhauser

15 Sep 15 Sep

05:36

New subject: [suse-amd64] powernow-k8 still not working, patch availlable?

Michael Steinhauser schrieb:

...

Langsdorf, Mark schrieb:

...
...
Aug 27 08:10:24 egal kernel: powernow-k8: internal error - pending bit very stuck - no further pstate changes possible Aug 27 08:10:24 egal kernel: powernow-k8: transition frequency failed.

I postet this before an was told this is because of the Invalid_Pss data.

Unlikely. For some reason, the transitions are failing on the hardware side. It could be a _PSS issue, but I doubt it.

What fid/vid table are you getting when the driver starts up?

-Mark Langsdorf AMD, Inc.

Hi, here I put some lines of /var/log/messages, showing the startup of powernow-k8:

Sep 13 18:08:44 egal kernel: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.2) Sep 13 18:08:44 egal kernel: ACPI Warning (acpi_utils-0065): Invalid package argument [20060127] Sep 13 18:08:44 egal kernel: ACPI Exception (acpi_processor-0274): AE_BAD_PARAMETER, Invalid _PSS data [20060127] Sep 13 18:08:44 egal kernel: powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV) Sep 13 18:08:44 egal kernel: powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa (1300 mV) Sep 13 18:08:44 egal kernel: powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x6 (1400 mV) Sep 13 18:08:44 egal kernel: powernow-k8: 3 : fid 0xe (2200 MHz), vid 0x2 (1500 mV) Sep 13 18:08:44 egal kernel: cpu_init done, current fid 0xe, vid 0x0 Sep 13 18:08:44 egal kernel: powernow-k8: ph2 null fid transition 0xe Sep 13 18:08:44 egal rcpowersaved: s2ram does not know your machine. See 's2ram -i' for details. (127) Sep 13 18:08:44 egal rcpowersaved: Use SUSPEND2RAM_FORCE=yes to override this detection.

In boot.msg I get this line after loading scsi-subsystem: <7>Losing some ticks... checking if CPU frequency changed.

Hope it helps

Michael

Hi, today I recognized the cpufreq-module of Enlightenment (e17) shows changes of the frequencies between 1 Ghz and 2,2 Ghz by opening applications. Is there a way to monitor or log the frequencies. And what are the rules of the changes? Actually running thunderbird, Opera and kaffeine-dvdapplication, The cpu-monitor of e17 shows now 1 Ghz with a CPU-usage between 9 and 20 percent (in Gkrellm). Running for example ekiga brings the cpu-freq up to 2.2 Ghz and then back to 1.8 Ghz and finally 1 Ghz. But this all fits not with the message powernow-k8: internal error - pending bit very stuck - no further pstate changes possible

6451

Age (days ago)

6453

Last active (days ago)

List overview

Download

6 comments

4 participants

participants (4)

Dieter Kluenter
Dittmann, Werner
Langsdorf, Mark
Michael Steinhauser