Thank you for the information. I can now see where the various frequencies come from when I change setperf. Is it possible to see the cpu voltage anywhere, to go along with the hw.cpuspeed?
I want to do further testing with the stress program as I do not think the H5 stability problems are to do with speed/voltage. I suspect something to do with network. I started out with the dwxe0 lan plugged into a 1000Mhz switch and failures were quite often. I then downgraded to a 100Mhz port and the system seemed to hang in there longer. I then tested with an old usb wifi adapter(run0) which was very slow and the system behaved even better, although it did fail in the same fashion. Has anyone tried to trace back the crash reports? It always seems to be a consistent crash no matter the program that was running. Stephen Graf -----Original Message----- From: owner-...@openbsd.org <owner-...@openbsd.org> On Behalf Of Mark Kettenis Sent: February 3, 2019 11:54 AM To: s_g...@telus.net Cc: k.lewandow...@icloud.com; arm@openbsd.org Subject: Re: initial cpu speed on orangepi one and orangepi pc2 - probably other H5 and H3 boards Any OS will boot with the CPU clock frequency and voltage that was set up by the firmware/bootloader. Those are supposed to be "safe" settings in the sense that the OS can run without overheating the SoC. If the DT provides a set of operating points, and there is clock and regulator support, OpenBSD will allow changing the clock frequency. For each frequency it will select the associated voltage in the operating points table. When there is support for changing the clock frequency, OpenBSD will switch to the operating point that has an associated clock frequency that not higher than the clock frequency the system booted with.
