[solved] load the correct watchdog kernel module - using a fake install

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • [solved] load the correct watchdog kernel module - using a fake install

      New

      Hello, how can i solved with problem?


      Source Code

      1. dmesg
      2. [ 90.305468] watchdog: Software Watchdog: cannot register miscdev on minor=130 (err=-16).
      3. [ 90.305526] watchdog: Software Watchdog: a legacy watchdog module is probably present.
      I use Kernel 4.14.0-0.bpo.3-amd64.


      Best regards

      openmedianer







      The post was edited 3 times, last by openmedianer ().

    • New

      Hello, now i have upgrade my system.
      A clean shutdown is not working.



      Source Code

      1. uname -r
      2. 4.18.0-0.bpo.3-amd64
      3. [ 0.00000] ACPI: SPCR Unexpected SPCR Access Width. Defaulting to byte size
      OMV 4 boots very slow.

      How can i solved the problem?


      forum.openmediavault.org/index…hread/4974-softdog-error/

      unix.stackexchange.com/questio…daemon-for-bios-watch-dog
      Images
      • omv-paste-update-bootmessege.jpg

        52.55 kB, 800×90, viewed 8 times
      • 2019-01-08-22-imgsda1omv-OMV-default-Partitionen.jpg

        136.81 kB, 800×510, viewed 7 times
      • 2019-01-08-23-imgsda1omv-OMV-change-Partitionen.jpg

        157.62 kB, 940×597, viewed 6 times

      The post was edited 8 times, last by openmedianer ().

    • New

      More Info:

      Now I use Kernel 4.9.0-7-amd64



      systemctl status watchdog.service

      Source Code

      1. systemctl status watchdog.service
      2. ● watchdog.service - watchdog daemon
      3. Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled)
      4. Active: active (running) since Thu 2019-01-10 20:06:08 CET; 26min ago
      5. Process: 1078 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
      6. Process: 1072 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=ex
      7. ited, status=0/SUCCESS)
      8. Main PID: 1081 (watchdog)
      9. Tasks: 1 (limit: 4915)
      10. CGroup: /system.slice/watchdog.service
      11. └─1081 /usr/sbin/watchdog
      12. Jan 10 20:06:08 openmediavault watchdog[1081]: interface: no interface to check
      13. Jan 10 20:06:08 openmediavault watchdog[1081]: temperature: no sensors to check
      14. Jan 10 20:06:08 openmediavault watchdog[1081]: no test binary files
      15. Jan 10 20:06:08 openmediavault watchdog[1081]: no repair binary files
      16. Jan 10 20:06:08 openmediavault watchdog[1081]: error retry time-out = 60 seconds
      17. Jan 10 20:06:08 openmediavault watchdog[1081]: repair attempts = 1
      18. Jan 10 20:06:08 openmediavault watchdog[1081]: alive=/dev/watchdog heartbeat=[none] to=root no_act=no force=no
      19. Jan 10 20:06:08 openmediavault watchdog[1081]: watchdog now set to 60 seconds
      20. Jan 10 20:06:08 openmediavault watchdog[1081]: hardware watchdog identity: FSC watchdog
      21. Jan 10 20:06:08 openmediavault systemd[1]: Started watchdog daemon.
      Display All

      The post was edited 1 time, last by openmedianer ().

    • New

      fossies.org/linux/kernel/v4.14…cumentation/hwmon/sch5636


      suse.com/de-de/support/kb/doc/?id=7016880


      Step 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:

      Source Code

      1. lsmod | grep -e dog -e wdt
      2. softdog 16384 0
      3. iTCO_wdt 16384 0
      4. iTCO_vendor_support 16384 1 iTCO_wdt



      Hello, my problem isn't solved.
      Can you help me?



      unix.stackexchange.com/questio…cklist-conf-does-not-work

      wiki.debian.org/KernelModuleBlacklisting

      The post was edited 8 times, last by openmedianer ().

    • New

      My solution:

      with Kernel linux-image-4.9.0-8-amd

      Brainfuck Source Code

      1. Kernel 4.18.0-0.bpo.3-amd64 will not clean booting, now shutdown oder reboot support.
      2. Error Message, dmesg: [ 0.000000] ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size
      3. Very long time to boot.
      4. ---------------------------
      5. Installing the default Debian 9 Kernel:
      6. apt-get install linux-image-4.9.0-7-amd64
      7. ---------------------------
      8. Configuration "last choise" Grub2.
      9. https://askubuntu.com/questions/148662/how-to-get-grub2-to-remember-last-choice
      10. ---------------------------
      11. Booting
      12. Kernel linux-image-4.9.0-8-amd6
      13. Blacklist with fake install, because the standard blacklisting doesn't work.
      14. -----------------------
      15. nano /etc/modprobe.d/softdog.conf
      16. Check:
      17. cat /etc/modprobe.d/softdog.conf
      18. install softdog /bin/true
      19. -----------------------
      20. nano /etc/modprobe.d/iTCO_wdt.conf
      21. Check:
      22. cat /etc/modprobe.d/iTCO_wdt.conf
      23. install iTCO_wdt /bin/true
      24. ----------------------------------
      25. nano /etc/modprobe.d/iTCO_vendor_support.conf
      26. cat /etc/modprobe.d/iTCO_vendor_support.conf
      27. install iTCO_vendor_support /bin/true
      28. ---------------------------------
      29. depmod -ae
      30. update-initramfs -u
      31. ---------------------------------
      32. Now i don't get any error message with dmesg.
      Display All


      14.01.2019

      uname -r
      4.19.0-0.bpo.1-amd64

      Now i get with dmesg

      Source Code

      1. [ 0.083051] ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size

      The post was edited 9 times, last by openmedianer ().