From: Guenter Roeck <linux@roeck-us.net>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: iTCO_wdt on Intel NUC
Date: Mon, 22 Jul 2019 09:21:52 -0700 [thread overview]
Message-ID: <20190722162152.GB8122@roeck-us.net> (raw)
In-Reply-To: <20190722161026.3bzxwibivomuysqf@valentin-vidic.from.hr>
On Mon, Jul 22, 2019 at 06:10:26PM +0200, Valentin Vidić wrote:
> On Mon, Jul 22, 2019 at 08:45:50AM -0700, Guenter Roeck wrote:
> > Weird. Is iTCO_wdt instantiated twice ?
>
> I don't think so. I blacklisted iTCO_wdt module and rebooted but
> the iTCO_wdt line in /proc/iomem still appears although the module
> was not loaded.
>
> I suspect that it might have to do with one of these modules?
>
> drivers/platform/x86/intel_pmc_ipc.c:#define TCO_DEVICE_NAME "iTCO_wdt"
> drivers/mfd/lpc_ich.c: .name = "iTCO_wdt",
> drivers/i2c/busses/i2c-i801.c: pdev = platform_device_register_resndata(&pci_dev->dev, "iTCO_wdt", -1,
>
Correct.
I suspect that the driver may be instantiated from two locations
on your system. On top of that, there is also wdat_wdt, which
instantiates a watchdog device through ACPI. Overall there are lots
of areas where things can go wrong with this driver.
Guenter
next prev parent reply other threads:[~2019-07-22 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 20:30 iTCO_wdt on Intel NUC Valentin Vidić
2019-07-22 0:05 ` Guenter Roeck
2019-07-22 4:55 ` Valentin Vidić
2019-07-22 15:45 ` Guenter Roeck
2019-07-22 16:10 ` Valentin Vidić
2019-07-22 16:21 ` Guenter Roeck [this message]
2019-07-22 17:41 ` Valentin Vidić
2019-07-22 17:52 ` Guenter Roeck
2019-07-22 17:56 ` Valentin Vidić
2019-07-22 18:03 ` Guenter Roeck
2019-07-22 18:12 ` Valentin Vidić
2019-07-24 9:43 ` Guenter Roeck
2019-07-24 10:00 ` Valentin Vidić
2019-07-24 10:18 ` 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=20190722162152.GB8122@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=vvidic@valentin-vidic.from.hr \
/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).