Bug 144331 - powernow-k8 doeasn't load
Summary: powernow-k8 doeasn't load
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Alpha 4
Hardware: x86-64 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Thomas Renninger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-20 11:46 UTC by Marian Jancar
Modified: 2006-02-05 11:59 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
acpidmp (88.48 KB, application/octet-stream)
2006-01-20 14:27 UTC, Marian Jancar 		Details
dmesg (21.47 KB, application/octet-stream)
2006-01-20 14:28 UTC, Marian Jancar 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Jancar 2006-01-20 11:46:32 UTC 
powewnow-k8 desn't load with the new kernel, worked fine in 10.0

epsilon:~ # modprobe powernow-k8
FATAL: Error inserting powernow_k8 (/lib/modules/2.6.15-rc5-git3-2-default/kernel/arch/x86_64/kernel/cpufreq/powernow-k8.ko): No such device
epsilon:~ # dmesg | grep powernow
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.4)
powernow-k8: BIOS error - no PSB or ACPI _PSS objects
Comment 1 Thomas Renninger 2006-01-20 12:41:24 UTC 
Ohh, probably ACPI, could you post dmesg and acpidmp output, please.
Comment 2 Marian Jancar 2006-01-20 14:27:50 UTC 
Created attachment 64281 [details]
acpidmp
Comment 3 Marian Jancar 2006-01-20 14:28:33 UTC 
Created attachment 64282 [details]
dmesg
Comment 4 Pavel Machek 2006-01-20 16:18:56 UTC 
Nvidia is loaded, so this is INVALID.

If you can reproduce it without nvidia, it would be interesting to insert printks to see where it fails.
Comment 5 Marian Jancar 2006-01-20 18:52:21 UTC 
The powernow-k8 is loaded (and fails) before the nvidia, there is other stuff that taints the kernel before the powernow, I will try to reproduce without.
Comment 6 Thomas Renninger 2006-02-03 11:47:33 UTC 
Seems as if an ACPI bug slipped in since 10.0 so that the cpufreq tables are not found any more.
Could you try latest kotd, please, there are a lot ACPI changes.
If it still does not work, do you see any suspicious ACPI errors in dmesg?
If not can you build a kernel with ACPI_DEBUG enabled, please.
If the loading of powernow-k8 still does not reveal any ACPI error messages, you can play a bit with /proc/acpi/debug_level and try to reload the module.
Comment 7 Thomas Renninger 2006-02-03 12:32:32 UTC 
You probably have modified something in BIOS and disabled cpufreq?
DSDT contains no _PSS entries, this cannot work ...
Comment 8 Marian Jancar 2006-02-03 12:39:17 UTC 
I just upgraded to STABLE kernel. It does the same on my home machine, with 9.3 kernel it worked and now it does not, the GNOME cpufreq applet was showing ~1-1.8Gzh depending on the load, now it refuses even to start.
Comment 9 Thomas Renninger 2006-02-03 12:53:38 UTC 
Please check your BIOS settings, maybe you modified the PowerNow! settings by accident?
There are no changes in the powernow-k8 driver concerning initialisation by PSB tables (I thought they were never used?).
The ACPI BIOS misses the cpufreq important parts (_PSS func), so I expect you changed the BIOS settings if it already worked?

Can you be 100% sure cpufreq worked with 9.3?
If you do not have PowerNow/cpufreq settings in BIOS, maybe you should first search for a BIOS update.
Comment 10 Marian Jancar 2006-02-05 11:59:17 UTC 
You are right, it was disabled on my home machine. Sorry for the confusion.