My system will no longer shutdown or reboot. I was originally using kernel 5.4 but upgraded to 5.10 but that did not resolve it. On shutdown the system hangs on a black screen and never fully shuts down. On reboot I get the error:
[ 168.212102] watchdog: watchdog0: watchdog did not stop!
Sometimes the above message is preceded with:
[ 167.731541] kauditd_printk_skb: 45 callbacks suppressed
[ 168.212102] watchdog: watchdog0: watchdog did not stop!
I added nowatchdog to GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub as described here but I continue to see the watchdog message on reboot. For either shutdown or reboot, I have to hold the power button to turn off the computer. I’ve read that shutdown/reboot problems could be tied to nvidia. After the latest update, I am forced to only use the opensource nvidia driver otherwise I get a black screen on boot.
Hi @linux-aarhus. I ran through the script and applied all recommended changes as prompted. However, the computer still behaves as described in first post failing to restart or shutdown.
Hi @linux-aarhus. Yes, it is a very old machine, but all that I have for now unfortunately. I am not sure why the controller is in RAID mode. I originally was using 5.4 kernel but only upgraded to 5.10 to test if it would fix shutdown/reboot problems. I have since downgraded back to 5.4. Below is results of intel-ucode reinstall and updated inxi output. The laptop still has same failed behavior on shutdown and reboot.
sudo pacman -Syyu intel-ucode
[sudo] password for name:
:: Synchronizing package databases...
core 167.6 KiB 1067 KiB/s 00:00 [######################] 100%
extra 1993.3 KiB 6.28 MiB/s 00:00 [######################] 100%
community 6.4 MiB 8.91 MiB/s 00:01 [######################] 100%
multilib 181.8 KiB 4.44 MiB/s 00:00 [######################] 100%
warning: intel-ucode-20201118-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) intel-ucode-20201118-1
Total Installed Size: 3.46 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) reinstalling intel-ucode [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
There is nothing wrong with having an old machine - if it works and fulfill it’s purpose then - I was just throwing ideas - and as I said - I not sure those particular settings makes a difference.
I did a search on your system and found a wiki entry on Centos.org.
It appears to reference a system comparable to yours.
The laptop has worked great for my purposes up until the most recent update. I’d like to continue using it rather than adding disposing of it.
Thank you for doing the research. I did see the ArchWiki link prior and added the nowatchdog to GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub as described here, but that didn’t make a difference. The wiki says “to disable watchdog timers (both software and hardware), append nowatchdog to your boot parameters.” Besides the aforementioned change and running the maxperfwiz script, I am not sure how to add nowatchdog to boot parameters?
The centos link is interesting. While I have used centos some in the past, I prefer manjaro and am hoping to keep it. Are you suggesting to switch to centos? Any additional suggestions to correct the reboot/shutdown failure?
No - I am not suggesting you should switch. But the centos link mentioned a setting which made the sleep function possible without the Nvidia driver.
You mentioned Nvidia as a possible cause of the issue.
The arch wiki link mentions that
Note: Some users reported the nowatchdog parameter does not work as expected but they have successfully disabled the watchdog (at least the hardware one) by blacklisting the above-mentioned module.
Which leads to the suggestion of blacklisting the watchdog module as described.
The centos wiki references adding the password to the BIOS for suspend to work. Would this affect shutdown/reboot as well or just suspend? I am using the opensource drivers for nvidia and have assumed that nvidia is the problem since historically that has often been the cause of many issues.
Do you know how to “blacklist” iTCO_wdt? I believe I do so within a .conf file in /etc/modprobe.d. Do I need to modify an existing file or should I create one specifically for this? Such as /etc/modprobe.d/myfile.conf. Within the conf file, I believe all it takes is just to add blacklist iTCO_wdt?
Curious if there are any further suggestions from the Manjaro community? I have run out of ideas and hoping that it is not time to scrap this laptop. Thanks.
- I was just throwing ideas - and as I said - I not sure those particular settings makes a difference.