Dear Maintainer, my system ins't able to power off and requires a long press of the power button. While i wai until it NOT turn off on the screen i read: " ........................... [ OK ] Deactivated swap dev-nvmeon1p7.swap - /dev/nvme0n1p7. OK Deactivated swap dev-disk-by\x2duuid-15733a89\x2dbb55\x2d45ff\x2d8775\x2dc1bdf15340dd.swap [OK] Reached target umount.target - Unmount All Filesystems. [OK] Reached target final.target Late Shutdown Services. [ OK ] Finished systemd-poweroff.service System Power Off. [ OK ] Reached target poweroff.target System Power Off. - /dev/disk/by-path/pci-0000: [ 3099.851551] systemd-journald [434]: Failed to send WATCHDOG=1 notification message: Connection refused systemd-journald [434]: Failed to send WATCHDOG=1 notification message: Connection refused /dev/disk/by-uuid/1573 [ 3179.052336] systemd-journald [434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected systemd-journald [434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected " On my old lenovo G580 i don't get this error and the laptop turns off correctly. I can give to you more logs if you need them. Regards Attilio
Control: tags -1 moreinfo power button. While i wai until it NOT turn off on the screen i read: Deactivated swap dev-disk-by\x2duuid- 15733a89\x2dbb55\x2d45ff\x2d8775\x2dc1bdf15340dd.swap notification message: Connection refused systemd-journald [434]: Failed to send WATCHDOG=1 notification message: Connection refused notification message: Transport endpoint is not connected systemd- journald [434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected correctly. This is unactionable due to lack of crucial information. 1) Why does it mention kernel 6.16? Does the problem not appear with 6.12.x? 2) Enable debug logs for both the kernel and systemd and upload to a pastebin the full log during shutdown and link it here
I hope to give to you some useful infos. I use Debian testing but i manually install latest kernel from experimental. The kernel 6.12 worked perfectly and the same happens with 6.15.6. All works, except for the 6.16 version. Some logs. boot, useful(?): https://pastebin.com/jVaJZKyh dmesg: https://pastebin.com/cdu9VekD journalctrl, today, 11.4Mb (hard power off at 11AM and 10 PM): [https://res.public.onecdn.static.microsoft/assets/mail/file-icon/png/txt_16x16.png]journalcrtl-onlytoday.txt<https://1drv.ms/t/c/4b9e8337825e1260/EYmO-FP1DH5HgA2kbdsykogBtLE6CqMu5zG9iAoRQDBbew?e=C1O9XJ> Regards Attilio
Control: retitle -1 system doesn't poweroff with kernel 6.16 Control: reassign -1 src:linux 6.16-1~exp1 experimental. The kernel 6.12 worked perfectly and the same happens with 6.15.6. All works, except for the 6.16 version. [https://res.public.onecdn.static.microsoft/assets/mail/file-icon/png/txt_16x16.png]journalcrtl-onlytoday.txt <https://1drv.ms/t/c/4b9e8337825e1260/EYmO-FP1DH5HgA2kbdsykogBtLE6CqMu5zG9iAoRQDBbew?e=C1O9XJ Ok that means it's a regression in kernel 6.16, reassigning to the kernel package for further triaging.
Hi, i don't know if it is relevant but from dmesg: [ 2.710024] ------------[ cut here ]------------ [ 2.710025] kernel BUG at lib/list_debug.c:35! [ 2.710036] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 2.710051] CPU: 3 UID: 0 PID: 514 Comm: (udev-worker) Not tainted 6.16-amd64 #1 PREEMPT(lazy) Debian 6.16-1~exp1 [ 2.710065] Hardware name: ASUS System Product Name/TUF GAMING B560M-PLUS WIFI, BIOS 2001 02/02/2023 [ 2.710078] RIP: 0010:__list_add_valid_or_report.cold+0x15/0x33 [ 2.710090] Code: 44 fd ff e9 d6 6c 78 00 4c 89 e6 bf 11 00 00 00 e8 56 f7 ff ff 48 89 f2 48 89 d9 48 89 fe 48 c7 c7 60 f8 96 86 e8 01 44 fd ff <0f> 0b 48 c7 c7 88 f7 96 86 e8 f3 43 fd ff 0f 0b 48 c7 c7 60 f7 96 [ 2.710113] RSP: 0018:ffffd06ec1b8b878 EFLAGS: 00010246 [ 2.710122] RAX: 0000000000000058 RBX: ffffffffc0dbe720 RCX: 0000000000000000 [ 2.710132] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8e69afadce00 [ 2.710142] RBP: 0000000000400140 R08: 0000000000000000 R09: 0000000000000000 [ 2.710152] R10: 00aaaaaa00aaaaaa R11: 00aaaaaa00aaaaaa R12: ffffffffc0dbe720 [ 2.710161] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 2.710171] FS: 00007fcc2123e980(0000) GS:ffff8e6a27e88000(0000) knlGS:0000000000000000 [ 2.710182] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.710191] CR2: 00007fcc202e5771 CR3: 0000000120cc8005 CR4: 0000000000770ef0 [ 2.710201] PKRU: 55555554 Regards Attilio
Nothing changed with the 6.16.1 kernel. Regards Attilio
The kernel 6.16.3+deb14 (from unstable) didn't solve my shutdown problem. Same bug unfixed, this a screenshot of my monitor while my pc boots: https://i.postimg.cc/brV3n3m1/photo-5875102605221415931-y.jpg [https://i.postimg.cc/brV3n3m1/photo-5875102605221415931-y.jpg] and another one at the console login: https://i.postimg.cc/Hnk6jf9p/photo-5875102605221415930-y.jpg [https://i.postimg.cc/Hnk6jf9p/photo-5875102605221415930-y.jpg] This one could be useless. Main Linux kernel devs suggest to contact devs of distro first "Please use your distribution's bug tracking tools". This is what i did. Regards Attilio
I found a bug opened by another user with an Asus MB, with my same issue (it is related to the asus_wmi module): https://bugzilla.kernel.org/show_bug.cgi?id=220473 https://bugzilla.opensuse.org/show_bug.cgi?id=1246924#c14 This is the solutive comment: https://bugzilla.opensuse.org/show_bug.cgi?id=1246924#c21 and the patch: https://bugzilla.opensuse.org/attachment.cgi?id=885249&action=diff The same user suggests a workaround: "......blacklisted the 'asus_wmi' and the 'asus_nb_wmi' modules through the '/etc/modprobe.d/blacklist.conf'...." ...the workaround works!!!!!! until the kernel will be patched. I think/hope this issue is fixed with kernel >6.16.3. Regards Attilio
Hi Attilio Can you please try the attached patch with the procedure described in https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4 and report back if that fixes your problem? Regards, Salvatore
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4 Hi Salvatore, I've got an Asus ROG STRIX Z790-F GAMING WIFI motherboard, and with kernel 6.16.3 I've been seeing the system hang every now and then at boot, and almost always at shutdown. While waiting to hear back from the OP, I gave the patch a try myself. After a few tests, it looks like the hangs are gone. Best regards.
Hi, Thanks for confirming your part, I will wait a bit for an ack as well from the reporter. Regards, Salvatore
Of course! I'd also like to gently remind the OP to remove both asus_wmi and asus_nb_wmi from the blacklist to ensure the testing is accurate.