<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Journald can cause an endless loop" href="https://bugs.freedesktop.org/show_bug.cgi?id=76886#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Journald can cause an endless loop" href="https://bugs.freedesktop.org/show_bug.cgi?id=76886">bug 76886</a> from <a class="email" href="mailto:aospan@netup.ru" title="Abylay Ospan <aospan@netup.ru>"> Abylay Ospan</a> <pre>I observe same infinite loop. systemd-journald read following: p=7,5120,282337378,-;power_supply AC: prop ONLINE=1 SUBSYSTEM=power_supply DEVICE=+power_supply:AC and then read '/sys/class/power_supply/AC/uevent' again which cause above message again => infinite loop (100% CPU usage by systemd-journald). If this kernel bug do we need to send bug report/patch to kernel ? For now I have disabled 'CONFIG_POWER_SUPPLY_DEBUG'. For me this 'fix' is ok (I don't need this debug). Here is backtrace: /dev/kmsg buffer overrun, some messages lost. Breakpoint 1, device_read_uevent_file (device=0x5555555caf20) at src/libsystemd/sd-device/sd-device.c:482 482 in src/libsystemd/sd-device/sd-device.c (gdb) bt #0 device_read_uevent_file (device=0x5555555caf20) at src/libsystemd/sd-device/sd-device.c:482 #1 0x0000555555587368 in sd_device_get_devname (device=0x5555555caf20, devname=0x7fffffffb8d0) at src/libsystemd/sd-device/sd-device.c:933 #2 0x0000555555581b14 in udev_device_get_devnode (udev_device=0x5555555cacb0) at src/libudev/libudev-device.c:677 #3 0x000055555555be2d in dev_kmsg_record (s=0x7fffffffe450, p=0x7fffffffc2c3 "power_supply AC: prop ONLINE=1", l=0) at src/journal/journald-kmsg.c:228 #4 0x000055555555c834 in server_read_dev_kmsg (s=0x7fffffffe450) at src/journal/journald-kmsg.c:348 #5 0x000055555555cb13 in dispatch_dev_kmsg (es=0x5555555c96b0, fd=7, revents=1, userdata=0x7fffffffe450) at src/journal/journald-kmsg.c:390 #6 0x000055555558d0c1 in source_dispatch (s=0x5555555c96b0) at src/libsystemd/sd-event/sd-event.c:2114 #7 0x000055555558e4f8 in sd_event_dispatch (e=0x5555555c91e0) at src/libsystemd/sd-event/sd-event.c:2471 #8 0x000055555558e670 in sd_event_run (e=0x5555555c91e0, timeout=18446744073709551615) at src/libsystemd/sd-event/sd-event.c:2499 #9 0x000055555555ae0d in main (argc=1, argv=0x7fffffffe768) at src/journal/journald.c:106 (gdb) frame 3 #3 0x000055555555be2d in dev_kmsg_record (s=0x7fffffffe450, p=0x7fffffffc2c3 "power_supply AC: prop ONLINE=1", l=0) at src/journal/journald-kmsg.c:228 228 src/journal/journald-kmsg.c: No such file or directory. (gdb) p kernel_device $1 = 0x5555555ca5ef "+power_supply:AC"</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>