[Bug 2023462] Re: chromeos_pstore.service started on non chrome platform hardware.

[wontfix]

Installed systemd 249.11-0ubuntu3.10 && Reboot.

Computer 1
:~$ systemctl list-dependencies systemd-pstore.service && systemd-analyze blame | grep pstore
systemd-pstore.service
● ├─-.mount
○ ├─modprobe at efi_pstore.service
● └─system.slice
     20ms modprobe at efi_pstore.service

Computer 2
:~$ systemctl list-dependencies systemd-pstore.service && systemd-analyze blame | grep pstore
systemd-pstore.service
● ├─-.mount
○ ├─modprobe at efi_pstore.service
● └─system.slice
     1ms modprobe at efi_pstore.service

Bug looks fixed if 1-20ms is normal range.

** Tags removed: verification-needed
** Tags added: verification-done verification-done-jammy

** Tags removed: verification-needed-jammy

** Tags removed: kinetic lunar mantic verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2023462

Title:
  chromeos_pstore.service started on non chrome platform hardware.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Kernel modules that provide pstore backends are unnecessarily loaded
  by systemd-pstore.service. While this is pretty benign behavior, it
  was introduced by an earlier SRU (bug 1978079) and is not consistent
  with newer releases in which systemd-pstore.service only tries to load
  efi_pstore.

  [Test Plan]

  Check which modules systemd-pstore.service depends on:

  $ systemctl list-dependencies systemd-pstore.service
  systemd-pstore.service
  * |--.mount
  * |-modprobe at chromeos_pstore.service
  * |-modprobe at efi_pstore.service
  * |-modprobe at pstore_blk.service
  * |-modprobe at pstore_zone.service
  * |-modprobe at ramoops.service
  * `-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-pstore.service ran, they might not get correct
  output. However, the original bug (bug 1978079) was only about
  efi_pstore, and that will still be loaded by systemd-pstore.service.
  On all releases newer than Jammy, only efi_pstore is loaded by
  systemd-pstore.service, and there have not been bug reports.

  [Original Description]

  systemd-analyze blame | grep pstore

  110ms modprobe at chromeos_pstore.service
  5ms modprobe at efi_pstore.service
  5ms modprobe at pstore_blk.service
  3ms modprobe at pstore_zone.service

  /lib/systemd/system/systemd-pstore.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023462/+subscriptions