Why is this bug marked as Done?
Issue still persists with 4.17.0-2-amd64 on ASUS N551JM laptop.
If users (upgrading from Strech) are expected to execute these workarounds, maybe there should be
NEWS entry of some sort?
I confirm this for 4.17.0-2-amd64 #1 SMP Debian 4.17.14-1 (2018-08-13 on
a XPS 13 9360.
Hi,
I can confirm to see this on Debian/buster AMD64 with...
linux-image-4.17.0-1-amd64 (4.17.8-1)
...and removing all dmesg-efi-*.enc.z files in /sys/fs/pstore/...
...and rebooting made the failures in dmesg go away.
Not sure what 'gzip: stdin: unexpected end of file' means exactly in
Package: src:linux
Version: 4.17.3-1
Severity: normal
Dear Maintainer,
Updating to 4.17, dmesg shows pstore: crypto_comp_decompress failed
I didn't know what's pstore used for, maybe efi?
Looking at config, maybe some pstore_*_compress should be set?
grep -i pstore /boot/config-4.17.0-1-amd64
4 matches
Mail list logo
