yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Chris Elledge <celledge@siteworx.io>
To: yocto@lists.yoctoproject.org
Subject: connman + busybox-hwclock startup failure
Date: Thu, 30 Mar 2023 18:04:59 -0400	[thread overview]
Message-ID: <CAHkgX0uZ0Hd5aMx+OcGuYnNdjVjY-nGCWLwL-D9-TbsnXo-m6w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1187 bytes --]

             reply	other threads:[~2023-03-30 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 22:04 Chris Elledge [this message]
2023-03-31  5:18 ` [yocto] connman + busybox-hwclock startup failure Alexander Kanavin
2023-07-28  6:15 ` Mike Looijmans

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=CAHkgX0uZ0Hd5aMx+OcGuYnNdjVjY-nGCWLwL-D9-TbsnXo-m6w@mail.gmail.com \
    --to=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).