Re: kern/56322: Excessive clock drift

[Frank Kardel <kardel%kardel.name@localhost>]

The following reply was made to PR kern/56322; it has been noted by GNATS.

From: Frank Kardel <kardel%kardel.name@localhost>
To: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, dholland%NetBSD.org@localhost
Cc: 
Subject: Re: kern/56322: Excessive clock drift
Date: Fri, 23 Jul 2021 09:22:16 +0200

 Did you mean to say HPET? I thought it was using TSC?
 
 I am interested in the value of kern.timecounter.choice like
 
 in the output below
 
 EXAMPLE:
 
 kern.timecounter.choice = TSC(q=3000, f=2200001000 Hz) 
 clockinterrupt(q=0, f=100 Hz) lapic(q=-100, f=25000000 Hz) hpet0(q=2000, 
 f=24000000 Hz) ACPI-Fast(q=1000, f=3579545 Hz) i8254(q=100, f=1193182 
 Hz) dummy(q=-1000000, f=1000000 Hz)
 kern.timecounter.hardware = TSC
 kern.timecounter.timestepwarnings = 1
 
 Frank
 
 
 On 07/23/21 01:35, David Holland wrote:
 > The following reply was made to PR kern/56322; it has been noted by GNATS.
 >
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: kern/56322: Excessive clock drift
 > Date: Thu, 22 Jul 2021 23:30:32 +0000
 >
 >   On Thu, Jul 22, 2021 at 03:05:01PM +0000, Frank Kardel wrote:
 >    > So I had to propose the next known workable alternative instead of
 >    > timecounters that haven't been detected :-). HPET is sometimes
 >    > disabled in BIOS.
 >   
 >   Like I said, I'll check that next time I reboot this machine, which
 >   isn't ordinarily very often.
 >   
 >    >  So far we do not know the output of "sysctl kern.timercounter".
 >   
 >   Like I already said, it was using the bad HPET.
 >   
 >   --
 >   David A. Holland
 >   dholland%netbsd.org@localhost
 >