From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Peter Milley <pbmilley@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [BUG]: Error accessing realtime clock
Date: Wed, 14 Feb 2018 02:45:16 +0100 [thread overview]
Message-ID: <20180214014516.GB3354@piout.net> (raw)
In-Reply-To: <1518566194.3441.3.camel@gmail.com>
On 13/02/2018 at 18:56:34 -0500, Peter Milley wrote:
> Okay, I've booted the new kernel.
>
> peter@haven:~$ uname -a
> Linux haven 4.16.0-rc1+ #32 SMP Tue Feb 13 22:11:39 CET 2018 x86_64
> x86_64 x86_64 GNU/Linux
> peter@haven:~$ dmesg | grep -i rtc
> [ 0.045403] RTC time: 23:46:52, date: 02/13/18
> [ 1.368198] rtc_cmos 00:01: RTC can wake from S4
> [ 1.368205] rtc_cmos: drivers/rtc/rtc-cmos.c +679 cmos_do_probe
> [ 1.368235] rtc_cmos: drivers/rtc/rtc-cmos.c +684 cmos_do_probe
> [ 1.368260] rtc_cmos: drivers/rtc/rtc-cmos.c +688 cmos_do_probe
> [ 1.368285] rtc_cmos: 1: 70 8
> [ 1.368302] rtc_cmos: probe of 00:01 failed with error -16
> [ 1.408861] hctosys: unable to open rtc device (rtc0)
>
[...]
> And /proc/ioports:
> peter@haven:~$ sudo cat /proc/ioports
> 0000-0cf7 : PCI Bus 0000:00
> 0000-001f : dma1
> 0020-0021 : pic1
> 0040-0043 : timer0
> 0050-0053 : timer1
> 0060-0060 : keyboard
> 0062-0062 : PNP0C09:00
> 0062-0062 : EC data
> 0064-0064 : keyboard
> 0066-0066 : PNP0C09:00
> 0066-0066 : EC cmd
> 0070-0072 : wdat_wdt
So I can tell you what is happening but I can't tell you why. You have a
watchdog at 0x70 (size 2) and the RTC at 0x70 (size 8).
Because the watchdog driver is probed first and it requests the io
region, when the RTC driver is probed, it fails to request the same
region.
Maybe your 4.10 kernel didn't have CONFIG_WDAT_WDT (this appeared in
4.9).
I'm afraid, that is as far as I can help, you'd have to ask someone that
is more knowledgeable about x86 to go further (I've added the wdat_wdt
driver author in Cc).
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-14 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 0:12 PROBLEM: Error accessing realtime clock Peter Milley
2018-02-02 15:14 ` Peter Milley
2018-02-13 15:56 ` [BUG]: " Peter Milley
2018-02-13 20:25 ` Alexandre Belloni
2018-02-13 20:45 ` Peter Milley
2018-02-13 20:58 ` Alexandre Belloni
2018-02-13 22:20 ` Alexandre Belloni
2018-02-13 23:56 ` Peter Milley
2018-02-14 1:45 ` Alexandre Belloni [this message]
2018-02-14 20:35 ` Peter Milley
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=20180214014516.GB3354@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=linux-rtc@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pbmilley@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).