Mailinglist Archive: opensuse-amd64 (78 mails)
| < Previous | Next > |
Re: [suse-amd64] Suse 10.1 powernow-k8
- From: Michael Steinhauser <mistr.rot@xxxxxx>
- Date: Tue, 23 May 2006 14:01:10 +0200
- Message-id: <4472F986.10503@xxxxxx>
Langsdorf, Mark schrieb:
>> With dmesg i get the following error from kernel:
>>
>> powernow-k8: Found 1 AMD Athlon 64 / Opteron processors
>> (version 1.60.2) ACPI Warning (acpi_utils-0065): Invalid
>> package argument [20060127] ACPI Exception
>> (acpi_processor-0274): AE_BAD_PARAMETER, Invalid _PSS data [20060127]
>> powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
>> powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa (1300 mV)
>> powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x6 (1400 mV)
>> powernow-k8: 3 : fid 0xe (2200 MHz), vid 0x2 (1500 mV)
>> cpu_init done, current fid 0xe, vid 0x0
>> powernow-k8: ph2 null fid transition 0xe
>>
>>
>> powernow-k8: internal error - pending bit very stuck - no
>> further pstate changes possible
>> powernow-k8: transition frequency failed
>>
>> powernow-k8: error - out of sync, fix 0xe 0xc, vid 0x2 0x2
>>
>> Have i to pass an option for powernow-k8 in the bootsequenz?
>>
>
> No, powernow-k8 should work if your machine doesn't
> have problems.
>
> Your machine has problems. Big problems. What are
> you running on?
>
> It looks like your machine is coming up in an illegal
> state (fid 0xe with vid 0x2). The driver tries to
> change the frequency, but the transition never
> completes. The driver ends up on a locked state after
> retrying the transition 100 times.
>
> It also looks like there is something wrong with the
> _PSS table that PN! uses to get the frequency and
> voltage data.
>
> If you don't have the latest BIOS, you may want to
> upgrade and see if that fixes anything.
>
> -Mark Langsdorf
> powernow-k8 maintainer
> AMD, Inc.
>
>
>
Hi,
I can remember i had a similar problem with Suse 10.0. There the
kernel-message was like: found amd64 Prozessor 2200 mhz stepping 0. This
problem was on several mainboards with no frequenzy-report
After an update from Suse the problem was solved.
This was the update:
9 Feb 2006 kernel-default: The standard kernel
wherein in it reads:
Also various non-security bugs were fixed: - Fix up patch for cpufreq
drivers that do not initialise current freq.
Find it here:
http://www.novell.com/linux/download/updates/100_x86_64.html
>> With dmesg i get the following error from kernel:
>>
>> powernow-k8: Found 1 AMD Athlon 64 / Opteron processors
>> (version 1.60.2) ACPI Warning (acpi_utils-0065): Invalid
>> package argument [20060127] ACPI Exception
>> (acpi_processor-0274): AE_BAD_PARAMETER, Invalid _PSS data [20060127]
>> powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
>> powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa (1300 mV)
>> powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x6 (1400 mV)
>> powernow-k8: 3 : fid 0xe (2200 MHz), vid 0x2 (1500 mV)
>> cpu_init done, current fid 0xe, vid 0x0
>> powernow-k8: ph2 null fid transition 0xe
>>
>>
>> powernow-k8: internal error - pending bit very stuck - no
>> further pstate changes possible
>> powernow-k8: transition frequency failed
>>
>> powernow-k8: error - out of sync, fix 0xe 0xc, vid 0x2 0x2
>>
>> Have i to pass an option for powernow-k8 in the bootsequenz?
>>
>
> No, powernow-k8 should work if your machine doesn't
> have problems.
>
> Your machine has problems. Big problems. What are
> you running on?
>
> It looks like your machine is coming up in an illegal
> state (fid 0xe with vid 0x2). The driver tries to
> change the frequency, but the transition never
> completes. The driver ends up on a locked state after
> retrying the transition 100 times.
>
> It also looks like there is something wrong with the
> _PSS table that PN! uses to get the frequency and
> voltage data.
>
> If you don't have the latest BIOS, you may want to
> upgrade and see if that fixes anything.
>
> -Mark Langsdorf
> powernow-k8 maintainer
> AMD, Inc.
>
>
>
Hi,
I can remember i had a similar problem with Suse 10.0. There the
kernel-message was like: found amd64 Prozessor 2200 mhz stepping 0. This
problem was on several mainboards with no frequenzy-report
After an update from Suse the problem was solved.
This was the update:
9 Feb 2006 kernel-default: The standard kernel
wherein in it reads:
Also various non-security bugs were fixed: - Fix up patch for cpufreq
drivers that do not initialise current freq.
Find it here:
http://www.novell.com/linux/download/updates/100_x86_64.html
| < Previous | Next > |