From: Guenter Roeck <linux@roeck-us.net>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>,
linux-watchdog@vger.kernel.org
Subject: Re: iTCO_wdt on Intel NUC
Date: Wed, 24 Jul 2019 02:43:58 -0700 [thread overview]
Message-ID: <2a14874f-1e28-6e42-ab87-b2c1e1ca5ac4@roeck-us.net> (raw)
In-Reply-To: <d2f78a10-df19-9922-565d-b0ed6fcacb67@roeck-us.net>
On 7/21/19 5:05 PM, Guenter Roeck wrote:
> On 7/21/19 1:30 PM, Valentin Vidić wrote:
>> Hello,
>>
>> I'm having trouble getting iTCO_wdt to work on NUC8i5BEH with kernel 4.19.37-5+deb10u1:
>>
>> [ 9.346099] iTCO_vendor_support: vendor-support=0
>> [ 9.377211] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
>> [ 9.377397] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
>> [ 9.377407] iTCO_wdt: probe of iTCO_wdt failed with error -16
>>
>> Is there a way to check if the TCO hardware is missing in this machine
>> or something else needs to be updated to get it working?
>>
>
> Most likely the memory region is reserved/used by something else. /proc/iomem
> might show you.
>
Here is a possible explanation for your problem.
https://lore.kernel.org/patchwork/patch/770990/
It seems like the memory resource is indeed reserved by the intel_pmc_ipc driver.
Guenter
next prev parent reply other threads:[~2019-07-24 9:44 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
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 [this message]
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=2a14874f-1e28-6e42-ab87-b2c1e1ca5ac4@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).