[202311] Fix pstore service not running #54
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
The pstore service is not able to start, even if there are backtrace for kernel panics/oops in the UEFI.
This carry a risk of filling up the UEFI storage space.
Work item tracking
How I did it
Systemd on newer version has fixed this issue by adding a dependency on the kernel module to ensure we only scan for
pstate after we can actually see pstate.
Took this fix to our system.
How to verify it
Simulate a kernel crash, and make sure that when system is live again, the backtrace are located on /var/lib/systemd/pstore/ and not /sys/fs/pstore/
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)