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: Wed, 31 Jul 2019 21:43:32 -0700 [thread overview]
Message-ID: <a92b4ac7-1709-ffc0-77a5-b42bd26fc12d@roeck-us.net> (raw)
In-Reply-To: <CAH3OF53UrARyB8xnJLu4rXm2EJOzR9S2XViSMrmJXeeRuPgb3w@mail.gmail.com>
On 7/31/19 9:18 PM, Vignesh Raman wrote:
> Hi Guenter,
>
> On Thu, Jul 25, 2019 at 6:40 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> 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.
>>
>
> Thanks for catching that. In working case the output of /proc/iomem is,
>
Wasn't me. Someone else had the same or a similar problem, and Jean Delvare
noticed the overlap with system memory.
Guenter
> fd000000-fe7fffff : PCI Bus 0000:00
> fd000000-fdabffff : pnp 00:09
> fdac0000-fdacffff : pnp 00:0b
> fdad0000-fdadffff : pnp 00:09
> fdae0000-fdaeffff : pnp 00:0b
> fdaf0000-fdafffff : pnp 00:0b
> fdb00000-fdffffff : pnp 00:09
> fdc6000c-fdc6000f : iTCO_wdt
> fdc6000c-fdc6000f : iTCO_wdt
>
> This explains why it works in another system (i7-6700).
>
> Regards,
> Vignesh
>
next prev parent reply other threads:[~2019-08-01 4:43 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
2019-08-01 4:18 ` Vignesh Raman
2019-08-01 4:43 ` Guenter Roeck [this message]
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=a92b4ac7-1709-ffc0-77a5-b42bd26fc12d@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).