[Bug 1229721] New: journal is not saved to persistent storage since august 20 2024
https://bugzilla.suse.com/show_bug.cgi?id=1229721 Bug ID: 1229721 Summary: journal is not saved to persistent storage since august 20 2024 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: seife@novell.slipkontur.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- After a few unexpected reboots/powerdowns (hardware battery controller of my thinkpad locked up and needed reset), I found that there are no journal entries persisted since I rebooted on august 20: ``` mixi:~ # journalctl --since "2024-08-20 20:54:57"|head Aug 20 20:54:57 mixi systemd[1]: Unmounted /opt. Aug 20 20:54:57 mixi systemd[1]: root.mount: Deactivated successfully. Aug 20 20:54:57 mixi systemd[1]: Unmounted /root. Aug 20 20:54:57 mixi systemd[1]: srv.mount: Deactivated successfully. Aug 20 20:54:57 mixi systemd[1]: Unmounted /srv. Aug 20 20:54:57 mixi systemd[1]: tmp.mount: Deactivated successfully. -- Boot 5ab5c43121a740329f4a0b3dfb160b65 -- Aug 25 10:32:45 mixi kernel: Linux version 6.11.0-rc4-4.g884d35d-default (geeko@buildhost) (gcc (SUSE Linux) 13.3.1 20240807 [revision 9d368828bd4d04ce507e02a581be850fca849fae], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.43.0.20240806-1) #1 SMP PREEMPT_DYNAMIC Fri A ug 23 20:02:05 UTC 2024 (884d35d) Aug 25 10:32:45 mixi kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.11.0-rc4-4.g884d35d-default root=/dev/mapper/system-root rd.lvm. lv=system/swap resume=/dev/system/swap mitigations=auto security=apparmor splash=silent Aug 25 10:32:45 mixi kernel: BIOS-provided physical RAM map: ``` I did reboot a few times already today: ``` mixi:~ # last reboot|head reboot system boot 6.11.0-rc4-4.g88 Sun Aug 25 10:32 - still running reboot system boot 6.11.0-rc4-2.g59 Sun Aug 25 10:22 - 10:32 (00:10) reboot system boot 6.11.0-rc4-2.g59 Sun Aug 25 10:16 - 10:20 (00:04) reboot system boot 6.11.0-rc4-2.g59 Sun Aug 25 10:08 - 10:12 (00:03) reboot system boot 6.11.0-rc4-2.g59 Sat Aug 24 23:28 - crash reboot system boot 6.11.0-rc4-2.g59 Tue Aug 20 20:55 - crash reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:19 - 20:54 (2+06:35) reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:11 - 14:18 (00:07) reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:09 - 14:11 (00:01) reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:04 - 14:07 (00:02) ``` But journalctl does not know about those: ``` mixi:~ # journalctl --list-boots |tail -9 3eb9bb2611184870a1ed229d864a69b8 Sat 2024-07-27 10:36:35 CEST Sat 2024-07-27 10:45:05 CEST -8 4bf6bb115cfc4ab4b3126b1a00c6c9b7 Sat 2024-07-27 10:45:20 CEST Mon 2024-07-29 16:13:28 CEST -7 8286230fe28344c59fa48996fd0807a7 Mon 2024-07-29 16:14:34 CEST Tue 2024-08-13 11:29:22 CEST -6 1a4645e76c634668bce7dce043b72833 Tue 2024-08-13 11:31:06 CEST Tue 2024-08-13 11:32:44 CEST -5 eebf61e09fe24938ad85d14aa7727d9c Tue 2024-08-13 11:33:00 CEST Sun 2024-08-18 14:04:40 CEST -4 2c1c576c22d84d82b8373c6df2a57d42 Sun 2024-08-18 14:04:57 CEST Sun 2024-08-18 14:07:02 CEST -3 855b89b2e857488fa542912da26616b8 Sun 2024-08-18 14:09:33 CEST Sun 2024-08-18 14:11:05 CEST -2 210c7a03d56a4d3e8f316b3c5feb0691 Sun 2024-08-18 14:11:20 CEST Sun 2024-08-18 14:18:36 CEST -1 d131d91a089e4de6ba71c982e7a97167 Sun 2024-08-18 14:19:38 CEST Tue 2024-08-20 20:54:57 CEST 0 5ab5c43121a740329f4a0b3dfb160b65 Sun 2024-08-25 10:32:45 CEST Sun 2024-08-25 11:23:23 CEST ``` -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c1 --- Comment #1 from Stefan Seyfried <seife@novell.slipkontur.de> --- JFTR: on August 20 I did zypper dup, from /var/log/zypp/history: ``` 2024-08-20 20:48:54|command|root@mixi|'zypper' '-v' 'dup' '--no-recommends'| ``` nothing systemd-releated was updated during this run. the last available journal (-b -1) has the following lines related to journal itself: ``` mixi:~ # journalctl -b -1|grep journal Aug 18 14:19:38 mixi systemd-journald[206]: Collecting audit messages is disabled. Aug 18 14:19:38 mixi systemd-journald[206]: Journal started Aug 18 14:19:38 mixi systemd-journald[206]: Runtime Journal (/run/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 8M, max 314.9M, 306.9M free. Aug 18 14:19:44 mixi systemd-journald[206]: Journal stopped Aug 18 14:19:45 mixi systemd-journald[206]: Received SIGTERM from PID 1 (systemd). Aug 18 14:19:45 mixi systemd[1]: run-credentials-systemd\x2djournald.service.mount: Deactivated successfully. Aug 18 14:19:45 mixi systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. Aug 18 14:19:45 mixi systemd-journald[690]: Collecting audit messages is disabled. Aug 18 14:19:45 mixi systemd-journald[690]: Journal started Aug 18 14:19:45 mixi systemd-journald[690]: Runtime Journal (/run/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 8M, max 314.9M, 306.9M free. Aug 18 14:19:45 mixi systemd[1]: systemd-journald.service: Deactivated successfully. Aug 18 14:19:46 mixi systemd-journald[690]: Time spent on flushing to /var/log/journal/5acde102e5594ff3bc6496cb06b393f0 is 150.125ms for 1367 entries. Aug 18 14:19:46 mixi systemd-journald[690]: System Journal (/var/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 560.4M, max 4G, 3.4G free. Aug 18 14:19:47 mixi systemd-journald[690]: Received client request to flush runtime journal. Aug 18 14:19:53 mixi rsyslogd[1878]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2406.0] ``` while the current boot has much less: ``` mixi:~ # journalctl -b|grep journal Aug 25 10:32:45 mixi systemd-journald[205]: Collecting audit messages is disabled. Aug 25 10:32:45 mixi systemd-journald[205]: Journal started Aug 25 10:32:45 mixi systemd-journald[205]: Runtime Journal (/run/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 8M, max 314.9M, 306.9M free. Aug 25 10:32:53 mixi systemd-journald[205]: Received client request to flush runtime journal. Aug 25 10:33:04 mixi rsyslogd[1916]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2406.0] ``` So it looks like the "handover" from initramfs is not happening properly? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c2 --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> --- Note that on 2024-08-13, a previous zypper dup did update dracut *but not rebuild the initramfs*. Subsequent reboots did still record to journal. Then on 2024-08-20 20:48, the next zypper dup did cause the initrd to be regeneated and after the reboot on 20:55: no more journal So it might be an issue with the updated dracut? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c3 --- Comment #3 from Stefan Seyfried <seife@novell.slipkontur.de> --- I did downgrade to dracut-059+suse.628.g20b345b4-1.1, rebuilt the initrd, rebooted but this did not change anything -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c4 --- Comment #4 from Christophe Marin <christophe@krop.fr> --- Check what systemctl status --failed and systemctl status 'systemd-journald.*' return -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c6 --- Comment #6 from Stefan Seyfried <seife@novell.slipkontur.de> --- It crashed due to a faulty power management controller (guessed, a reset through the pinhole on the T480's bottom finally fixed it and the battery gauge) by hard power off, after 4 days of uptime (first crash) and a few hours uptime (second crash). It did always reach login. mixi:~ # systemctl status --failed mixi:~ # systemctl status systemd-journald.* --no-pager ● systemd-journald.socket - Journal Sockets Loaded: loaded (/usr/lib/systemd/system/systemd-journald.socket; static) Active: active (running) since Thu 2024-08-29 07:58:06 CEST; 8h ago Invocation: 2d8f587801434aa79af7b280f25c5914 Triggers: ● systemd-journald.service Docs: man:systemd-journald.service(8) man:journald.conf(5) Listen: /run/systemd/journal/socket (Datagram) /run/systemd/journal/stdout (Stream) CGroup: /system.slice/systemd-journald.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Active: active (running) since Thu 2024-08-29 07:58:06 CEST; 8h ago Invocation: 98719a2085714e39afcfe98c9c4d662b TriggeredBy: ○ systemd-journald-audit.socket ● systemd-journald.socket ● systemd-journald-dev-log.socket Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 205 (systemd-journal) Status: "Processing requests..." Tasks: 1 (limit: 18762) FD Store: 36 (limit: 4224) CPU: 478ms CGroup: /system.slice/systemd-journald.service └─205 /usr/lib/systemd/systemd-journald Aug 29 07:58:06 mixi systemd-journald[205]: Collecting audit messages is disabled. Aug 29 07:58:06 mixi systemd-journald[205]: Journal started Aug 29 07:58:06 mixi systemd-journald[205]: Runtime Journal (/run/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 8M, max 3….9M free. Aug 29 07:58:14 mixi systemd-journald[205]: Received client request to flush runtime journal. Notice: journal has been rotated since unit was started, output may be incomplete. Hint: Some lines were ellipsized, use -l to show in full. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c7 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #7 from Andrei Borzenkov <arvidjaar@gmail.com> --- (In reply to Stefan Seyfried from comment #1)
So it looks like the "handover" from initramfs is not happening properly?
May be. Reboot with systemd.log_level=debug printk.devkmsg=on log_buf_len=16M and provide full "journalctl -b" output. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c8 --- Comment #8 from Stefan Seyfried <seife@novell.slipkontur.de> --- Created attachment 877033 --> https://bugzilla.suse.com/attachment.cgi?id=877033&action=edit journalctl -b with debug commandline parameters -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c10 --- Comment #10 from Stefan Seyfried <seife@novell.slipkontur.de> --- I probably did capture it too early, lightdm was up and logged in, then I switched to vt1 and logged in to capture it. I'll retry and wait longer before capturing This boot (I did reboot without the debug after capturing) now has: Aug 30 08:00:38 mixi systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway. Aug 30 08:00:38 mixi systemd[1]: Mounting /var... Aug 30 08:00:38 mixi systemd[1]: Starting Cryptography Setup for cr_system-home... Aug 30 08:00:38 mixi kernel: psmouse serio2: Failed to enable mouse on synaptics-pt/serio0 Aug 30 08:00:38 mixi (udev-worker)[751]: event2: Failed to write 'sensitivity' attribute: Input/output error Aug 30 08:00:38 mixi kernel: iwlwifi 0000:03:00.0: base HW address: 38:ba:f8:f4:ed:63, OTP minor version: 0x4 Aug 30 08:00:38 mixi systemd[1]: Mounted /.snapshots. Aug 30 08:00:38 mixi systemd[1]: Mounted /boot/efi. Aug 30 08:00:38 mixi systemd[1]: Mounted /boot/grub2/i386-pc. Aug 30 08:00:38 mixi systemd[1]: Mounted /boot/grub2/x86_64-efi. Aug 30 08:00:38 mixi systemd[1]: Mounted /opt. Aug 30 08:00:38 mixi systemd[1]: Mounted /root. Aug 30 08:00:38 mixi systemd[1]: Mounted /srv. Aug 30 08:00:38 mixi systemd[1]: Mounted /usr/local. Aug 30 08:00:38 mixi systemd[1]: Mounted /var. Aug 30 08:00:38 mixi systemd[1]: Starting Load AppArmor profiles... Aug 30 08:00:38 mixi systemd[1]: Started Forward Password Requests to Plymouth. Aug 30 08:00:38 mixi systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight... Aug 30 08:00:38 mixi systemd[1]: Starting Load/Save Screen Backlight Brightness of leds:tpacpi::kbd_backlight... Aug 30 08:00:38 mixi kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' Aug 30 08:00:38 mixi kernel: mc: Linux media interface: v0.10 Aug 30 08:00:38 mixi systemd[1]: Starting Flush Journal to Persistent Storage... Aug 30 08:00:38 mixi systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). it probably did not flush anything, because the files are still old: mixi:~ # l /var/log/journal/5acde102e5594ff3bc6496cb06b393f0/ -rt | tail -2 -rw-r----- 1 root systemd-journal 33554432 Aug 20 20:54 system.journal -rw-r-----+ 1 root systemd-journal 16777216 Aug 20 20:54 user-10329.journal -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c11 --- Comment #11 from Stefan Seyfried <seife@novell.slipkontur.de> --- Created attachment 877037 --> https://bugzilla.suse.com/attachment.cgi?id=877037&action=edit retry for journalctl -b with debug I did check with systemctl list-jobs that boot had finished and with "journalctl -f" that nothing was happening anymore before capturing. Also, var.mount (which I found as "waiting for..." in previous log) was definitely finished, but I cannot find it in this journalctl output as being executed? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c16 --- Comment #16 from Stefan Seyfried <seife@novell.slipkontur.de> --- Created attachment 877075 --> https://bugzilla.suse.com/attachment.cgi?id=877075&action=edit journalctl -b with systemd.log_level=debug udev.log_level=info This one seems less truncated :-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c17 --- Comment #17 from Stefan Seyfried <seife@novell.slipkontur.de> --- Created attachment 877076 --> https://bugzilla.suse.com/attachment.cgi?id=877076&action=edit cat-config systemd/journald.conf Now that I see it: I have rsyslogd installed, default config, the only non-standard thing is a custom time format template (which I have been using since 10 years) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c18 --- Comment #18 from Stefan Seyfried <seife@novell.slipkontur.de> --- note: I'm on vacation for the next two weeks, so answers might take longer than usual... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c21 --- Comment #21 from Stefan Seyfried <seife@novell.slipkontur.de> --- /var/log/journal does exist: mixi:~ # ls -l /var/log/journal/ total 0 drwxr-sr-x 1 root systemd-journal 15868 Jul 29 16:14 5acde102e5594ff3bc6496cb06b393f0 mixi:~ # du -sh /var/log/journal/ 577M /var/log/journal/ mixi:~ # df -hT /var/log/journal/ Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/system-root btrfs 100G 20G 78G 20% /var mixi:~ # ls -lrt /var/log/journal/5acde102e5594ff3bc6496cb06b393f0/|tail -3 -rw-r-----+ 1 root systemd-journal 8388608 Jul 29 16:14 user-10329@a3038c45f00446faa549a932c744c403-000000000005fb58-00061e36a70a8c10.journal -rw-r----- 1 root systemd-journal 33554432 Aug 20 20:54 system.journal -rw-r-----+ 1 root systemd-journal 16777216 Aug 20 20:54 user-10329.journal mixi:~ # lsof /run/systemd/journal/io.systemd.journal lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/10329/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.portal file system /run/user/10329/doc Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd-j 206 root 9u unix 0xffff888b4195f400 0t0 1240 /run/systemd/journal/io.systemd.journal type=STREAM (LISTEN) journalctl --flush results in a journal message: Sep 01 20:47:00 mixi systemd-journald[206]: Received client request to flush runtime journal. but no changes to anything in /var/log/journal I also tried restarting systemd-journald.service, but also no change. But a journalctl --flush afterwards then moved on to the persistent storage: Sep 01 20:50:24 mixi systemd-journald[206]: Journal stopped Sep 01 20:50:24 mixi systemd-journald[206]: Received SIGTERM from PID 1 (n/a). Sep 01 20:50:24 mixi systemd[1]: Stopping Journal Service... Sep 01 20:50:24 mixi systemd[1]: systemd-journald.service: Deactivated successfully. Sep 01 20:50:24 mixi systemd[1]: Stopped Journal Service. Sep 01 20:50:24 mixi systemd[1]: run-credentials-systemd\x2djournald.service.mount: Deactivated successfully. Sep 01 20:50:24 mixi systemd[1]: Starting Journal Service... Sep 01 20:50:24 mixi systemd-journald[4175]: 36 unknown file descriptors passed, closing. Sep 01 20:50:24 mixi systemd-journald[4175]: Collecting audit messages is disabled. Sep 01 20:50:24 mixi systemd-journald[4175]: Journal started Sep 01 20:50:24 mixi systemd-journald[4175]: Runtime Journal (/run/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 8M, max 314.9M, 306.9M free. Sep 01 20:50:24 mixi systemd[1]: Started Journal Service. Sep 01 20:51:21 mixi systemd-journald[4175]: Time spent on flushing to /var/log/journal/5acde102e5594ff3bc6496cb06b393f0 is 144.629ms for 2131 entries. Before restart, the /proc/<pid-of-jounrald>/exe link was pointing to /lib/systemd/systemd-journald (deleted), now it is pointing to /usr/lib/systemd/systemd-journald. My guess is still, the "handover" from initramfs to installed system (with a restart of journald?) is not working as intended and so for me the journald from initramfs is still running? But I have no real knowledge how this is supposed to work anyway, so I might be totally wrong here. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c23 --- Comment #23 from Stefan Seyfried <seife@novell.slipkontur.de> --- both booting with "init=/bin/bash" and a normal boot, pid 2 is "kthreadd" which looks pretty normal because the first thing the kernel needs to do is initialize its threading infrastructure. mixi:~ # ps 2 PID TTY STAT TIME COMMAND 2 ? S 0:00 [kthreadd] It is maybe also normal that a kernel thread can not be handled exactly the same as a userspace process and thus the "invalid argument"s are probably to be expected. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c25 --- Comment #25 from Stefan Seyfried <seife@novell.slipkontur.de> --- Back from vacation, but not really arrived mentally ;) I'll try the pidfd program in the next days, and I'll also try booting with an older kernel, because I noticed the failure started with 6.11.0-rc4 while the last working journal was with 6.11.0-rc3. Maybe something in the kernel changed / broke which affects the switch from initrd to installed system. This would also explain why everyone else running tumbleweed with "normal" kernels (not Kernel:HEAD) does not see this. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c26 --- Comment #26 from Stefan Seyfried <seife@novell.slipkontur.de> --- I just did reboot with kernel-vanilla 6.10.5-1-vanilla and it worked fine. Rebooting into 6.11.0-rc5-2 from Kernel:HEAD (but not up to date) broke again => IT IS A KERNEL PROBLEM!! ;-) I'm now zypper dup'ing to current tumbleweed + kernel:head 6.11-rc7, but I'm pretty sure we can send this bug to the kernel developers. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c27 --- Comment #27 from Stefan Seyfried <seife@novell.slipkontur.de> --- It works with kernel 6.11-rc7: mixi:~ # journalctl --list-boots |tail -5 -4 d131d91a089e4de6ba71c982e7a97167 Sun 2024-08-18 14:19:38 CEST Tue 2024-08-20 20:54:57 CEST -3 3b110d9ba0624a91bc0978c5f37624d8 Sun 2024-09-01 20:42:33 CEST Sun 2024-09-01 21:12:08 CEST -2 d9313ac7f9bf4203bc2d34b301beb1cb Thu 2024-09-12 12:01:36 CEST Thu 2024-09-12 12:02:50 CEST -1 0b856a821c6c4c289cd4539f0b4db54d Thu 2024-09-12 12:20:22 CEST Thu 2024-09-12 12:25:13 CEST 0 0bc0708564cf47a391bdf4beca5f4c92 Thu 2024-09-12 12:25:33 CEST Thu 2024-09-12 12:26:27 CEST mixi:~ # last reboot|head -5 reboot system boot 6.11.0-rc7-1.g56 Thu Sep 12 12:25 - still running reboot system boot 6.11.0-rc7-1.g56 Thu Sep 12 12:20 - 12:25 (00:04) reboot system boot 6.11.0-rc5-2.g2b Thu Sep 12 12:03 - 12:19 (00:16) reboot system boot 6.10.5-1-vanilla Thu Sep 12 12:01 - 12:02 (00:01) reboot system boot 6.11.0-rc5-2.g2b Wed Sep 11 18:33 - 12:01 (17:28) Boot entry -2 is from 6.10.5-vanilla, boot entry -1 from 6.11.0-rc7, the subsequent boot of 6.11.0-rc5 got ignored again. Looks like someone else complained to kernel developers already ;-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229721 https://bugzilla.suse.com/show_bug.cgi?id=1229721#c28 --- Comment #28 from Stefan Seyfried <seife@novell.slipkontur.de> --- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... this revert probably was the one that fixed this. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com