On Tue, Mar 10, 2020 at 12:24:24PM -0400, Theron wrote:
> On 2020-03-10 01:38, Peter Jeremy wrote:
> > Are you running NTP? If so, is NTP maintaining lock and what is the
> > reported PLL frequency (ntpq -c kerni)?
>
> Didn't show any useful difference, "kernel status: pll unsync" when I tested
>
On Mar 10, 2020, at 9:24 AM, Theron wrote:
>
> On 2020-03-10 01:38, Peter Jeremy wrote:
>> Are you running NTP? If so, is NTP maintaining lock and what is the
>> reported PLL frequency (ntpq -c kerni)?
>
> Didn't show any useful difference, "kernel status: pll unsync" when I tested
> this.
Ma
On Tue, Mar 10, 2020 at 9:24 AM Theron wrote:
> I had previously used powerd to let the CPU underclock to 700MHz when
> idle. Now, I've lost all control over CPU frequency (either by powerd
> or by sysctl) since there is some in-kernel cpufreq driver which I can't
> figure out how to disable.
It
On 2020-03-10 01:38, Peter Jeremy wrote:
Are you running NTP? If so, is NTP maintaining lock and what is the
reported PLL frequency (ntpq -c kerni)?
Didn't show any useful difference, "kernel status: pll unsync" when I
tested this.
What does "sysctl kern.timecounter" report and have you tr
On 2020-Mar-09 19:59:09 -0400, Theron wrote:
>Since switching from 12.1-RELEASE to CURRENT I've noticed timing
>problems with audio applications. It turns out that the problem is not
>with the audio drivers, but with the system clock driver, which now
>reports passage of time 0.3% too slow. A
Hi All,
Since switching from 12.1-RELEASE to CURRENT I've noticed timing
problems with audio applications. It turns out that the problem is not
with the audio drivers, but with the system clock driver, which now
reports passage of time 0.3% too slow. Although I discovered this only
recently
