No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Bug #1713535 reported by Olivier Louvignes
6
This bug affects 1 person
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_support: vendor-support=0
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/system/watchdog.service; enabled; vendor preset: enabled)
   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=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, status=0/SUCCESS)
 Main PID: 2768 (watchdog)
    Tasks: 1
   Memory: 732.0K
      CPU: 13ms
   CGroup: /system.slice/watchdog.service
           └─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/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
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=/boot/vmlinuz-4.11.0-14-generic root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 vt.handoff=7
ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.11.0-14-generic N/A
 linux-backports-modules-4.11.0-14-generic N/A
 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.86A.0029.2016.1124.1625
dmi.board.name: NUC6CAYB
dmi.board.vendor: Intel Corporation
dmi.board.version: J23203-402
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:

description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: artful
Revision history for this message
Olivier Louvignes (olouvignes) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Olivier Louvignes (olouvignes) wrote : CRDA.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : IwConfig.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : JournalErrors.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : Lspci.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : ProcEnviron.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : ProcModules.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : RfKill.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : UdevDb.txt

apport information

Revision history for this message
Olivier Louvignes (olouvignes) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc7

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Olivier Louvignes (olouvignes) wrote :

I've just installed v4.13-rc7 and no more luck .

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.