Error parsing pcc subspaces from pcct astra linux

Arch Linux

You are not logged in.

#1 2017-04-08 22:44:16

[ERROR ON BOOT] Error parsing PCC subspaces from PCCT

Hello everybody, sorry to bother you but I’m getting the following error
[0.460665] Error parsing PCC subspaces from PCCT.
I’m on a Thinkpad t440p.

I searched all over around but could not get something to get rid of that (Arch is starting, and everything is working but the error is still there).
Tried updating the BIOS to the latest version.
I have win7 installed in another partition but it was installed without EFI. Also, I selected LEGACY ONLY boot on bios.

Does anyone know what could be causing this?

#2 2017-04-09 06:47:44

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

Seems to be a regression with the 4.10.x kernel, though I found results referring to older kernels too. I don’t think any solution exists yet.

#3 2017-04-09 17:02:33

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

Thank you, is there something to worry about? or just ‘ignore’ it till a newer kernel fix it?
I don’t get what it’s refering to, so don’t know the severity either

#4 2017-09-06 17:04:35

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

Got the same error. No news on bugzilla. Do we have any news here?

#5 2017-09-06 19:34:22

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

@LnX_Archer welcome to the arch linux forums. linux-hardend is now on 4.13 so you could try to see if the bug has been fixed in that series.
If not I suggest you check if the bug report has been filed upstream at https://bugzilla.kernel.org/.

#6 2017-09-07 08:26:05

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

Same error on linux-hardened 4.13.a-1, HW is Dell E5450.

#7 2017-09-25 03:00:36

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

Same error with linux-hardened 4.13.3.a-1 running on my Thinkpad T450s.

#8 2017-09-26 15:03:49

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

The `linux-lts` doesn’t have this problem, as this is kernel 4.9. Tested on Thinkpad x250. Every other kernel 4.12/4.13 (such as `zen` and similars) show the warning errors

#9 2018-02-15 03:07:01

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

I still have this issue on 4.15 on my Thinkpad. Any news on this?

#10 2018-02-15 04:26:55

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

@Bronze, you can follow the Red Hat Bugzilla link posted above.

#11 2018-06-12 22:08:46

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

The bug report states this bug was recently fixed in kernel 4.16.12. I still get the error message. Are you guys still getting it?

#12 2018-06-12 22:22:30

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

No, it states it’s fixed in «kernel-4.16.12-300.fc28» and «kernel-4.16.12-200.fc27» because fedora included pending pataches, see https://bugzilla.redhat.com/show_bug.cgi?id=1435837#c82
So… are you running fedora?

#13 2018-06-12 22:23:17

Re: [ERROR ON BOOT] Error parsing PCC subspaces from PCCT

The bug report states this bug was recently fixed in kernel 4.16.12. I still get the error message.

From the redhat bug report it was fixed in kernel-4.16.12-300.fc28 kernel-4.16.12-200.fc27 are you running one of those specific kernels?
https://git.kernel.org/pub/scm/linux/ke … 34b0e7e615 only changes comments
https://www.spinics.net/lists/linux-acpi/msg82033.html not yet applied to mainline
https://git.kernel.org/pub/scm/linux/ke … b0e402283c this should be the needed patch
Edit:
Does apply cleanly to 4.17 if you try building 4.17.1 with the patch applied and it resolves the issue for then you could open an issue on the arch bug tracker asking for the patch to be applied.

Last edited by loqs (2018-06-12 22:28:06)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[Solved] Eroor parsing PCC subspaces from PCCT, Error on Boot / Linux Mint 18.3 don´t start

[Solved] Eroor parsing PCC subspaces from PCCT, Error on Boot / Linux Mint 18.3 don´t start

Post by ALDN04H » Sun Mar 11, 2018 3:43 pm

I started my Laptop like an hour before. But this time he give me an error massage after the Linux Mint start screen.

After that noithing more happens. Then i restart him with the power button. Then i startet him again.
But shortly after this restart this error appeared.

Then i want to know if this is an hardware or software error. So i insert my Linux Mint 17.3 live CD and boot again.
But now a other error appears.

But now he start after some minutes and error massages (show link below). So i try to reed the boot log with

You can see the results here:

After the next restart without live CD he is in a loop at this point after the Linux Mint start screen:

Now i searched this errors in the internet buit i dont find a solution for me because this multible errors. What i found out is that it can be something with the drivers but dont ask what exactly.
So my Laptop wont start anymore at the moment. So i hope you can help me.

Asus F555L
Intel Core I5
Nvidia GForce 930m
8GB Ram
500GB HDD
Linux Mint Cinnamon 18.3 64bit
Kernel Nr. (i dont know the number, i have no opportunity to take a look at it sry)

I you need more informations pls aks me and i will add it here:

Thank you for your help!

After 2 re-installation of Linux Mint, the problem disappeared. I could be a problem with the graphic driver. Or a problem with the cryptswap1 or something else. I got a various mix of different error massages. All in all i cant fix this bug, so i decided to reinstall and this was after the 2nd time successful. But Thx for you your help and time.

Источник

Error parsing PCC subspaces from PCCT

Bug Description

[Impact]
A scary-looking message appears in dmesg in several places during boot:

«Error parsing PCC subspaces from PCCT»

This could cause users to believe they have buggy firmware, in cases where it’s actually fine.

[Test Case]
dmesg | grep «Error parsing PCC subspaces»

[Fix]
Resolved in upstream commit that cleanly cherry-picks back to bionic:
8f8027c5f935 mailbox: PCC: erroneous error message when parsing ACPI PCCT

[Regression Risk]
PCC is a generic ACPI-defined mechanism for the OS and firmware to communicate. Since the fix does change how the tables are parsed, regression scenarios could include breakages in PCC clients (things that use this layer to communicate to firmware). The only Kconfig option I see in bionic’s source that depends on CONFIG_PCC is the CPPC library, which provides ACPI CPU performance management used by the cppc-cpufreq driver and is used by the scaling driver/governor for Sandy bridge processors.

Tested on an Nvidia DGX system. This is an upstream fix, so any regressions will have upstream support.

CVE References

This change was made by a bot.

description:	updated
Changed in linux (Ubuntu):
importance:	Undecided → High

Michael Heuberger, thank you for reporting this and helping make Ubuntu better.

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don’t have to create a new bug report.

Thank you for your understanding.

tags:	added: bios-outdated-1.23
Changed in linux (Ubuntu):
importance:	High → Low
status:	Confirmed → Incomplete

Thanks Christopher. Unfortunately your link to Lenovo has no BIOS files to download for Ubuntu environments.

What’s the most easiest way to upgrade BIOS on my machine then?

Hi, I have exactly the same problem (PCC error parsing etc.), I have Lenovo L540, just have updated my BIOS to the newest 1.82 version, didn’t help. Please, help

Thanks for response. It doesn’t want to work due to unsupported packeges (chrome maybe I don’t know what else) but I dont have simple access to my packages library or sth. Is there any simple way to uninstall all unsupported software and clean repo? Thanks

Hi, I still have a problem. When I write «ubuntu-bug linux» it shows that there’s problem with linux-image- 4.2.0-25- generic and it cannot report the error; that it’s not an official Ubuntu package (kernel?!) and ask to delete/uninstall all such packages.
I also cannot update through apt-get. 🙁 Temporary errors during translating repos. I’m not sure if my spelling is correct, I haven’t got it written in english.
Please help, thanks a lot! It would be nice just to have an opportunity to update the system..

Unfortunately I cannot do this, I tried to generate this report file also on older kernels I still have, but there’s the same problem. I just can’t use «ubuntu-bug linux» is there any other way?

Ok, I’ve set up the internet connection and upgraded system with apt-get. There’s only problem with linux-generic, linux-headers- generic, linux-image- generic. I don’t know how to update it. There’s still a problem with generating a log with ubuntu-bug-linux.. I really appreciate your engagement. Thank you

Hi, I finally managed to generate this file after updating my system. I don’t know why, but it worked. I’ll upload the report here, ok? I hope it’s gonna be useful. Thanks

This error is also present on an Asus ZenBook UX305F

Error is also an Lenovo Think Pad X1 Carbon, Intel® Core™ i7-5600U CPU @ 2.60GHz × 4

N14ET32W (1.10 )
08/13/2015

4.5.0-040500- generic #201603140130 SMP Mon Mar 14 05:32:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I followed this guide, and have the latest BIOS/EFI (1.24) On an X1 Carbon 2nd Gen:

Linux X1-C 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Lenovo Think Pad X1 Carbon, Intel® Core™ i7-5600U CPU @ 2.60GHz × 4
Update the bios with the tutorial but for model 20BS Think Pad X1 Carbon, and all very well.

But still the error:

[ 0.115516] Error parsing PCC subspaces from PCCT

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Same Problem on T440p.

Bios:
GLET83WW (2.37 )
03/31/2016

Error:
[ 0.197312] Error parsing PCC subspaces from PCCT

Dualboot System with Windows 8.1

Farst Startup is disabled.

Booting with Nvidia Card on.

I am getting the error on thinkpad x250 under 16.04 LTS 4.4.0-45-generic. Although the laptop shipped with Win 8.1 there is no dual boot. Ubuntu only. Looking forward to any update.

I have fixed the issue by editing /etc/fstab file.
I have deleted entries of two disks that were used by WIndows OS from fstab and the problem disappeared.

finally, but I reainstalled system, thanks for letting know!

2016-11-30 15:53 GMT+01:00 dmitry :

Hardware:
Lenovo L450 [Processor: Intel® Core™ i5-5200U CPU @ 2.20GHz × 4; Graphics: Intel® HD Graphics 5500 (Broadwell GT2)]

### Factory delivery (as was) with Microsoft Windows 8 pre-installed on HDD.

### HDD removed and replaced for new SDD: Samsung SSD 850 EVO 250GB.
### Additional RAM slot filled.
### SDD && RAM integrity tested with SMART diagnostics && memtest_86x, respectively. No errors found.

### Ubuntu 15.10 installed on on SDD (formatted and encrypted according to wizard on Ubuntu Live-USB). First occurrence of of ‘Error parsing PCC subspaces from PCCT’. Distribution upgraded to Ubuntu 16.04 LTS (is now).

###### System Information:
### Kernel:

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use ‘blkid’ to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#

### Boot from EFI & info:

$ mount | grep efivars
efivarfs on /sys/firmware/ efi/efivars type efivarfs (rw,nosuid, nodev,noexec, relatime)

Handle 0x0031, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: JDET54WW (1.16 )
Release Date: 08/19/2015
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 16384 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.16
Firmware Revision: 1.16

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0010, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20DTCTO1WW
Version: ThinkPad L450
Serial Number: PF0E0Y2S
UUID: 7A299C81- 542D-11CB- 9157-B3EF243807 44
Wake-up Type: Power Switch
SKU Number: LENOVO_ MT_20DT_ BU_Think_ FM_ThinkPad L450
Family: ThinkPad L450

BootCurrent: 0014
Time.

The system crashes I mentioned are likely unrelated; I noticed a 3rd party daemon to randomly hog up all of my CPU.
. Nevermind.

Interestingly tough, I observed the ‘Error parsing PCC subspaces from PCCT’ also while booting and running from a live-USB on the same system as mentioned above (with all other /dev/sdX drives unmounted since I intended to run a fsck check).

Just speculation from a Linux-beginner on my side, but doesn’t this indicate an issue with the motherboard firmware; i.e. conflicts in either the BIOS/UEFI, MBR, etc.?

Did anyone solved the problem?I met the problem on server,the OS version is ubuntu 16.04.02,hope anyone can help me!

Same problem on Thinkpad L440, cannot even run Ubuntu, it crashes with this message on screen. Totally lost, have no clue, this discussion does not give a clear guide, what to do.
Problem appeared all of a sudden, no new install, no dual boot.
Please help.

I had to reinstall the system, still have an error, but it works at least

2017-09-26 8:58 GMT+02:00 PrPom.cz :

description:	updated
Changed in linux (Ubuntu Bionic):
status:	New → Confirmed
assignee:	nobody → dann frazier (dannf)

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

—————
linux (4.17.0-7.8) cosmic; urgency=medium

—————
linux (4.15.0-33.36) bionic; urgency=medium

* RTNL assertion failure on ipvlan (LP: #1776927)
— ipvlan: drop ipv6 dependency
— ipvlan: use per device spinlock to protect addrs list updates
— SAUCE: fix warning from «ipvlan: drop ipv6 dependency»

* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
— test_bpf: flag tests that cannot be jited on s390

* HDMI/DP audio can’t work on the laptop of Dell Latitude 5495 (LP: #1782689)
— drm/nouveau: fix nouveau_ dsm_get_ client_ id()’s return type
— drm/radeon: fix radeon_ atpx_get_ client_ id()’s return type
— drm/amdgpu: fix amdgpu_ atpx_get_ client_ id()’s return type
— platform/x86: apple-gmux: fix gmux_get_ client_ id()’s return type
— ALSA: hda: use PCI_BASE_ CLASS_DISPLAY to replace PCI_CLASS_ DISPLAY_ VGA
— vga_switcheroo: set audio client id according to bound GPU id

* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
— UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix sockets

* Update2 for ocxl driver (LP: #1781436)
— ocxl: Fix page fault handler in case of fault on dying process

* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
— net: core: Expose number of link up/down transitions
— dev: always advertise the new nsid when the netns iface changes
— dev: advertise the new ifindex when the netns iface changes

* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
— block, bfq: fix occurrences of request finish method’s old name
— block, bfq: remove batches of confusing ifdefs
— block, bfq: add requeue-request hook

* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
— ALSA: hda: add mute led support for HP ProBook 455 G5

* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
— i2c: xlp9xx: Fix issue seen when updating receive length
— i2c: xlp9xx: Make sure the transfer size is not more than
I2C_ SMBUS_BLOCK_ SIZE

* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
— x86/kvm: fix LAPIC timer drift when guest uses periodic mode

* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
— [Config:] d-i: Add ax88179_178a and r8152 to nic-modules

* Nvidia fails after switching its mode (LP: #1778658)
— PCI: Restore config space on runtime resume despite being unbound

* Kernel error «task zfs:pid blocked for more than 120 seconds» (LP: #1781364)
— SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3

* CVE-2018-12232
— PATCH 1/1] socket: close race condition between sock_close() and
sockfs_ setattr( )

* CVE-2018-10323
— xfs: set format back to extents if xfs_bmap_ extents_ to_btree

Источник

«Error parsing PCC subspaces from PCCT» during initializing the system

Bug Description

After an update such an error shows when I turn my xubuntu on.

Piotr Miszczak, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http:// kernel. ubuntu. com/

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn’t boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you’ve tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel- fixed-upstream
kernel- fixed-upstream- X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel- bug-exists- upstream
kernel- bug-exists- upstream- X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel- bug-exists- upstream.

Also, you don’t need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Источник

Ubuntu: Error parsing PCC subspaces from PCCT: ACPI PCC probe failed

Question:

I have a Lenovo Thinkpad e540 laptop with dual graphics, Intel integrated and Nvidia GT 740m Discrete. After changing from nouveau drivers to Nvidia binary driver 346.82 proprietary before login screen I’ve got a message:

I’ve read somewhere that if I put in grub file quiet splash nomodeset that will fix this, but that doesn’t work for me, then I get into login loop.

How can I fix this?

Solution:1

I had the same problem after installing Ubuntu 16.04 on the Lenovo w540 with preinstalled Win 8.1. It appeared that I didn’t install Ubuntu with correct bootloader. The Windows was booting in UEFI mode while the Ubuntu in BIOS mode.So I’ve reinstalled Ubuntu, but this time I read:

The problem with the PCC parsing. didn’t appear since then.

I don’t know if it’s relevant but I’ve installed Ubuntu on a separate drive with separate efi partition.In my BIOS settings I have now another entry on the boot order list: ‘ubuntu’. It was placed by the Ubuntu installer on the first place so I moved it below the USB stuff but above the Windows Boot Manager so I can boot from USB key or choose from the GRUB2 boot menu which system to boot on each restart.

Solution:2

Due to the response on the comment, and that it apparently works.

Answer: Usually happens on Linux-Windows dual boot. Disable hiberboot (fast startup) in Windows. If it comes back after some upgrade, just boot to Windows and restart, worked on my friend’s PC.

Windows > Control Panel > All Control Panel Items > Power Options > System Settings > Change settings that are currently unavailable (UAC) > Turn on fast startup (recommended) ※ unchecked this.

Note: Well, it really isn’t recommended to dual boot Windows with Linux.

Источник

Keywords: Status: CLOSED ERRATA Alias: None Product: Fedora Classification: Fedora Component: kernel Sub Component: Version: 27 Hardware: Unspecified OS: Unspecified Priority: low Severity: low Target Milestone: — Assignee: Al Stone QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Duplicates (1): 1468315 (view as bug list) Depends On: Blocks: TreeView+ depends on / blocked		Reported: 2017-03-24 23:48 UTC by Dimitris Modified: 2018-06-05 17:36 UTC (History) CC List: 72 users (show) Fixed In Version: kernel-4.16.12-300.fc28 kernel-4.16.12-200.fc27 Doc Type: If docs needed, set a value Doc Text: Clone Of: Environment: Last Closed: 2018-05-29 11:20:09 UTC Type: Bug Dependent Products:

Attachments (Terms of Use) Dump of dmesg which contains the PCCT error message (87.53 KB, text/plain) 2017-06-14 05:46 UTC, Max Roeleveld no flags Details /sys/firmware/acpi/tables/PCCT from a Dell laptop (110 bytes, application/octet-stream) 2018-03-20 09:45 UTC, Aleksei Kovura no flags Details /sys/firmware/acpi/tables/FACP from a Dell laptop (268 bytes, application/octet-stream) 2018-03-20 09:46 UTC, Aleksei Kovura no flags Details FADT and PCCT tables for ThinkPad T450s (804 bytes, application/x-gzip) 2018-03-20 19:51 UTC, Romualdas Mincevicius no flags Details /sys/firmware/acpi/tables/FACP from an ASUS ROG G551JW (268 bytes, application/octet-stream) 2018-03-28 02:21 UTC, Franco Geller no flags Details /sys/firmware/acpi/tables/PCCT from an ASUS ROG G551JW (110 bytes, application/octet-stream) 2018-03-28 02:23 UTC, Franco Geller no flags Details patch 1/3 — simple documentation fix only (1.73 KB, patch) 2018-04-04 21:19 UTC, Al Stone no flags Details | Diff patch 2/3 — fix a possible subtable parsing issue (2.29 KB, patch) 2018-04-04 21:20 UTC, Al Stone no flags Details | Diff patch 3/3 — correct bogus error message about PCCT (9.09 KB, patch) 2018-04-04 21:21 UTC, Al Stone no flags Details | Diff FACP from Sony Vaio Pro 13 (268 bytes, application/octet-stream) 2018-04-23 06:09 UTC, Dominik ‘Rathann’ Mierzejewski no flags Details PCCT from Sony Vaio Pro 13 (110 bytes, application/octet-stream) 2018-04-23 06:11 UTC, Dominik ‘Rathann’ Mierzejewski no flags Details Upstream patch (as accepted in linux-pm) (10.13 KB, patch) 2018-05-24 17:41 UTC, Al Stone no flags Details | Diff View All Add an attachment (proposed patch, testcase, etc.)

---

---

---

---

---

---

---

---

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com