nowatchdog to the kernel parameters and wrote a file
and I ran:
sudo mkinitcpio -P
cat /proc/sys/kernel/watchdog gives
watchdog did not stop still exists when reboot
Host: ThinkPad Kernel: 5.17.5-2-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.24.5 Distro: Manjaro Linux
Type: Laptop System: LENOVO product: 20WKA000CD v: ThinkPad X13 Gen 2i
serial: <superuser required>
Mobo: LENOVO model: 20WKA000CD v: SDK0L77769 WIN
serial: <superuser required> UEFI: LENOVO v: N35ET44W (1.44 )
ID-1: BAT0 charge: 54.7 Wh (100.0%) condition: 54.7/54.7 Wh (100.0%)
Info: quad core 11th Gen Intel Core i7-1165G7 [MT MCP] speed (MHz):
avg: 660 min/max: 400/4700
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
Device-2: IMC Networks Integrated RGB Camera type: USB driver: uvcvideo
Display: x11 server: X.Org v: 21.1.3 driver: X: loaded: modesetting
gpu: i915 resolution: 2560x1600~60Hz
OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 22.0.2
Device-1: Intel Ethernet I219-V driver: e1000e
Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB
Local Storage: total: 953.87 GiB used: 88.02 GiB (9.2%)
Processes: 252 Uptime: 3m Memory: 15.35 GiB used: 2.89 GiB (18.9%)
Shell: Zsh inxi: 3.3.15
the exact command is:
blacklist iTCO_wdt not
nowatchdog to your kernel command-line as well.
The ones I blacklisted
Feels like you reopen this thread every couple months.
Just to be sure, watchdog and nmi_watchdog are two different things:
The Linux kernel watchdog is used to monitor if a system is running.
It is supposed to automatically reboot hanged systems due to unrecoverable software errors.
The watchdog module is specific to the hardware or chip being used.
Personal computer users don’t need watchdog as they can reset the system manually.
However, it is useful for systems that are mission critical and need the ability to reboot
themselves without human intervention.
A watchdog is usually a timer like mechanism which will generate an
interrupt at a specified time interval.
An NMI is a non maskable interrupt.
So an NMI watchdog is a watchdog which will generate a non maskable interrupt,
i.e. the interrupt handler will get executed no matter what the CPU state is.
This is very useful in scenarios where you are getting unexplained system freeze scenarios,
as the NMI watchdog interrupt handler will simply kill whatever process
happens to be freezing the CPU at the moment.
This way, your CPU gets freed up AND you get a detailed stack trace of why your
CPU got frozen up in the first place.
blacklist the following as such:
call file watchdog.conf and place in /etc/modprobe.d/
In Grub add nmi_watchdog=0 and nowatchdog in kernel boot parameter and UPDATE GRUB
Should show 0
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.