Intel NUC NUC8i3BEK Hardware Watchdog iTCO Linux Error

[JKipp]

Whenever I try to launch the Hardware Watchdog on my Intel NUC running 18.04 or 16.04 LTS Ubuntu I get:

(I am following this instruction http://www.madore.org/~david/linux/iTCO-wdt-test.html)

On my 7gen NUC with 16.04 it worked, but 8gen NUCs have this trouble. Glad for any help! Thanks

[  71.325175] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11

[  71.325237] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]

[  71.325252] iTCO_wdt: probe of iTCO_wdt failed with error -16

[Oscar_A_Intel1]

Hello JKipp,

Thank you for posting on the Intel Community.

I understand that you’re trying to launch the Hardware Watchdog on your Intel® NUC 8i3BEK.

Please allow me some days to investigate the behavior you’re experiencing, since the only operating system validated by Intel is Windows 10* 64-bit. You can check that information on the link below.

https://www.intel.com/content/www/us/en/support/articles/000005628/mini-pcs.html

Also, have you tried posting this question to the Linux* forum of the distribution that you’re using? You may have answers from users that have encountered the same issue.

Thank you,

Oscar A.

Intel Customer Support Technician

Under Contract to Intel Corporation

[JKipp]

Hello Oscar_intel,

thank you for taking a look into this. The hardware watchdog is important for Intel NUC to be used as IoT device.

I have only checked linux forums on this an, but not posted it public.

I have tried out 16.04 LTS, 18.04 LTS Ubuntu, Yocto and Debian OS. All give the same error. 6+ months ago, I remembered testing it with an older Linux Kernel on 16.04 and it worked.

So mostlikely all kernels of the last 6 months and 18.04 don't work on Linux together with 8 Gen NUCs.

Thanks

Jens

[Ronny_G_Intel]

Hi JKipp, We provide limited support for Linux* Operating Systems and most of the time we limit it to make sure that the OS runs fine. I have not tested this and we have no information about the error message reported. Did you report this error message to the owner of the guide: http://www.madore.org/~david/linux/iTCO-wdt-test.html ? Regards, Ronny G

[JKipp]

Hi,

I understand. I have made a bug report to the linux kernel maintainers of itco_wdt. If you could test this on your NUC and also confirm this error. This would help. Thanks

[Ronny_G_Intel]

Hi JKipp, I ran it and got the same "error message". If you get anything back from your bug report please let me know. Regards, Ronny G

[Abigail_G_Intel]

Hello JKipp,

I would like to know if you have any update that you would like to share with us?

Best Regards, 

Abigail G 

Intel Customer Support Technician

Under Contract to Intel Corporation. 

[vvidic]

I have the same problem with NUC8i5BEH. Neither iTCO_wdt nor wdat_wdt load correctly to create a working /dev/watchdog device. Can you issue a firmware update enabling watchdog device on Linux?

[IFisc]

@vvidic​ Did you find a solution? Also on my Nuc8i5BEH the wdat_wdt loads without any output as error, but no watchdog device is created :-( See also my thread here on intel forum https://forums.intel.com/s/question/0D70P000006VRwX/nuc8i5beh-is-registering-itcowd-watchdog-wronlgy-and-so-watchdog-is-unusable?s1oid=00DU0000000YT3c&s1nid=0DB0P000000U1Hq&emkind=chatterCommentNotification&s1uid=0050P000008X0kV&emtm=1571068968521&fromEmail=1&s1ext=0

[IMudr]

I am getting same error on brand new Laptop Lenovo P53 with i9-9880H CPU

iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11

iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]

iTCO_wdt: probe of iTCO_wdt failed with error -16

[IFisc]

I have the same with NUC8i5BEH too ... and also opened up an own thread some time ago. https://forums.intel.com/s/question/0D70P000006VRwX/nuc8i5beh-is-registering-itcowd-watchdog-wronlgy-and-so-watchdog-is-unusable?s1oid=00DU0000000YT3c&s1nid=0DB0P000000U1Hq&emkind=chatterCommentNotification&s1uid=0050P000008X0kV&emtm=1571068968521&fromEmail=1&s1ext=0

The error matches to infos that can be found at https://www.spinics.net/lists/linux-i2c/msg41504.html where Linux Kernel devs analyzed the tpic and said that it needs to be fixed in BIOS from NUC.