No /dev/watchdog on NUC6CAYS devices with iTCO_wdt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
It looks like iTCO_wdt won't properly setup a /dev/watchdog device on Intel recent Celeron NUCs (NUC6CAYS).
```
# uname -a
Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
```
Modules are properly loaded (but looks like it is not used)
```
# lsmod | grep -e dog -e wdt
iTCO_wdt 16384 0
iTCO_vendor_support 16384 1 iTCO_wdt
```
No device found in kernel.log:
```
Aug 28 18:49:56 player-ef15 kernel: [ 14.192689] iTCO_vendor_
Aug 28 18:49:56 player-ef15 kernel: [ 14.198585] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
```
No device found by the service:
```
# service watchdog status
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/
Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
Process: 2758 ExecStartPre=
Main PID: 2768 (watchdog)
Tasks: 1
Memory: 732.0K
CPU: 13ms
CGroup: /system.
└─2768 /usr/sbin/watchdog
août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no soft=no mla=0 mem=0
août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to check
août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno = 2 = 'No such file or directory')
```
---
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2017-08-28 (1 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0aa7 Intel Corp.
Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.157.11
Tags: xenial
Uname: Linux 4.11.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access sambashare sudo video www-data
_MarkForUpload: True
dmi.bios.date: 11/24/2016
dmi.bios.vendor: Intel Corp.
dmi.bios.version: AYAPLCEL.
dmi.board.name: NUC6CAYB
dmi.board.vendor: Intel Corporation
dmi.board.version: J23203-402
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
description: | updated |
description: | updated |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1713535
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.