[solved] load the correct watchdog kernel module - using a fake install
-
- OMV 4.x
- openmedianer
-
-
Hello, now i have upgrade my system.
A clean shutdown is not working.Codeuname -r 4.18.0-0.bpo.3-amd64 [ 0.00000] ACPI: SPCR Unexpected SPCR Access Width. Defaulting to byte size
OMV 4 boot very slow.
How can i solved the problem?
https://forum.openmediavault.o…hread/4974-softdog-error/
-
More Info:
Now I use Kernel 4.9.0-7-amd64
systemctl status watchdog.service
Code
Alles anzeigensystemctl status watchdog.service ● watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-01-10 20:06:08 CET; 26min ago Process: 1078 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS) Process: 1072 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=ex ited, status=0/SUCCESS) Main PID: 1081 (watchdog) Tasks: 1 (limit: 4915) CGroup: /system.slice/watchdog.service └─1081 /usr/sbin/watchdog Jan 10 20:06:08 openmediavault watchdog[1081]: interface: no interface to check Jan 10 20:06:08 openmediavault watchdog[1081]: temperature: no sensors to check Jan 10 20:06:08 openmediavault watchdog[1081]: no test binary files Jan 10 20:06:08 openmediavault watchdog[1081]: no repair binary files Jan 10 20:06:08 openmediavault watchdog[1081]: error retry time-out = 60 seconds Jan 10 20:06:08 openmediavault watchdog[1081]: repair attempts = 1 Jan 10 20:06:08 openmediavault watchdog[1081]: alive=/dev/watchdog heartbeat=[none] to=root no_act=no force=no Jan 10 20:06:08 openmediavault watchdog[1081]: watchdog now set to 60 seconds Jan 10 20:06:08 openmediavault watchdog[1081]: hardware watchdog identity: FSC watchdog Jan 10 20:06:08 openmediavault systemd[1]: Started watchdog daemon.
-
-
https://fossies.org/linux/kern…cumentation/hwmon/sch5636
https://www.suse.com/de-de/support/kb/doc/?id=7016880
ZitatStep 1. The right watchdog module has to be determined.
Currently there is no stable programmatic approach to determine the right watchdog kernel module in any case.
- On HP hardware the "hpwdt" module should work.
- For systems with an Intel TCO "iTCO_wdt" can be used.
Dell, Fujitsu, and Lenovo usually fall into this category. - Inside a VM on z/VM on an IBM mainframe "vmwatchdog" might be used.
- Inside a Xen VM (aka DomU) "xen_wdt" is a good choice.
- "softdog" is the most generic driver, but it is recommended that you use one with actual hardware integration.
See /lib/modules/.../kernel/drivers/watchdog in the kernel package for a list of choices. Of course, the hardware
vendor should be able to name the right watchdog. A test as described in
step 5 below shows, if a loaded module works.
My System:Codelsmod | grep -e dog -e wdt softdog 16384 0 iTCO_wdt 16384 0 iTCO_vendor_support 16384 1 iTCO_wdt
Hello, my problem isn't solved.
Can you help me?https://unix.stackexchange.com…cklist-conf-does-not-work
-
My solution:
with Kernel linux-image-4.9.0-8-amd
Code
Alles anzeigenKernel 4.18.0-0.bpo.3-amd64 will not clean booting, now shutdown oder reboot support. Error Message, dmesg: [ 0.000000] ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size Very long time to boot. --------------------------- Installing the default Debian 9 Kernel: apt-get install linux-image-4.9.0-7-amd64 --------------------------- Configuration "last choise" Grub2. https://askubuntu.com/questions/148662/how-to-get-grub2-to-remember-last-choice --------------------------- Booting Kernel linux-image-4.9.0-8-amd6 Blacklist with fake install, because the standard blacklisting doesn't work. ----------------------- nano /etc/modprobe.d/softdog.conf Check: cat /etc/modprobe.d/softdog.conf install softdog /bin/true ----------------------- nano /etc/modprobe.d/iTCO_wdt.conf Check: cat /etc/modprobe.d/iTCO_wdt.conf install iTCO_wdt /bin/true ---------------------------------- nano /etc/modprobe.d/iTCO_vendor_support.conf cat /etc/modprobe.d/iTCO_vendor_support.conf install iTCO_vendor_support /bin/true --------------------------------- depmod -ae update-initramfs -u --------------------------------- Now i don't get any error message with dmesg.
14.01.2019
uname -r
4.19.0-0.bpo.1-amd64Now i get with dmesg
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!