Bug 92551

Summary: ACPI PCC probe failed.
Product: ACPI Reporter: Cristian Aravena Romero (caravena)
Component: OtherAssignee: acpi_other
Status: CLOSED MOVED    
Severity: normal CC: aaron.lu, info, jackkcs, linux-acpi, sworddragon2
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 3.19-rc7 Tree: Mainline
Regression: No
Attachments: My dmesg
lspci -vvnn
acpidump.txt

Description Cristian Aravena Romero 2015-02-03 10:26:40 UTC
Created attachment 165651 [details]
My dmesg

dmesg:
[    1.293820] ACPI PCC probe failed.
Comment 1 Cristian Aravena Romero 2015-02-03 10:27:10 UTC
Created attachment 165661 [details]
lspci -vvnn
Comment 2 Aaron Lu 2015-02-06 05:46:58 UTC
Unfortunately, the ACPI PCC author Ashwin Chaugule <ashwin.chaugule@linaro.org> didn't register on kernel bugzilla so we can't assign this bug to him. I suggest you sent him/her an email and CC linux-acpi mailing list about this problem.

BTW, please attach your acpidump, that would be useful:
# acpidump > acpidump.txt
Comment 3 Cristian Aravena Romero 2015-02-06 13:00:08 UTC
Created attachment 166011 [details]
acpidump.txt
Comment 4 info 2015-02-13 09:56:34 UTC
I can't boot into the system on 3.19 to get the acpidump as you suggest, but would doing it on 3.18 be ok?
Comment 5 info 2015-02-13 10:00:48 UTC
Here is the dump (taken on 3.13): http://paste.debian.net/plainh/ac2bd14b/
Comment 7 info 2015-02-13 10:10:09 UTC
Sorry, I pasted here by mistake, I was meant to post in https://bugzilla.kernel.org/show_bug.cgi?id=93171
Comment 8 dino99 2015-02-13 13:15:43 UTC
i can confirm that issue with the final 3.19 kernel (ubuntu vivid i386) running a q9550 cpu on an old mobo asus pw5dh (so maybe my hardware does not have the needed specs)

from journalctl:
.....
 PCCT header not found.
 ACPI PCC probe failed.
Comment 9 Aaron Lu 2015-02-15 01:52:59 UTC
As I said, the ACPI PCC author Ashwin Chaugule <ashwin.chaugule@linaro.org> didn't register on kernel bugzilla so we can't assign this bug to him. Please write to him and cc linux-acpi mailing list about this problem. You can point him about this bug of course for the information you have provided.

I don't find a proper status for this bug so I'll just keep it as is.