Date: Thu, 24 Sep 2020 18:04:58 -0400 From: Ed Maste <emaste@freebsd.org> To: mike@karels.net Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: clock problems with BeagleBone Black on 12.2BETA2 Message-ID: <CAPyFy2Cz60DRVMvh0X3A2dn2U4LNXO%2BdSQYHSyFHQ8ctxkKviQ@mail.gmail.com> In-Reply-To: <202009221809.08MI9bwX036997@mail.karels.net> References: <202009221809.08MI9bwX036997@mail.karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Sep 2020 at 14:09, Mike Karels <mike@karels.net> wrote: > > I just installed 12.2BETA2 on a BeagleBone Black (armv7), and it took > at least an hour. I hit ^T periodically, and time seemed screwed up > (real time was progressing slowly at best). I've independently confirmed this on the 12.2BETA2 image; from my console: ... FreeBSD 12.2-BETA2 r365865 GENERIC arm ... Trying to mount root from ufs:/dev/ufs/rootfs [rw]... Warning: no time-of-day clock registered, system time will not be set accurately Growing root partition to fill device random: read_random_uio unblock wait load: 1.28 cmd: awk 39 [piperd] 0.12r 0.00u 0.00s 0% 2060k load: 1.28 cmd: awk 39 [piperd] 0.14r 0.00u 0.00s 0% 2060k ... time seems to be running about 500x slow. I ^C'd each startup script that was stuck (I'm not as patient as Mike), and got to a login prompt. I was able to login as root just fine and the system seemed responsive for commands that don't sleep. I tried `sleep 0.01` and that took about 5 seconds of actual time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Cz60DRVMvh0X3A2dn2U4LNXO%2BdSQYHSyFHQ8ctxkKviQ>