ACPI PCC probe failed.

Bug #1430625 reported by Cristian Aravena Romero
206
This bug affects 42 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
One Hundred Papercuts
Confirmed
Low
Unassigned
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

systemd message in RED

dmesg:
[ 1.068627] ACPI PCC probe failed.

In kernel 4.0-rc3 Not red

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: caravena 3118 F...m pulseaudio
 /dev/snd/controlC0: caravena 3118 F.... pulseaudio
CurrentDesktop: GNOME
Date: Wed Mar 11 01:13:11 2015
InstallationDate: Installed on 2014-09-25 (167 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-7-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Low
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does the 'ACPI PCC probe failed' also appear in kernels earlier in 3.19?

Revision history for this message
Matthew Haughton (snafu109) wrote :

Looks fixed upstream in commit efd756daf4ddae3cec2404c4e0b680b7cfdd6a45. This downgrades the message urgency from error to debug level.

I wouldn't expect this to show in kernels earlier than 3.19 because this driver was added in that kernel version, see 86c22f8c9a3b71d42d38bfcd80372de72f573713

Revision history for this message
Kerry Kobashi (kkobashi-0) wrote :

This showed up on boot today after I upgraded from Lubuntu 14.04 to 15.04.
14.04 was only on my system for 2 days and thus fresh with minimal packages installed.

This message didn't exist for me prior to this.

Details:
- Asus M5A78L-M mobo
- 3.19.0-15

Revision history for this message
i1abnrk (i1abnrk) wrote :

I also had this error on ASUS Z87-Pro motherboard when upgrading 14.10 to 15.04. Unity was unable to login using any kernel. Using a liveusb I downloaded the lastest NVIDIA driver for my EVGA GeForce 960 GTX from NVIDIA. I installed it from a root shell and I was able to log in after restart.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a Vivid test kernel with a cherry-pick of efd756da. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1430625/

Can folks affected by this bug test this kernel and see if it resolves the bug?

Thanks in advance!

Revision history for this message
i1abnrk (i1abnrk) wrote :

Sorry, every time I try to install NVIDIA drivers, via package manager or NVIDIA download on 13.10, 14.04, 14.10, 15.04 I get login trouble. I don't know how to install the kernel, advise.

Revision history for this message
i1abnrk (i1abnrk) wrote :

I got around my NVIDIA problems here after a fresh install of 14.10:
http://ubuntuforums.org/showthread.php?t=2263316 see additional steps at the end

Revision history for this message
sedat akbal (sedatakbal) wrote :

This showed up on boot today after I upgraded from Ubuntu 14.04 to 15.04 and after fresh install Ubuntu 15.05 it showed up again

This message didn't exist for me prior to this.

Details:
- Asus FJ3C
- linux-headers-3.19.0-15-generic

Revision history for this message
Paolo Zonari (paolo-zonari) wrote :

"I built a Vivid test kernel with a cherry-pick of efd756da. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1430625/

Can folks affected by this bug test this kernel and see if it resolves the bug?

Thanks in advance!"

Tried to test this kernel.
No effect.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Paolo, can you post the output of uname -a ?

Revision history for this message
giovano iannotti (iannotti) wrote :

This is happening to me too. I have a fresh 15.04 install. After a few successful reboot, I get that message every time and can't login anymore . All the alternatives are useless. My installation is encrypted. The sequence is: 1)turn on; 2) Ubuntu 15.04 screen, asking for password; 3) correct password; 4) fsckd-cancel-msg: Press control+C to cancel all filesystems checks in progress; 5) auto reboot, Grub version 2.02 beta2-22ubuntu1 screen with alternatives, all useless; 6) *Ubuntu chosen; 7) ACPI probe failed message; 8) Ubuntu 15.04 passphrase screen again 9) passphrase correct; 10) ACPI PCC probe failed message screen with cursor this time; 11) three alternatives, all useless. When I try to reboot, it says Error getting authority 12) reboot. All starts again.
I think the problem is very important, because the computer is useless.
Have a Sony vpcf2.

Revision history for this message
giovano iannotti (iannotti) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

PCC (Platform Communication Channel) is a recent ACPI 5.0 addition. The driver does not find a PCC communications mailbox and just exits with that error message. It is not something to worry about, most machines don't have an ACPI PCCT table and they don't use this mechanism.

References:

ACPI specification Chapter 14.0 "Platform Communications Channel"
Linux source: drivers/mailbox/pcc.c

Revision history for this message
giovano iannotti (iannotti) wrote :

Colin,

How can it be something not to worry about if that's preventing me to use the computer?
"Machine displays error and hangs, will not proceed any further with boot. Pretty catastrophic, suggests that message not entirely harmless"

Thanks.

Revision history for this message
Colin Ian King (colin-king) wrote :

Looking at the driver and where it is occurring suggests to me that the driver is not the root cause, it is probably somewhere else. The message is the last one that you see and hence it is easy to mistake that at the reason for failure.

tags: added: kernel-da-key
Revision history for this message
Paolo Zonari (paolo-zonari) wrote :

For Joseph
3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:01 UTC 2015 i686 i686 i686 GNU/Linux

Revision history for this message
giovano iannotti (iannotti) wrote :

Thanks, Colin

I reinstalled Ubuntu and had the same problem. Now I reinstalled it for the third time, without encrypting the whole system. Only encrypted /home and it is working for the moment. Could it be related to the encryption process?

Revision history for this message
Nicola Corti (corti-nico) wrote :

I'm having the same issue on Ubuntu 15.04
--
Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Squabl (squabl) wrote :

I have the same issue as well. Installed 15.04 twice. At second attempt system booted to desktop but after upgrading everything and a reboot I couldn't boot to Ubuntu anymore.

Revision history for this message
parislanuit (ubuntu-banderilles) wrote :

Mobo gigabyte GA-965GM-S2 (AHCI 1.07 [08.04.2006])
GC Nvidia GTX 460 GM
Ubuntu 15.04 Kernel 3.19.0.16

Booting on AHCI

==> Boots fine if I use open source Nouveau driver

==> Boots fine but mentionning " [ 1.072944] ACPI PCC probe failed " if I use the NVIDIA 346.59 driver.

If I go back to Nouveau driver the "xxx probe failed" doesn't show again..

Revision history for this message
Ahmed (akha666-f) wrote :

I have the same issue with Ubuntu 15.04 after last kernel update, I saw some people talking about nvidia driver issue but I have ATI 5045HD
Can someone help me for fix this issue?

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

I have not problem with [0"]kernel 4.1.0-rc4"
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc4-unstable/

Thanks,
--
Cristian

Revision history for this message
historyb (historyb) wrote :

I have the same issue with an Intel video card on a Dell Inspiron 15 3000

Revision history for this message
Pavel (ppv) wrote :

I see the same message at the beginning of booting of Ubuntu Trusty with the linux kernel 3.19.0-21 and don't see it when boot Ubuntu with the kernel 3.13.0-55.

Revision history for this message
Colin Ian King (colin-king) wrote :

The error message is turned into a pr_debug debug message with this commit:

commit efd756daf4ddae3cec2404c4e0b680b7cfdd6a45
Author: Rafael J. Wysocki <email address hidden>
Date: Thu Feb 5 00:40:08 2015 +0100

    ACPI / PCC: Use pr_debug() for debug messages in pcc_init()

    pcc_init() uses pr_err() to print two messages that are really debug
    and not interesting to users. Replace those pr_err() with pr_debug().

    Reported-by: Cristian <email address hidden>
    Signed-off-by: Rafael J. Wysocki <email address hidden>

Revision history for this message
ludo33200 (ludo-cheron) wrote :

Bug also affects me
This bug comes with a SATA hard drive or wire problem that may be connected ... or not
My pc sometimes refuses to start saying it doesn't find any hard drive.
As i disconnect and then reconnect the SATA wires, pc starts (i see grub)
but now i cant login with Ubuntu because of this error "ACPI PCC probe failed [1.119018] ACPI probe failed \n starting version 219 \n Welcome to emergency mode ... Give root password for maintenance:"

Even if the "APCI PCC probe failed" message may not be main problem, any problem disallowing the pc to boot might be considered as ... critical.

Today error stopped after i've cleaned the SATA Power connector connected to my main hard drive.

Revision history for this message
thecure (keith-k) wrote :

Rebooted my main pc, first time in long time and got this error. Unable to reach desktop using either Nvidia, Nouveau and even pulling GPU and using Intel off mb. Not sure if related but getting sysctl errors also tried reinstalling systemd and even switching to upstart but both fail to reach reach desktop and hangs on acpci failure. Old kernels fail also. I keep correcting a no libgpg.so.0 version error but it won't hold between boots. Ubuntu 15.04 64bit gigabyte Z97X-UD5H-BK mb 32gb ram i7 4790K. MB and devices check out fine and live stick works fine. Hope some of this is of any use.

Revision history for this message
giovano iannotti (iannotti) wrote :

Colin seems to be right.

I removed Ubuntu and tried other distros and the error was there again and again.
So, I bought another HD. The message is still there, but there is no more error and Ubuntu works fine now. Finally, after almost one year fighting this catastrophic and annoying error.
So, anyone else tried changing possibly broken HD?

Revision history for this message
ludo33200 (ludo-cheron) wrote :

>So, anyone else tried changing possibly broken HD?
YES this anoyong bug comes with hard driver problems
I first thought my hd was going wrong and changed it
Then the problem still occured, i think i've got something wrong with sata wires or controller

Revision history for this message
thecure (keith-k) wrote : Re: [Bug 1430625] Re: ACPI PCC probe failed.

One drive was a little too warm but added fan and drive checks out ok with
no actual failures just past temperature warnings. I still get the ACPI
probe error but for once made it to failsafe desktop.

On Mon, Aug 3, 2015, 14:41 ludo33200 <email address hidden> wrote:

> >So, anyone else tried changing possibly broken HD?
> YES this anoyong bug comes with hard driver problems
> I first thought my hd was going wrong and changed it
> Then the problem still occured, i think i've got something wrong with sata
> wires or controller
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1430625
>
> Title:
> ACPI PCC probe failed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/1430625/+subscriptions
>

Revision history for this message
thecure (keith-k) wrote :

I'm an idiot. It was a flipping HDMI cable that went bad. Very strange it
gave me all kinds of mother board errors and unbootable Ubuntu install.
Stranger yet that USB stick would boot fine and I could chroot into my
Ubuntu LVM and run everything. Now boots slow from I'm sure from all the
"fixing" I did.

On Tue, Aug 4, 2015 at 2:00 PM, Keith Karnafel <email address hidden> wrote:

> One drive was a little too warm but added fan and drive checks out ok with
> no actual failures just past temperature warnings. I still get the ACPI
> probe error but for once made it to failsafe desktop.
>
> On Mon, Aug 3, 2015, 14:41 ludo33200 <email address hidden> wrote:
>
>> >So, anyone else tried changing possibly broken HD?
>> YES this anoyong bug comes with hard driver problems
>> I first thought my hd was going wrong and changed it
>> Then the problem still occured, i think i've got something wrong with
>> sata wires or controller
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1430625
>>
>> Title:
>> ACPI PCC probe failed.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/hundredpapercuts/+bug/1430625/+subscriptions
>>
>

Revision history for this message
Lárus Baldursson (baldursson64) wrote :

I use NVIDIA GT610 and binary driver 346.59 updates, works fine until after few hours i get bugs all over the screen, AOC and i have to turn off the computer, X org and 340 driver are not good for HD video.

Revision history for this message
మంగిపూడి కోదండరామ్ (Mangipudi Kodanda Ram) (kodanda) wrote :

I am on Kubuntu, with a hybrid Intel-NVIDIA card.

I have upgraded recently from 14.04->14.10->15.04, all in immediate succession. Upgrade process went without a problem and I was able to use the computer for a few days. Then once this "ACPI PCC probe failed" message appeared, but the boot process went well. After another day or two, now this message appears and says "Welcome to emergency mode! After logging in type "journalctl -xb" to view system logs, ... ... .. .. ... bal bla blah, asking for root password.

But I could not boot at all. A "systemctl default" choice also does not allow me to boot. Now the machine is unbootable.

How can I fix it?

Revision history for this message
మంగిపూడి కోదండరామ్ (Mangipudi Kodanda Ram) (kodanda) wrote :

I've also tried to login to root at this "Welcome to emergency mode....." prompt and purged all nvidia drivers and rebooted twice. No use, still exactly the same message...

Revision history for this message
Observation2016 (well-duh) wrote :

More painful when it comes up during installation process.

IDK about when a true fix to code might happen but...

a NOPCC option would nice for initial installations where newer users are not yet building their own kernels.

Better yet to help true noobs and expedite things everyone wanting to do a quick and dirty install before recompiling...
couldn't options for MOBO architecture be set automatically based on a quick examination of BIOS date?

For instance the hardware for PCC simply did not exist before a certain date. So that code ideally should be automatically turned off if the BIOS date is not later than that. Not a complete or perfect solution of course. But I suspect the volume of problem reports would be dramatically reduced as many newer Linux inductees tend to either start with well used older hardware or brand new hardware.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.