From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: J William Piggott <elseifthen@gmx.com>,
Karel Zak <kzak@redhat.com>,
util-linux@vger.kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-rtc@vger.kernel.org
Subject: Re: [bugreport] "hwclock -w" reset time instead of setting the right time
Date: Fri, 3 Jan 2020 11:02:32 +0100 [thread overview]
Message-ID: <20200103100232.GH3040@piout.net> (raw)
In-Reply-To: <CABXGCsMLfarquWnzV=e3Ta_HPac+DALfKEOaD3rp5n9MPqgyFw@mail.gmail.com>
Hi,
On 02/01/2020 22:17:26+0500, Mikhail Gavrilov wrote:
> On Thu, 2 Jan 2020 at 21:59, J William Piggott <elseifthen@gmx.com> wrote:
> >
> > You've demonstrated that 'hwclock -w' does not 'reset' the RTC.
> >
> > Does your new motherboard use a battery backup for the RTC?
> > Is the battery good?
> >
>
> If you look carefully demonstration the RTC 'reset' happens after
> reboot __only__ when 'hwclock -w' have been entered before reboot.
> So if I reboot the computer without 'hwclock -w' the RTC will be not reset.
>
What is your kernel version?
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-03 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 10:58 [bugreport] Ext4 automatically checked at each boot Mikhail Gavrilov
2020-01-01 12:30 ` Mikhail Gavrilov
2020-01-01 14:17 ` Theodore Y. Ts'o
2020-01-01 23:19 ` Mikhail Gavrilov
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
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 [this message]
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=20200103100232.GH3040@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=elseifthen@gmx.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.