linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-watchdog@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	it+linux-watchdog@molgen.mpg.de
Subject: Re: watchdog: iTCO_wdt: cannot register miscdev on minor=130 (err=-16).
Date: Tue, 26 May 2020 04:38:50 -0700	[thread overview]
Message-ID: <95b7828b-2de2-6c29-f51d-c6d22b59d014@roeck-us.net> (raw)
In-Reply-To: <a6e0f876-3a0f-49fd-7f45-715e75b6a779@molgen.mpg.de>

On 5/26/20 4:21 AM, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> Linux 5.4.39 reports the watchdog messages below on a Dell PowerEdge T630 with 12x E5-2603 v4 @ 1.70GHz.
> 
>     DMI: Dell Inc. PowerEdge T630/0NT78X, BIOS 2.5.4 08/17/2017
> 
> ```
> handsomejack:~$ more /proc/version
> Linux version 5.4.39.mx64.334 (root@lol.molgen.mpg.de) (gcc version 7.5.0 (GCC)) #1 SMP Thu May 7 14:27:50 CEST 2020
> handsomejack:~$ grep TCO /boot/config-5.4.39.mx64.334
> CONFIG_NETCONSOLE=m
> CONFIG_NETCONSOLE_DYNAMIC=y
> # CONFIG_SP5100_TCO is not set
> CONFIG_ITCO_WDT=y
> CONFIG_ITCO_VENDOR_SUPPORT=y
> CONFIG_NV_TCO=y
> # CONFIG_INTEL_SMARTCONNECT is not set
> # CONFIG_EXTCON is not set
> handsomejack:~$ dmesg --level=err
> [   11.618887] watchdog: iTCO_wdt: cannot register miscdev on minor=130 (err=-16).
> [   11.627956] watchdog: iTCO_wdt: a legacy watchdog module is probably present.
> handsomejack:~$ dmesg | grep -e iTCO -e watchdog
> [   11.603138] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> [   11.609888] iTCO_wdt: Found a Wellsburg TCO device (Version=2, TCOBASE=0x0460)
> [   11.618887] watchdog: iTCO_wdt: cannot register miscdev on minor=130 (err=-16).
> [   11.627956] watchdog: iTCO_wdt: a legacy watchdog module is probably present.
> [   11.636462] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> [   11.643679] iTCO_vendor_support: vendor-support=0
> handsomejack:~$ ls -l /dev/watchdog
> crw------- 1 root root 10, 130 May 26 11:40 /dev/watchdog
> ```
> 
> Together the error and success messages are from the same module are confusing me a little. How can I find out the legacy watchdog module?
> 

/dev/watchdog is your legacy watchdog. You should also have /dev/watchdogN
(where N is a number, probably '0') which is the iTCO watchdog. The error
message refers to the inability to create /dev/watchdog because it already
exists, not to the inability to install the driver at all.

You might have some other log messages indicating which other watchdog
is installed. Otherwise you might need to use ioctls on /dev/watchdog
to determine its name. 'lsmod' might also be useful.

Guenter

  reply	other threads:[~2020-05-26 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 11:21 watchdog: iTCO_wdt: cannot register miscdev on minor=130 (err=-16) Paul Menzel
2020-05-26 11:38 ` Guenter Roeck [this message]
     [not found]   ` <843f5c26-82ac-3553-7d98-3cbe3068cc99@molgen.mpg.de>
2020-05-26 13:54     ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95b7828b-2de2-6c29-f51d-c6d22b59d014@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=it+linux-watchdog@molgen.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=wim@linux-watchdog.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).