You are not logged in.

Pages: 1

#1 2023-06-23 23:57:47

SunBlade
Member
From: at home
Registered: 2023-02-18
Posts: 27

[SOLVED] watchdog error on shutdown/reboot

Hi,
most of my shutdowns and reboots take ages to complete. until now i thought that is because i run btrfs with forced max compression and bees. but upon closer inspection of my logs i am not so sure anymore.

every single shutdown/reboot has some kind of watchdog error, something like this for example:

Jun 23 23:34:00 systemd[1]: Reached target System Shutdown.
Jun 23 23:34:00 systemd[1]: Reached target Late Shutdown Services.
Jun 23 23:34:00 systemd[1]: systemd-poweroff.service: Deactivated successfully.
Jun 23 23:34:00 systemd[1]: Finished System Power Off.
Jun 23 23:34:00 systemd[1]: Reached target System Power Off.
Jun 23 23:34:00 systemd[1]: Shutting down.
Jun 23 23:34:00 systemd-shutdown[1]: Syncing filesystems and block devices.
Jun 23 23:35:28 systemd-journald[498]: Failed to send WATCHDOG=1 notification message: Connection refused
Jun 23 23:36:04 kernel: INFO: task (sd-sync):2516 blocked for more than 122 seconds.
Jun 23 23:36:04 kernel:       Not tainted 6.3.9-zen1-1-zen #1
Jun 23 23:36:04 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 23 23:36:04 kernel: task:(sd-sync)       state:D stack:0     pid:2516  ppid:1      flags:0x00000002
Jun 23 23:36:04 kernel: Call Trace:
Jun 23 23:36:04 kernel:  <TASK>
Jun 23 23:36:04 kernel:  __schedule+0xc18/0x1620
Jun 23 23:36:04 kernel:  ? bdi_split_work_to_wbs+0x1b8/0x400
Jun 23 23:36:04 kernel:  ? filemap_map_pages+0x15f/0x640
Jun 23 23:36:04 kernel:  schedule+0x5e/0xd0
Jun 23 23:36:04 kernel:  sync_inodes_sb+0x311/0x350
Jun 23 23:36:04 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jun 23 23:36:04 kernel:  ? __pfx_sync_inodes_one_sb+0x10/0x10
Jun 23 23:36:04 kernel:  iterate_supers+0x8c/0xf0
Jun 23 23:36:04 kernel:  __do_sys_sync+0x44/0xb0
Jun 23 23:36:04 kernel:  do_syscall_64+0x60/0x90
Jun 23 23:36:04 kernel:  ? do_user_addr_fault+0x1e9/0x740
Jun 23 23:36:04 kernel:  ? exc_page_fault+0x7c/0x180
Jun 23 23:36:04 kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jun 23 23:36:04 kernel: RIP: 0033:0x7fec92b166cb
Jun 23 23:36:04 kernel: RSP: 002b:00007ffc0a87be88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
Jun 23 23:36:04 kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fec92b166cb
Jun 23 23:36:04 kernel: RDX: 00007ffc0a87becc RSI: 00000000ffffffff RDI: 0000000000000003
Jun 23 23:36:04 kernel: RBP: 00007ffc0a87bfa0 R08: 0000000000000000 R09: 0000000000000000
Jun 23 23:36:04 kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
Jun 23 23:36:04 kernel: R13: 0000000000000000 R14: 00007ffc0a87dfd4 R15: 000055b208edb838
Jun 23 23:36:04 kernel:  </TASK>
Jun 23 23:37:08 systemd-journald[498]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jun 23 23:38:07 kernel: INFO: task kworker/25:2:734 blocked for more than 122 seconds.
Jun 23 23:38:07 kernel:       Not tainted 6.3.9-zen1-1-zen #1
Jun 23 23:38:07 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 23 23:38:07 systemd-journald[498]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jun 23 23:38:07 kernel: task:kworker/25:2    state:D stack:0     pid:734   ppid:2      flags:0x00004000
Jun 23 23:38:07 kernel: Workqueue: inode_switch_wbs inode_switch_wbs_work_fn
Jun 23 23:38:07 kernel: Call Trace:
Jun 23 23:38:07 kernel:  <TASK>
Jun 23 23:38:07 kernel:  __schedule+0xc18/0x1620
Jun 23 23:38:07 kernel:  schedule_preempt_disabled+0x65/0xe0
Jun 23 23:38:07 kernel:  rwsem_down_read_slowpath+0x18b/0x560
Jun 23 23:38:07 kernel:  down_read+0x48/0xb0
Jun 23 23:38:07 kernel:  inode_switch_wbs_work_fn+0x61/0x7f0
Jun 23 23:38:07 kernel:  ? __switch_to_asm+0x3e/0x80
Jun 23 23:38:07 kernel:  ? finish_task_switch.isra.0+0x94/0x2f0
Jun 23 23:38:07 kernel:  ? __schedule+0xc20/0x1620
Jun 23 23:38:07 kernel:  process_one_work+0x252/0x460
Jun 23 23:38:07 kernel:  worker_thread+0x55/0x4f0
Jun 23 23:38:07 kernel:  ? __pfx_worker_thread+0x10/0x10
Jun 23 23:38:07 kernel:  kthread+0xde/0x110
Jun 23 23:38:07 kernel:  ? __pfx_kthread+0x10/0x10
Jun 23 23:38:07 kernel:  ret_from_fork+0x2c/0x50
Jun 23 23:38:07 kernel:  </TASK>
Jun 23 23:38:07 kernel: INFO: task (sd-sync):2516 blocked for more than 245 seconds.
Jun 23 23:38:07 kernel:       Not tainted 6.3.9-zen1-1-zen #1
Jun 23 23:38:07 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 23 23:38:07 kernel: task:(sd-sync)       state:D stack:0     pid:2516  ppid:1      flags:0x00000002
Jun 23 23:38:07 kernel: Call Trace:
Jun 23 23:38:07 kernel:  <TASK>
Jun 23 23:38:07 kernel:  __schedule+0xc18/0x1620
Jun 23 23:38:07 kernel:  ? bdi_split_work_to_wbs+0x1b8/0x400
Jun 23 23:38:07 kernel:  ? filemap_map_pages+0x15f/0x640
Jun 23 23:38:07 kernel:  schedule+0x5e/0xd0
Jun 23 23:38:07 kernel:  sync_inodes_sb+0x311/0x350
Jun 23 23:38:07 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jun 23 23:38:07 kernel:  ? __pfx_sync_inodes_one_sb+0x10/0x10
Jun 23 23:38:07 kernel:  iterate_supers+0x8c/0xf0
Jun 23 23:38:07 kernel:  __do_sys_sync+0x44/0xb0
Jun 23 23:38:07 kernel:  do_syscall_64+0x60/0x90
Jun 23 23:38:07 kernel:  ? do_user_addr_fault+0x1e9/0x740
Jun 23 23:38:07 kernel:  ? exc_page_fault+0x7c/0x180
Jun 23 23:38:07 kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jun 23 23:38:07 kernel: RIP: 0033:0x7fec92b166cb
Jun 23 23:38:07 kernel: RSP: 002b:00007ffc0a87be88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
Jun 23 23:38:07 kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fec92b166cb
Jun 23 23:38:07 kernel: RDX: 00007ffc0a87becc RSI: 00000000ffffffff RDI: 0000000000000003
Jun 23 23:38:07 kernel: RBP: 00007ffc0a87bfa0 R08: 0000000000000000 R09: 0000000000000000
Jun 23 23:38:07 kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
Jun 23 23:38:07 kernel: R13: 0000000000000000 R14: 00007ffc0a87dfd4 R15: 000055b208edb838
Jun 23 23:38:07 kernel:  </TASK>
Jun 23 23:38:22 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jun 23 23:38:22 systemd-journald[498]: Received SIGTERM from PID 1 (systemd-shutdow).
Jun 23 23:38:22 systemd-journald[498]: Journal stopped

and even the fast shutdowns/reboots have this error:

Jun 23 11:58:35 systemd[1]: Reached target System Shutdown.
Jun 23 11:58:35 systemd[1]: Reached target Late Shutdown Services.
Jun 23 11:58:35 systemd[1]: systemd-reboot.service: Deactivated successfully.
Jun 23 11:58:35 systemd[1]: Finished System Reboot.
Jun 23 11:58:35 systemd[1]: Reached target System Reboot.
Jun 23 11:58:35 systemd[1]: Shutting down.
Jun 23 11:58:35 systemd[1]: Using hardware watchdog 'SP5100 TCO timer', version 0, device /dev/watchdog0
Jun 23 11:58:35 systemd[1]: Watchdog running with a timeout of 10min.
Jun 23 11:58:35 kernel: watchdog: watchdog0: watchdog did not stop!
Jun 23 11:58:35 systemd-shutdown[1]: Using hardware watchdog 'SP5100 TCO timer', version 0, device /dev/watchdog0
Jun 23 11:58:35 systemd-shutdown[1]: Watchdog running with a timeout of 10min.
Jun 23 11:58:35 systemd-shutdown[1]: Syncing filesystems and block devices.
Jun 23 11:58:38 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jun 23 11:58:38 systemd-journald[496]: Received SIGTERM from PID 1 (systemd-shutdow).
Jun 23 11:58:38 systemd-journald[496]: Journal stopped

my previous system iteration did not have this problem. changes i made since then (aprox. 4 months ago):
- BIOS update
- fiddling with BIOS options, especially disabling tpm and enabling virtualization
- reformatting everything except the ESP to btrfs
- installing and configuring arch from scratch, no config from my old iteration was used

how do i narrow down the problem?

Last edited by SunBlade (2023-08-15 14:06:45)

Live your life, you got only one.

Offline

#2 2023-06-24 06:29:52

Ferdinand
Member
From: Norway
Registered: 2020-01-02
Posts: 338

Re: [SOLVED] watchdog error on shutdown/reboot

It may of course be that your BIOS update changed something, but those watchdogs are a bit unwieldy anyway.
Basically, they're there to detect if your system stops functioning, and try to get it up and running again.
Good for things that are supposed to just keep running, but not overly useful on a desktop client.

I have tried disabling them, but somehow I still have some nagging me when it's shut down time tongue

There's some info in the Wiki, and the links to more information contains some, well, more information smile
https://wiki.archlinux.org/title/Improv … #Watchdogs

Xfce ⬩ No CSD ⬩ Arch Forum Readme

Offline

#3 2023-06-27 17:07:51

SunBlade
Member
From: at home
Registered: 2023-02-18
Posts: 27

Re: [SOLVED] watchdog error on shutdown/reboot

Ferdinand wrote:

I have tried disabling them, but somehow I still have some nagging me when it's shut down time tongue

the nowatchdog boot option seems to only disable the hung kernel task warning. but after also blacklisting my hardware TCO in modprobe, no more errors have shown up on shutdown/reboot.

shutdown/reboot times have vastly improved, but the fs sync still hangs from 3 secs up to 1 minute.

Jun 27 17:38:22 systemd[1]: Stopped target Swaps.
Jun 27 17:38:22 systemd[1]: Reached target System Shutdown.
Jun 27 17:38:22 systemd[1]: Reached target Unmount All Filesystems.
Jun 27 17:38:22 systemd[1]: Reached target Late Shutdown Services.
Jun 27 17:38:22 systemd[1]: systemd-poweroff.service: Deactivated successfully.
Jun 27 17:38:22 systemd[1]: Finished System Power Off.
Jun 27 17:38:22 systemd[1]: Reached target System Power Off.
Jun 27 17:38:22 systemd[1]: Shutting down.
Jun 27 17:38:22 systemd-shutdown[1]: Syncing filesystems and block devices.
Jun 27 17:38:43 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jun 27 17:38:43 systemd-journald[498]: Journal stopped

it seems like the watchdogs created a new problem by trying to fix something that was intentional.
i think one of my btrfs mount options "rw,noatime,compress-force=zstd:15,ssd_spread,discard=async,space_cache=v2,subvol=/root" causes this delay.
will a "sudo fsync" sync my SSDs in the same way systemd-shutdown does?

Live your life, you got only one.

Offline

#4 2023-06-28 16:52:54

Ferdinand
Member
From: Norway
Registered: 2020-01-02
Posts: 338

Re: [SOLVED] watchdog error on shutdown/reboot

I think the command to execute if you want to sync cached writes to persistent storage is sync - not fsync?

Anyway, I'm afraid I don't get the long sync time - I think that should be done and over with in less than a second.

Xfce ⬩ No CSD ⬩ Arch Forum Readme

Offline

#5 2023-07-03 11:04:31

SunBlade
Member
From: at home
Registered: 2023-02-18
Posts: 27

Re: [SOLVED] watchdog error on shutdown/reboot

Ferdinand wrote:

I think the command to execute if you want to sync cached writes to persistent storage is sync - not fsync?

yes, you are right. doing a "sudo sync" before hitting the shutdown button in kde does not seem to change anything.

SunBlade wrote:

the nowatchdog boot option seems to only disable the hung kernel task warning. but after also blacklisting my hardware TCO in modprobe, no more errors have shown up on shutdown/reboot.

scratch that. i still get those errors, but at a distinctly lowered rate.

Jul 03 11:56:55 systemd[1]: Reached target System Shutdown.
Jul 03 11:56:55 systemd[1]: Reached target Unmount All Filesystems.
Jul 03 11:56:55 systemd[1]: Reached target Late Shutdown Services.
Jul 03 11:56:55 systemd[1]: systemd-poweroff.service: Deactivated successfully.
Jul 03 11:56:55 systemd[1]: Finished System Power Off.
Jul 03 11:56:55 systemd[1]: Reached target System Power Off.
Jul 03 11:56:55 systemd[1]: Shutting down.
Jul 03 11:56:55 systemd-shutdown[1]: Syncing filesystems and block devices.
Jul 03 11:58:12 systemd-journald[489]: Failed to send WATCHDOG=1 notification message: Connection refused
Jul 03 11:59:05 kernel: INFO: task kworker/12:2:517 blocked for more than 122 seconds.
Jul 03 11:59:05 kernel:       Not tainted 6.4.1-zen1-1-zen #1
Jul 03 11:59:05 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 03 11:59:05 kernel: task:kworker/12:2    state:D stack:0     pid:517   ppid:2      flags:0x00004000
Jul 03 11:59:05 kernel: Workqueue: inode_switch_wbs inode_switch_wbs_work_fn
Jul 03 11:59:05 kernel: Call Trace:
Jul 03 11:59:05 kernel:  <TASK>
Jul 03 11:59:05 kernel:  __schedule+0xca6/0x1950
Jul 03 11:59:05 kernel:  schedule_preempt_disabled+0x65/0xe0
Jul 03 11:59:05 kernel:  rwsem_down_read_slowpath+0x18b/0x560
Jul 03 11:59:05 kernel:  down_read+0x48/0xb0
Jul 03 11:59:05 kernel:  inode_switch_wbs_work_fn+0x61/0x7f0
Jul 03 11:59:05 kernel:  ? __switch_to_asm+0x3e/0x80
Jul 03 11:59:05 kernel:  ? finish_task_switch.isra.0+0x94/0x2f0
Jul 03 11:59:05 kernel:  ? __schedule+0xcae/0x1950
Jul 03 11:59:05 kernel:  process_one_work+0x252/0x460
Jul 03 11:59:05 kernel:  worker_thread+0x55/0x4f0
Jul 03 11:59:05 kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 03 11:59:05 kernel:  kthread+0xe8/0x120
Jul 03 11:59:05 kernel:  ? __pfx_kthread+0x10/0x10
Jul 03 11:59:05 kernel:  ret_from_fork+0x2c/0x50
Jul 03 11:59:05 kernel:  </TASK>
Jul 03 11:59:05 kernel: INFO: task (sd-sync):30467 blocked for more than 122 seconds.
Jul 03 11:59:05 kernel:       Not tainted 6.4.1-zen1-1-zen #1
Jul 03 11:59:05 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 03 11:59:05 kernel: task:(sd-sync)       state:D stack:0     pid:30467 ppid:1      flags:0x00000002
Jul 03 11:59:05 kernel: Call Trace:
Jul 03 11:59:05 kernel:  <TASK>
Jul 03 11:59:05 kernel:  __schedule+0xca6/0x1950
Jul 03 11:59:05 kernel:  ? bdi_split_work_to_wbs+0x1b8/0x400
Jul 03 11:59:05 kernel:  ? filemap_map_pages+0x162/0x640
Jul 03 11:59:05 kernel:  schedule+0x5e/0xd0
Jul 03 11:59:05 kernel:  sync_inodes_sb+0x311/0x350
Jul 03 11:59:05 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jul 03 11:59:05 kernel:  ? __pfx_sync_inodes_one_sb+0x10/0x10
Jul 03 11:59:05 kernel:  iterate_supers+0x8c/0xf0
Jul 03 11:59:05 kernel:  __do_sys_sync+0x44/0xb0
Jul 03 11:59:05 kernel:  do_syscall_64+0x60/0x90
Jul 03 11:59:05 kernel:  ? do_user_addr_fault+0x3c3/0x9e0
Jul 03 11:59:05 kernel:  ? exc_page_fault+0x7f/0x180
Jul 03 11:59:05 kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 03 11:59:05 kernel: RIP: 0033:0x7f8db8cf16cb
Jul 03 11:59:05 kernel: RSP: 002b:00007ffdc18774d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
Jul 03 11:59:05 kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8db8cf16cb
Jul 03 11:59:05 kernel: RDX: 00007ffdc187751c RSI: 00000000ffffffff RDI: 0000000000000003
Jul 03 11:59:05 kernel: RBP: 00007ffdc18775f0 R08: 0000000000000000 R09: 0000000000000000
Jul 03 11:59:05 kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
Jul 03 11:59:05 kernel: R13: 0000000000000000 R14: 00007ffdc1877fd4 R15: 0000556f8743f838
Jul 03 11:59:05 kernel:  </TASK>
Jul 03 12:00:12 systemd-journald[489]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jul 03 12:01:07 kernel: INFO: task kworker/12:2:517 blocked for more than 245 seconds.
Jul 03 12:01:07 kernel:       Not tainted 6.4.1-zen1-1-zen #1
Jul 03 12:01:07 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 03 12:01:07 systemd-journald[489]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jul 03 12:01:07 kernel: task:kworker/12:2    state:D stack:0     pid:517   ppid:2      flags:0x00004000
Jul 03 12:01:07 kernel: Workqueue: inode_switch_wbs inode_switch_wbs_work_fn
Jul 03 12:01:07 kernel: Call Trace:
Jul 03 12:01:07 kernel:  <TASK>
Jul 03 12:01:07 kernel:  __schedule+0xca6/0x1950
Jul 03 12:01:07 kernel:  schedule_preempt_disabled+0x65/0xe0
Jul 03 12:01:07 kernel:  rwsem_down_read_slowpath+0x18b/0x560
Jul 03 12:01:07 kernel:  down_read+0x48/0xb0
Jul 03 12:01:07 kernel:  inode_switch_wbs_work_fn+0x61/0x7f0
Jul 03 12:01:07 kernel:  ? __switch_to_asm+0x3e/0x80
Jul 03 12:01:07 kernel:  ? finish_task_switch.isra.0+0x94/0x2f0
Jul 03 12:01:07 kernel:  ? __schedule+0xcae/0x1950
Jul 03 12:01:07 kernel:  process_one_work+0x252/0x460
Jul 03 12:01:07 kernel:  worker_thread+0x55/0x4f0
Jul 03 12:01:07 kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 03 12:01:07 kernel:  kthread+0xe8/0x120
Jul 03 12:01:07 kernel:  ? __pfx_kthread+0x10/0x10
Jul 03 12:01:07 kernel:  ret_from_fork+0x2c/0x50
Jul 03 12:01:07 kernel:  </TASK>
Jul 03 12:01:07 kernel: INFO: task (sd-sync):30467 blocked for more than 245 seconds.
Jul 03 12:01:07 kernel:       Not tainted 6.4.1-zen1-1-zen #1
Jul 03 12:01:07 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 03 12:01:07 kernel: task:(sd-sync)       state:D stack:0     pid:30467 ppid:1      flags:0x00000002
Jul 03 12:01:07 kernel: Call Trace:
Jul 03 12:01:07 kernel:  <TASK>
Jul 03 12:01:07 kernel:  __schedule+0xca6/0x1950
Jul 03 12:01:07 kernel:  ? bdi_split_work_to_wbs+0x1b8/0x400
Jul 03 12:01:07 kernel:  ? filemap_map_pages+0x162/0x640
Jul 03 12:01:07 kernel:  schedule+0x5e/0xd0
Jul 03 12:01:07 kernel:  sync_inodes_sb+0x311/0x350
Jul 03 12:01:07 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jul 03 12:01:07 kernel:  ? __pfx_sync_inodes_one_sb+0x10/0x10
Jul 03 12:01:07 kernel:  iterate_supers+0x8c/0xf0
Jul 03 12:01:07 kernel:  __do_sys_sync+0x44/0xb0
Jul 03 12:01:07 kernel:  do_syscall_64+0x60/0x90
Jul 03 12:01:07 kernel:  ? do_user_addr_fault+0x3c3/0x9e0
Jul 03 12:01:07 kernel:  ? exc_page_fault+0x7f/0x180
Jul 03 12:01:07 kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 03 12:01:07 kernel: RIP: 0033:0x7f8db8cf16cb
Jul 03 12:01:07 kernel: RSP: 002b:00007ffdc18774d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
Jul 03 12:01:07 kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8db8cf16cb
Jul 03 12:01:07 kernel: RDX: 00007ffdc187751c RSI: 00000000ffffffff RDI: 0000000000000003
Jul 03 12:01:07 kernel: RBP: 00007ffdc18775f0 R08: 0000000000000000 R09: 0000000000000000
Jul 03 12:01:07 kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
Jul 03 12:01:07 kernel: R13: 0000000000000000 R14: 00007ffdc1877fd4 R15: 0000556f8743f838
Jul 03 12:01:07 kernel:  </TASK>
Jul 03 12:01:35 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jul 03 12:01:35 systemd-journald[489]: Received SIGTERM from PID 1 (systemd-shutdow).
Jul 03 12:01:35 systemd-journald[489]: Journal stopped

curiously that also means, the shutdown takes ages when those errors appear. however, i do not know if they are a symptom or the cause.

Live your life, you got only one.

Offline

#6 2023-08-15 14:05:25

SunBlade
Member
From: at home
Registered: 2023-02-18
Posts: 27

Re: [SOLVED] watchdog error on shutdown/reboot

for anyone who is still interested: i nailed down the problem to bees. turns out bees does not like my system setup (probably forced compression or snapper).

sometimes when i stop bees i notice high disk io for several minutes. system monitor shows that all that traffic is coming from btrfs kernel jobs. i assume those are compressing the bees database, which would stall unmount attempts at shutdown.

completely disabling bees has resulted in consistently lightning fast shutdowns for over a month now. and occasionally running duperemove to reclaim some diskspace is acceptable.

Live your life, you got only one.

Offline

Pages: 1

Board footer

Powered by FluxBB