Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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.n
Encountered last night (2025-03-30) on Debian 12 on systemd package
252.36-1~deb12u1. 100% CPU usage by /sbin/init stopped either by
stopping .timer units manually or by waiting until clock changed
00:59:59Z -> 02:00:00+0100.
This is evidenced by one of the multiple affected machines logs showing
I took a bit of time to try to reproduce, without success. Here were my
steps:
$ lxc launch ubuntu:jammy --vm jammy
Launching jammy
$ lxc exec jammy bash
root@jammy:~# apt update && apt install -y atop
...
root@jammy:~# systemctl stop systemd-timesyncd
root@jammy:~# timedatectl set-timezone Europe
I'm not sure about the proposed fix, but:
* Dublin is probably not the only timezone impacted.
* We should probably try to reproduce that and confirm the bug on Jammy, but
also check Noble, just to be sure.
** Tags added: rls-jj-incoming
** Also affects: systemd (Ubuntu Jammy)
Importance: Und
how to reduce:
1. Stop clock synchronization
systemctl stop chrony
2. Set the timezone to Dublin
timedatectl set-timezone Europe/Dublin
3. Change the time to waitting for Daylight saving time switch
timedatectl set-time "2024-03-30 23:59:50"
At 0 o'clock, the system is executing atop logrotatio
5 matches
Mail list logo
