This bug was fixed in the package systemd - 245.4-4ubuntu3.18
---------------
systemd (245.4-4ubuntu3.18) focal; urgency=medium
[ Nick Rosbrook ]
* core: make sure we don't get confused when setting TERM for a tty fd
(LP: #1959475)
File:
debian/patches/lp1959475-core-make-sure-we-don-t-get-confused-when-setting-TERM-fo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498
* shared/calendarspec: when mktime() moves us backwards, jump forward
(LP: #1966800)
File:
debian/patches/lp1966800-shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1f063541e44f6ff1a6904676d4264a2e49a09594
* network: do not remove localhost address (LP: #1979951)
File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=87f872b8c5451f353601fb606e7fd7a479217cef
* units: remove the restart limit on the [email protected] (LP: #1982462)
File:
debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68353ffaf3539e6a58ef62a8b50850f56eae29ea
[ Mustafa Kemal Gilor ]
* d/p/lp1978079-efi-pstore-not-cleared-on-boot.patch: pstore: Run after
modules are loaded. Thanks to Alexander Graf <[email protected]>.
(LP: #1978079)
Author: Mustafa Kemal Gilor
File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e60756f2079d6408abdb967127a1d9b9a0eba8c
-- Nick Rosbrook <[email protected]> Wed, 31 Aug 2022
11:27:33 -0400
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982462
Title:
Some modprobe loading services requested by the pstore service fail
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Jammy:
Fix Released
Status in systemd source package in Kinetic:
Fix Released
Bug description:
[Impact]
It has been detected that some modprobe services fail on UC22 after
the jammy upgrade 249.11-0ubuntu3.4:
$ systemctl --system --no-ask-password --no-pager list-units --state=failed
Failed units:
UNIT LOAD ACTIVE SUB DESCRIPTION
● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module
chromeos_pstore
● modprobe@efi_pstore.service loaded failed failed Load Kernel Module
efi_pstore
● [email protected] loaded failed failed Load Kernel Module
mtdpstore
● modprobe@pstore_blk.service loaded failed failed Load Kernel Module
pstore_blk
● modprobe@pstore_zone.service loaded failed failed Load Kernel Module
pstore_zone
● [email protected] loaded failed failed Load Kernel Module
ramoops
This happens because of some changes to systemd-pstore.service that
now has:
After=modprobe@efi_pstore.service [email protected]
modprobe@chromeos_pstore.service [email protected]
modprobe@pstore_zone.service modprobe@pstore_blk.service
Wants=modprobe@efi_pstore.service [email protected]
modprobe@chromeos_pstore.service [email protected]
modprobe@pstore_zone.service modprobe@pstore_blk.service
This causes too many tries of the modprobe services, that fail in the
end with
Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service:
Start request repeated too quickly.
Although we have seen this only on UC22, it potentially can affect
classic systems as well, as systemd-pstore.service is re-tried there a
few times too. See https://github.com/snapcore/core-base/issues/72 for
more details.
A fix for this is available upstream:
https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1
[Test Plan]
Start the device and check that there is no modprobe-pstore related
failed service. This is racy, so a few tries will be needed to make
sure things are fine.
[Where problems could occur]
The modprobe services are usually dependencies from other services, so
it should be fine if the retry behavior is controlled by those other
services. Risk should be small. If something goes wrong we might see a
lot of restarts for these services.
[Other Info]
Testing should happen on UC22 too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
