Hi @kate.mason, I just finished putting all this together! I don’t think it’s related to the EC, I would like to collect the coreboot logs, so I’ve put together a PureBoot build enabling the SPI flash console and added a tool to extract the log. It will take a bit longer than normal to boot or resume because I turned up debug logging, but it’s still pretty quick.
It’s important to reproduce the issue within the first few boots after flashing, because the logs will stop writing once the console space is full. I allocated a lot of space (1 MB) since we have plenty of room in flash, so you should have room to boot a handful of times.
Could you please do the following?
- Get this PureBoot build: https://source.puri.sm/firmware/releases/-/blob/PureBoot-Librem14-flashconsole-1/librem_14/pureboot-librem_14-Librem14-flashconsole-1.rom.gz
- Extract and copy to a USB flash drive, flash it normally from PureBoot (you can keep settings if desired)
- Boot the OS. (The first boot after flashing always takes longer due to memory re-training, just wait a minute or so.)
- Suspend from the OS and attempt to resume, confirm that this reproduces the failure
- Shut off system, boot to PureBoot and enter recovery shell
- Insert a USB flash drive and run:
extract_console.sh, this will read back the console from flash and save it on the flash drive. (Runrebootto reboot from the recovery console.)
Then send me the console.log created on the flash drive. (If you’d like to see it for yourself, tr -d '\377' | less <console.log - there will be a lot of empty space filled with FF and the log levels are not written as text, but less displays it reasonably.) At that point you can flash the PureBoot release again.
I’m focusing on the failure to resume rather than shutdown first because shutdown doesn’t produce any coreboot logs, if they are both caused by the same root issue it will be easier to troubleshoot this way.