FS#55229 - [linux-lts] Fail to boot: Error parsing PCC subspaces from PCCT

Attached to Project: Arch Linux
Opened by Jakob Schöttl (nurfz) - Monday, 21 August 2017, 19:54 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 22 August 2017, 05:07 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I cannot boot my system anymore. I had linux-lts installed. All I can remember what I did before, was removing the deepin-daemon (which I never intended to install). Automatic upgrades on that day are attached.

The boot messages are:

Starting vmlinuz-linux
Using load options 'ro root=UUID=xxxx initrd=boot\initramfs-linux-lts.img

<clear screen>

Error parsing PCC subpaces from PCCT
ACPI Error: Needed type [Reference], found [Integer] ffff8d2033e3
...
ERROR: resume: hibernation device '/dev/sda7' not found
Waiting 10 seconds for device /dev/sda7
...
You are now beeing dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

<not responding to keyboard input>



Additional info:

* package version(s)

linux-lts-4.9.44-1
Same problem when downgrade to:
linux-lts-4.9.43-1
linux-lts-4.9.42-1
linux-lts-4.9.41-1
Same problem when installing latest linux-zen

Works with latest linux

* config and/or log files etc.

- Hardware
- Lenovo Thinkpad T450s
- Intel Corporation HD Graphics 5500 (rev 09)
- Picture of boot messages
- List of upgrades on that day

I would use linux instead of linux-lts but then I get system freezes due to a
different bug, possibly related to #53657.
   upgrades.txt (0.8 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 22 August 2017, 05:07 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Look for support at irc/forum. Seems to be a user configuration issue.
Comment by Jakob Schöttl (nurfz) - Monday, 21 August 2017, 19:58 GMT
Picture of boot messages

--- (cannot comment anymore)

Thanks for your feedback, loqs!
Yes, I booted from a live usb stick and installed different kernel versions.
When booting normally, I had no choice to select a specific boot entry.

I don't know for sure which boot loader I am using.
refind-efi is installed, but this command displays "GRUB":
sudo dd if=/dev/sda bs=512 count=1 2>/dev/null | strings | grep -Eoi 'grub|lilo|acronis|reboot|refind'

I guess I have to (1) boot from usb stick, (2) mount the fs and chroot, then (3) mount the boot partition to /boot and then (4) call refind-install or grub-install?
Maybe this fixes the problem. At my last attempts, I forgot step (3).
   boot-messages.jpg (367.2 KiB)
Comment by loqs (loqs) - Monday, 21 August 2017, 21:49 GMT
The upgrade packages do not include linux-lts or anythinng that should have been included in linux-lts's initrd so it is interesting that it started failing after those updates.
You have been able to downgrade linux-lts so you can boot the filesystems from live media?
The picture references 4.12.8-2 did you choose the wrong boot entry by accident on that boot, it also seems to indicate a resume parameter was specified which you do not mention.

Loading...