chromeos_pstore.service started on non chrome platform hardware.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Low
|
Unassigned |
Bug Description
[Impact]
Kernel modules that provide pstore backends are unnecessarily loaded by systemd-
[Test Plan]
Check which modules systemd-
$ systemctl list-dependencies systemd-
systemd-
* |--.mount
* |-modprobe@
* |-modprobe@
* |-modprobe@
* |-modprobe@
* |-<email address hidden>
* `-system.slice
On an affected machine, we see several pstore providers in addition to efi_pstore. On a patched system, we should only see efi_pstore.
[Where problems could occur]
If somehow a user was running a configuration where one of the other modules was needed for pstore on their system, and that module was not loaded when systemd-
[Original Description]
systemd-analyze blame | grep pstore
110ms modprobe@
5ms modprobe@
5ms modprobe@
3ms modprobe@
/lib/systemd/
Related branches
- Lukas Märdian: Approve
-
Diff: 796 lines (+623/-45)16 files modifieddebian/patches/lp1977630-fix_machinectl_pull_tar.patch (+81/-0)
debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch (+5/-4)
debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch (+29/-0)
debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch (+80/-0)
debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch (+41/-0)
debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch (+69/-0)
debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch (+26/-0)
debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch (+59/-0)
debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch (+33/-0)
debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch (+58/-0)
debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch (+67/-0)
debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch (+47/-0)
debian/patches/series (+11/-1)
debian/systemd.postinst (+16/-1)
debian/tests/tests-in-lxd (+1/-1)
dev/null (+0/-38)
tags: | added: jammy kinetic lunar mantic |
summary: |
- chromeos_pstore.service running on non chrome platform hardware. + chromeos_pstore.service started on non chrome platform hardware. |
tags: | added: foundations-todo |
description: | updated |
Changed in systemd (Ubuntu Jammy): | |
status: | Triaged → In Progress |
This is fixed in Lunar and newer (https:/ /github. com/systemd/ systemd/ commit/ 8b8bd621e1d1680 8678fc3afed257d f1fa03a281). Is this really causing any harm on Jammy though? I'm not sure we need to do anything about it on Jammy.