From: Karel Zak <kzak@redhat.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: util-linux@vger.kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [bugreport] "hwclock -w" reset time instead of setting the right time
Date: Thu, 2 Jan 2020 12:08:17 +0100 [thread overview]
Message-ID: <20200102110817.ahqaqidw3ztw3kax@10.255.255.10> (raw)
In-Reply-To: <CABXGCsNkzPrjqMRaWpssorxzhMLWBvLeSw9BpKYr_DW4LJQECQ@mail.gmail.com>
On Thu, Jan 02, 2020 at 01:08:41PM +0500, Mikhail Gavrilov wrote:
> "hwclock -w" reset time instead of setting the right time on M/B "ROG
> Strix X570-I Gaming"
> Demonstration: https://youtu.be/QRB7ZLiEfrc
> Some DE like GNOME has automatic time synchronization option and there
> is a feeling that hardware time reset after each Linux boot.
Can you try "hwclock -w -v" to get more details?
For example on my workstation:
# ./hwclock -w -v
hwclock from util-linux 2.35-rc1-20-63f8
System Time: 1577963091.683987
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1531914946 seconds after 1969
Last calibration done at 1531914946 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
RTC type: 'rtc_cmos'
Using delay: 0.500000 seconds
missed it - 1577963091.684767 is too far past 1577963091.500000 (0.184767 > 0.001000)
1577963092.500000 is close enough to 1577963092.500000 (0.000000 < 0.002000)
Set RTC to 1577963092 (1577963091 + 1; refsystime = 1577963091.000000)
Setting Hardware Clock to 11:04:52 = 1577963092 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Not adjusting drift factor because the --update-drift option was not used.
New /etc/adjtime data:
0.000000 1577963091 0.000000
1577963091
UTC
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2020-01-02 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABXGCsODr3tMpQxJ_nhWQQg5WGakFt4Yu5B8ev6ErOkc+zv9kA@mail.gmail.com>
[not found] ` <20200101141748.GA191637@mit.edu>
[not found] ` <CABXGCsOv26W6aqB5WPMe-mEynmwy55DTfTeL5Dg9vRq6+Y6WvA@mail.gmail.com>
2020-01-02 8:08 ` [bugreport] "hwclock -w" reset time instead of setting the right time Mikhail Gavrilov
2020-01-02 11:08 ` Karel Zak [this message]
2020-01-02 11:55 ` Mikhail Gavrilov
2020-01-02 13:14 ` Karel Zak
2020-01-02 15:00 ` Mikhail Gavrilov
2020-01-02 16:58 ` J William Piggott
2020-01-02 17:17 ` Mikhail Gavrilov
2020-01-03 10:02 ` Alexandre Belloni
2020-01-03 10:11 ` Mikhail Gavrilov
2020-01-03 10:19 ` Alexandre Belloni
2020-01-03 14:22 ` Mikhail Gavrilov
2020-01-04 5:44 ` Jinke Fan
2020-01-04 8:25 ` Mikhail Gavrilov
2020-01-04 11:35 ` Jinke Fan
2020-01-04 12:23 ` Mikhail Gavrilov
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=20200102110817.ahqaqidw3ztw3kax@10.255.255.10 \
--to=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=util-linux@vger.kernel.org \
/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).