Bug 297119

Summary:	"powernow-k8: invalid freq entries 3900000 kHz vs. 65535000 kHz" for Gigabyte GA-K8N Pro-SLI and AMD Athlon 64 X2 3800+
Product:	[openSUSE] openSUSE 10.2	Reporter:	Ulrich Windl <Ulrich.Windl>
Component:	Basesystem	Assignee:	Thomas Renninger <trenn>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	joachim.deguara
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Output of acpidump, bzip2 compressed

Description Ulrich Windl 2007-08-03 06:32:01 UTC

Every boot syslog has the following entires for an AMD Athlon 64 X2 3800+ CPU:
powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ processors (version 2.00.00)
powernow-k8: invalid freq entries 3900000 kHz vs. 65535000 kHz
powernow-k8: invalid freq entries 3900000 kHz vs. 65535000 kHz
powernow-k8: invalid freq entries 3900000 kHz vs. 65535000 kHz
powernow-k8: invalid freq entries 3900000 kHz vs. 65535000 kHz
powernow-k8:    0 : fid 0xc (2000 MHz), vid 0x8
powernow-k8:    1 : fid 0x2 (1000 MHz), vid 0x12

All packages are up-to-date (1. August 2007). Powersave is powersave-0.15.11-0.2.
cpu info is:
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 43
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
stepping        : 1
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ts fid vid ttp
bogomips        : 2010.51

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 43
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
stepping        : 1
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ts fid vid ttp
bogomips        : 2010.51

Comment 1 Thomas Renninger 2007-08-05 14:34:07 UTC

Is there a BIOS update available for that machine?
If yes, pls try it.
If not, or if still does not work, pls provide acpidump output.

Comment 2 Ulrich Windl 2007-08-06 06:31:17 UTC

According to http://www.gigabyte.com.tw/Support/Motherboard/BIOS_Model.aspx?ProductID=1883, installed BIOS (F9 dated 2006/02/10) is latest.

Comment 3 Joachim Deguara 2007-08-06 10:58:10 UTC

Ulrich, please attach the results of apcidump (as root call "acpidump > dsdt" and attach dsdt).

Comment 4 Ulrich Windl 2007-08-07 06:02:08 UTC

Created attachment 155857 [details]
Output of acpidump, bzip2 compressed

Comment 5 Joachim Deguara 2007-08-07 08:05:45 UTC

This is a BIOS bug.  What it is doing is reporting bogus P-States to the OS.
Good:
            Package (0x06)
            {
                0x03E8,
                0x00009C40,
                0x64,
                0x09,
                0xE8202C82,
                0x0482
            },
Bogus:
            Package (0x06)
            {
                0xFFFF,
                0xFFFFFFFF,
                0xFF,
                0xFF,
                0xFFFFFFFF,
                0x03FF
            },
The driver is then doing the right thing and comparing the frequency (1st member) with the computed frequency from the control field (4th member) and reporting that they don't match and thus throwing away the bogus p-state.  Reading your DSDT (and confirmed in your kernel log) you should still get two valid and working P-States, 2GHz and 1GHz.  Do these work fine?

Comment 6 Ulrich Windl 2007-08-08 06:13:29 UTC

Yes, the CPU seems to change between 1GHz and 2GHz. I had been reporting this problem because the message came up first after some online update, and I thought there's something wrong (which after all actually is, but not what I had thought).
Changing bug summary to reflect this.
Problem reported to Gigabyte as well.

Comment 7 Joachim Deguara 2007-08-08 09:41:42 UTC

Then this does not sound like a bug at all (everything is working fine) and just a note in the log that the kernel gives us some incorrect data.
Thanks for reporting it to Gigabyte.