linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Vignesh Raman <vignesh.raman.in@gmail.com>
Cc: linux-watchdog@vger.kernel.org,
	andriy.shevchenko@linux.intel.com,
	rajneesh.bhardwaj@linux.intel.com,
	mika.westerberg@linux.intel.com
Subject: Re: watchdog: iTCO_wdt: failed to load
Date: Thu, 25 Jul 2019 06:10:33 -0700	[thread overview]
Message-ID: <e1f4f561-ba33-b9ce-66db-c67cb260ecdf@roeck-us.net> (raw)
In-Reply-To: <CAH3OF53G3bHfxpGVLHKns9k-QBAUroiqvkcdQ4d+gOmsLvaN6w@mail.gmail.com>

On 7/24/19 10:12 PM, Vignesh Raman wrote:
> Hi Guenter,
> 
> On Wed, Jul 24, 2019 at 6:57 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> What is the output of /proc/iomem, what PCI devices does it have, and what are
>> the ACPI devices ? Reason for asking is that I don't immediately see the ACPI
>> or PCI devices associated with above patch in your dmesg. If not, the patch
>> might actually cause the watchdog in your system not to work.
> 
> /proc/iomem  - http://paste.debian.net/1092996/

Here is your problem:

00100000-5e431017 : System RAM
   00c5fffc-00c5ffff : iTCO_wdt

The address range requested by the watchdog is marked by the BIOS as system memory.

The patch referenced below tries to address a different problem and does not apply
to your system.

Guenter

> PCI devices  - http://paste.debian.net/1092997/
> ACPI devices - http://paste.debian.net/1093003/
> 
>> Also, did this ever work in your system ? If it did work, did the failure
>> start after a kernel update or after a BIOS update ?
> 
> The hardware watchdog has never worked in the system. Without the
> patch https://lore.kernel.org/patchwork/patch/770990/ the probe error
> is seen,
> [    3.828440] iTCO_wdt iTCO_wdt: can't request region for resource
> [mem 0x00c5fffc-0x00c5ffff]
> [    3.828803] iTCO_wdt: probe of iTCO_wdt failed with error -16
> 
> With the patch the module loads fine, but the hardware watchdog does not work.
> 
> Regards,
> Vignesh
> 


  reply	other threads:[~2019-07-25 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24  7:34 watchdog: iTCO_wdt: failed to load Vignesh Raman
2019-07-24  9:34 ` Guenter Roeck
2019-07-24 13:27 ` Guenter Roeck
2019-07-25  5:12   ` Vignesh Raman
2019-07-25 13:10     ` Guenter Roeck [this message]
2019-08-01  4:18       ` Vignesh Raman
2019-08-01  4:43         ` Guenter Roeck
2019-07-24 16:06 ` Andy Shevchenko

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=e1f4f561-ba33-b9ce-66db-c67cb260ecdf@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rajneesh.bhardwaj@linux.intel.com \
    --cc=vignesh.raman.in@gmail.com \
    /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).