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 10:52:03 -0700 [thread overview]
Message-ID: <20190722175203.GA12554@roeck-us.net> (raw)
In-Reply-To: <20190722174129.qzlg5exwx5ns3fkw@valentin-vidic.from.hr>
On Mon, Jul 22, 2019 at 07:41:29PM +0200, Valentin Vidić wrote:
> On Mon, Jul 22, 2019 at 09:21:52AM -0700, Guenter Roeck wrote:
> > 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.
>
> Yes, it seems to be related to i2c_i801 because that tries to
> load iTCO_wdt:
>
> # modprobe i2c_i801
> [40450.070587] i801_smbus 0000:00:1f.4: SPD Write Disable is set
> [40450.070652] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
> [40450.072919] iTCO_vendor_support: vendor-support=0
> [40450.073485] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> [40450.073546] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
> [40450.073578] iTCO_wdt: probe of iTCO_wdt failed with error -16
>
Is this the first mention of iTCO_wdt in the log ?
The easiest explanation that this point would be that lpc_ich instantiates
iTCO_wdt as well.
Guenter
next prev parent reply other threads:[~2019-07-22 17:52 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
2019-07-22 17:41 ` Valentin Vidić
2019-07-22 17:52 ` Guenter Roeck [this message]
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=20190722175203.GA12554@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