From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Chris Elledge <celledge@siteworx.io>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] connman + busybox-hwclock startup failure
Date: Fri, 31 Mar 2023 07:18:08 +0200 [thread overview]
Message-ID: <CANNYZj-M=MwvYT7Ed0VGyEbYMovP90ZWfn383DofozCxa28rMw@mail.gmail.com> (raw)
In-Reply-To: <CAHkgX0uZ0Hd5aMx+OcGuYnNdjVjY-nGCWLwL-D9-TbsnXo-m6w@mail.gmail.com>
Can you submit a patch for this please? The mailing list is openembedded-core@.
Alex
On Fri, 31 Mar 2023 at 00:05, Chris Elledge <celledge@siteworx.io> wrote:
>
> I've encountered an issue when using a system that has both connman and the hwclock.sh script enabled during startup. The default combined startup order for these two services is wrong.
>
> Currently connman starts at 05, and hwclock.sh is at 20 (default for update-rc.d). This means that we have a situation where connman starts up and obtains a correct NTP time, then hwclock.sh clobbers the system time with whatever is in the RTC even if it is way in the past. The big issue caused by that is connman schedules its next NTP update at an absolute time of (current time + 1024s). Once the hwclock.sh script knocks the system time way into the past, the NTP update will not run for a potentially very long time.
>
> I would suggest adding a line to poky/meta/recipes-core/busybox.inc to move hwclock.sh earlier.
> For example:
> INITSCRIPT_PARAMS:${PN}-hwclock = "start 04 2 3 4 5 . stop 20 0 1 6"
> or
> INITSCRIPT_PARAMS:${PN}-hwclock = "start 40 S . stop 20 0 1 6"
>
> Thanks,
> Chris Elledge
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#59555): https://lists.yoctoproject.org/g/yocto/message/59555
> Mute This Topic: https://lists.yoctoproject.org/mt/97961702/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2023-03-31 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 22:04 connman + busybox-hwclock startup failure Chris Elledge
2023-03-31 5:18 ` Alexander Kanavin [this message]
2023-07-28 6:15 ` [yocto] " Mike Looijmans
[not found] <175151A6DCB6A43F.12651@lists.yoctoproject.org>
2023-03-30 22:10 ` Chris Elledge
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='CANNYZj-M=MwvYT7Ed0VGyEbYMovP90ZWfn383DofozCxa28rMw@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=celledge@siteworx.io \
--cc=yocto@lists.yoctoproject.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).