How to disable reboot broadcast message?

Support
1 
Broadcast message from username@Desktop (Sun 1919-08-10 11:45:14 CST):

The system is going to reboot NOW!

[756.345947] watchdog: watchdog0: watchdog did not stop!
[756.472889] watchdog: watchdog0: watchdog did not stop!

Every time I reboot and found a message like this.

Is there any way to get rid of these messages?

Manjaro version: Testing Update 20220709
Kernel: 5.18.10-1-MANJARO x86_64

3

Ignore it

4 Likes
4

It needs to go away again.

5

from r/archlinux

It’s a systemd bug, you’re not supposed to get those broadcasts on a tty. Put mesg n in your ~/.bash_login (or whatever the equivalent is for your shell) as a temporary workaround.

6

First: which Watchdog do yo have?
==> lsmod | grep -e dog -e wdt -e tco
Then: blacklist it.
Example:

journalctl -p err -b
…
sp5100-tco sp5100-tco: Watchdog hardware is disabled
…

That requires /etc/modprobe.d/blacklist_tco.conf with content: blacklist sp5100_tco

sudo nano /etc/modprobe.d/blacklist_tco.conf

More: Reboot doesn't work? - #31 by Stagger_Lee - General system - EndeavourOS
or Watchdog did not stop

7 
>>> lsmod | grep -e dog -e wdt -e tco
iTCO_wdt               16384  0
intel_pmc_bxt          16384  1 iTCO_wdt
iTCO_vendor_support    16384  1 iTCO_wdt

journalctl -p err -b
Jul 10 23:18:52 ThinkPad kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Jul 10 23:18:52 ThinkPad kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
Jul 10 23:18:52 ThinkPad systemd-udevd[285]: could not read from '/sys/module/pcc_cpufreq/initstate': No such>
Jul 10 23:18:53 ThinkPad kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP>
Jul 10 23:18:55 ThinkPad kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 10 23:18:55 ThinkPad systemd[517]: Failed to start Update XDG user dir configuration.
Jul 10 23:19:02 ThinkPad kernel: ntfs3: Unknown parameter 'windows_names'
8

So do in terminal:
sudo nano /etc/modprobe.d/blacklist_tco.conf
contents: EDIT:

blacklist iTCO_wdt
blacklist iTCO_vendor_support

followed by saving the new created file with contents above and finally reboot. Thats all.

9

I have this file and I have nowatchdog in kernel parameters

10

you have to blacklist these 2 + adding the nowatchdog parameter:
blacklist iTCO_wdt
blacklist iTCO_vendor_support
then reboot and test with these commands:
cat /proc/sys/kernel/watchdog
cat /proc/sys/kernel/nmi_watchdog
both should give: ‘0’

11

Brahma is correct, my failure…
? nowatchdog is not needed if blacklisted? Either-or
My

journalctl -p err -b
sp5100-tco sp5100-tco: Watchdog hardware is disabled

solved by using
blacklist sp5100_tco
only, in /etc/modprobe.d/blacklist_tco.conf
No warnings after.

12

Yes, nowatchdog is not needed. But the broadcast message still exists. I regard it as a bug.

Although I did not find it in systemd’s github issues.