Bug 31482

Summary: Stop process is delayed because of watchdog
Product: Mageia Reporter: papoteur <yvesbrungard>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: fri, ghibomgx
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Journal when rebooting

Description papoteur 2023-02-01 09:16:35 CET
Description of problem:
When halting, target 'reboot' is reached, but the process wait some seconds (one minute?)
At end, the following message is displayed and the halting process continues:
watchdog: watchdog0: watchdog didn't stop!
dracut warning: killing all remaining processes

How reproducible:
Always

Steps to Reproduce:
1. Start Mageia
2. Stop or reboot Mageia

uname -a
Linux YZenbook.home 5.15.88-desktop-1.mga8 #1 SMP Sat Jan 14 15:00:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
papoteur 2023-02-01 09:17:03 CET

Summary: Stop process is retained because of watchdog => Stop process is delayed because of watchdog

Comment 1 Morgan Leijström 2023-02-01 10:35:39 CET
Could you attach a part of journal from shutting down?

for example given by
journalclt -b-1 --since <the time seconds when you started shutdown>

CC: (none) => fri

Comment 2 papoteur 2023-02-01 10:57:30 CET
Created attachment 13669 [details]
Journal when rebooting
Comment 3 Morgan Leijström 2023-02-01 14:12:02 CET
That watchdog line I see also on my machines, and have for... years?

Grepping on watchdog i get three lines from every reboot:

$ journalctl -b-1 | grep watchdog
feb 01 11:55:25 svarten.tribun kernel: watchdog: watchdog0: watchdog did not stop!
feb 01 11:55:25 svarten.tribun systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
feb 01 11:55:25 svarten.tribun systemd[1]: Set hardware watchdog to 10min.

Must be something else.
Comment 4 papoteur 2023-02-01 14:50:21 CET
Replaying the film, I see at last:
dracut Warning: Unmounted /oldroot
Rebooting
Nothing more
Morgan Leijström 2023-02-01 14:52:24 CET

Assignee: bugsquad => kernel

Comment 5 papoteur 2023-02-01 15:00:18 CET
I use a SSD with luks encryption (/ and /home), without LVM.
Comment 6 papoteur 2023-02-04 13:50:47 CET
Today, while rebooting, I got:
systemd-shutdown, waiting for process osspd
Comment 7 Giuseppe Ghibò 2023-02-04 14:00:36 CET
You might uninstall the 'ossp' package. It's not used anymore. IMHO shouldn't be installed by default. It's triggered by some dep during the installation or draksound, not sure (need to be reviewed where it comes from). Anyway I got the stop delay even without ossp.

CC: (none) => ghibomgx

Comment 8 papoteur 2023-02-04 14:26:43 CET
In systemd, osspd.service is not enabled at start. Thus something starts it. speechdispatcher?
Shouldn't it be withdrawn from cauldron?
Comment 9 Giuseppe Ghibò 2023-02-04 14:41:20 CET
I got problems with ossp since mga7, I had also a patchset for the package somewhere which includes also some patch from deb, and also some fix for snprintf array size fixing, that I never pushed because even with those fixes doesn't change anything. But it's not the direct cause of the stop delay, at least in this round, because even if you remove it, you still got the delay.

It's used for an old compatibility layer with the Open Sound System which was the linux sound system before alsa, but it's rarely used since most applications uses alsa now. For me, since it compiles it can stay in the distro, you never now (you might have for instance some very ancient software or game to use with even outside mageia tree), but IMHO shouldn't be triggered to be installed by default anyway (or during an update).