clock problems with BeagleBone Black on 12.2BETA2

[Mike Karels]

bcc: re@ for their information

> Date: Tue, 22 Sep 2020 19:27:54 +0000 (UTC)
> From: Oskar Holmlund <oskar.holmlund at yahoo.com>

>  Den tisdag 22 september 2020 20:09:53 CEST, Mike Karels <mike at karels.net> skrev: 

> > 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). Eventually the system came
> > up, and I logged in. I ran date several times, a few seconds apart, and
> > the time did not change. I ran a ping of a nearby system, and it sent
> > and received only one ping; aparently timeouts/alarms are broken. It is
> > as if the system clock is not interrupting, or is doing so much more slowly
> > than it should. I'll append a transcript in case there are clues that I
> > missed. Any thoughts on what is broken?

> > fwiw, I also installed on a Raspberry Pi 3B+ (aarch64), and that proceeded
> > normally.

> 		Mike
[transcript omitted]

> Hi Mike,



> If I remember correct, most of the system are broken due to removal of ti,hwmods property in the devicetree.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244754

> A workaround is to use an older version of devicetree. I cant tell if you need to do it manually or if sombody will do it for you in the 12.2 release process.

> Another solution is to use head. Beaglebone black and pocketbeagle works. It's still work to cleanup the transition to the clk framework, feel free to try it out and please let me know if you run into any trouble.

> //Oskar

Thanks for the information.  fwiw, it would sure be nice if this was working
at release time.  I expect occasional breakage on head, but not on releng/X
as we approach release time.

		Mike