Bug 13146 (A7GM-S_2.0_ACPI_PSS)
| Summary: | Foxconn A7GM-S 2.0: BIOS does not provide ACPI _PSS objects in a way that Linux understands | ||
|---|---|---|---|
| Product: | Power Management | Reporter: | Leo Milano (lmilano) |
| Component: | cpufreq | Assignee: | Mark Langsdorf (mark.langsdorf) |
| Status: | CLOSED INSUFFICIENT_DATA | ||
| Severity: | normal | CC: | davej, lenb, mark.langsdorf, ross.alexander, rui.zhang, tpringle, yakui.zhao |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.30-rc2 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Output from lshal
Full output from dmesg Output from acpidump acpidump of an ASUS M4A78T-E bios 1001 acpidump of an ASUS M4A78T-E bios 1201 (with ACPI 2.0 set) dmidecode output dmidecode of ASUS M4A78T-E BIOS 1201 |
||
|
Description
Leo Milano
2009-04-22 02:50:55 UTC
Created attachment 21077 [details]
Full output from dmesg
Hi, Leo
We see such issue on many boxes based on AMD platform. This is related with BIOS bug. And it had better be fixed by bios upgrading.
As there is no _PSS object, the powerk8 cpufreq driver can't be loaded. Of course the cpu scaling can't work.
Thanks.
Hi, Rui
How about reject this bug?
Thanks.
Hi Yakui Thanks for the quick response. I reported this bug here because it was suggested by the dmesg output: "Please report this to the Linux ACPI maintainers". I think we would all save our time if this message was not output this way. Also, I am using the latest BIOS available, so I am not sure what else can be done. Should I report this to the manufacturer and ask for a fix on their side? Thanks! re-opened. The bug here is that the powernow-k8 driver is asking users to send-email. This bug is fixed only when that is gone. Leo, if you can attach your acpidump, then we can verify that the ACPI code is correct that the warning in the driver simply needs to be updated. I already sent a patch to the cpufreq list which is meant for 2.6.30 inclusion. I mixed up WARN_ONCE and thought it's doing what the newly introduce printk_once is doing. Also the message is cleaned up there to: +static const char ACPI_PSS_BIOS_BUG_MSG[] = + KERN_ERR FW_BUG PFX "No compatible ACPI _PSS objects found.\n" + KERN_ERR FW_BUG PFX "Try again with latest BIOS.\n"; This is: [PATCH 4/5] CPUFREQ: powernow-k8 cleanup msg if BIOS does not export ACPI _PSS of the patch series with subject: Several ondemand and powernow-k8 cleanups and bugfixes for 2.6.30 Created attachment 21109 [details]
Output from acpidump
Output from acpidump. I ran it as "sudo acpidump -o acpidump.txt". I got the warning: "Wrong checksum for OEMB!"
For the record (mostly for people suffering the same problem). I did contact Foxconn through their online support form this Wednesday, I explained the problem carefully, I offered help, and I got NO response whatsoever in three days. I have attached the ACPIDUMP output from my M4A78T-E (bios 1001) for Len. Created attachment 21151 [details]
acpidump of an ASUS M4A78T-E bios 1001
I have upgraded the BIOS to 1201 and enable APCI 2.0 in the BIOS and the _PSS problem seems to be fixed. powernow-k8: Found 1 AMD Phenom(tm) II X4 810 Processor processors (4 cpu cores) (version 2.20.00) powernow-k8: 0 : pstate 0 (2600 MHz) powernow-k8: 1 : pstate 1 (1900 MHz) powernow-k8: 2 : pstate 2 (1400 MHz) powernow-k8: 3 : pstate 3 (800 MHz) Attached is also the latest ACPI dump. Cheers Ross Created attachment 21182 [details]
acpidump of an ASUS M4A78T-E bios 1201 (with ACPI 2.0 set)
acpidump of an ASUS M4A78T-E bios 1201 (with ACPI 2.0 set)
hi, leo, can you upgrade your BIOS and see if the problem still exists? Hi Rui, I have the latest BIOS for my motherboard: 872F1P02. I just checked in the bios upgrade site @ foxconn and they still have that version as the most recent: Version: 872F1P02 Size: 768KB Date: 12/24/2008 As I said above, I tried to contact the foxconn engineers and I got no response whatsoever! Thanks! Leo Leo and Ross, please attach the dmidecode output of your laptop. Created attachment 21221 [details]
dmidecode output
Hi Rui. This is really a desktop, not a laptop. I just attached the output of dmidecode. Thanks!
then I am not surprised that CPU p-state control is not supported on this platform. I agree with len's comments in #5. re-assign to thomas. Thomas, please close this bug when your patch is upstream. Created attachment 21223 [details]
dmidecode of ASUS M4A78T-E BIOS 1201
well, these are really two different problems. let's focus on the incorrect warning message in this bug, i.e. "[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor." Sure. The warning is misleading and needs to be fixed. However, I don't see why a desktop should not use CPU scaling. Actually, it should: http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_9485_9487%5E10272,00.html What's the point of having a quad-core running at 3Ghz while the computer is idle? Of course, if this a BIOS bug it needs to be fixed by the BIOS provider, not by the Linux kernel. Thanks! Patch reposted, I can't do more. thanks, Thomas, can you give an url of the patch please? I can't find the place where to get the archives of cpufreq mail list. anyway, re-assign this to cpufreq category. Update: the Foxconn folks DID respond to my inquiry the next day, but the answer did not come through in my email. I'll work with them and try to find a resolution. Is there a good URL I can point them to in regards to what is the standard for ACPI objects such as _PSS ? Thanks! Leo Also: if such a source of info exists, it should be output in the kernel error, so that users can report something more useful to their motherboard vendors (as opposed to just "complain" :-) ) The same error message appears when using a Gigabyte GA-MA790XT-UD4P (revision 1.0) motherboard with bios version F4G. I see this problem on all 6 AMD systems I work with. CPU frequency scaling does not work on any of these systems under Linux. The problem is quite pervasive and does not seem to effect Windows. These systems all use different Chipsets, motherboard vendors and AMD cpu variants. The common factor seems to be AMD CPUs and recent Linux kernels. I've filed some details on a recently released IBM thinkpad here: https://bugs.launchpad.net/linux/+bug/364156 If you have a system working under Windows, you need to dump the ACPI _PSS objects and post them here. Then we can try to find out why Linux is not interpreting them as valid objects and hopefully get the issue resolved. It's great that kernel bugzilla is back. can you please verify if the problem still exists in the latest upstream kernel? bug closed as there is no response from the bug reporter. |