Re: kern/56322: Excessive clock drift

[David Holland <dholland-bugs%netbsd.org@localhost>]

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: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
	netbsd-bugs%netbsd.org@localhost, dholland%NetBSD.org@localhost
Subject: Re: kern/56322: Excessive clock drift
Date: Sat, 24 Jul 2021 03:12:24 +0000

 On Fri, Jul 23, 2021 at 07:25:01AM +0000, Frank Kardel wrote:
  >  Did you mean to say HPET? I thought it was using TSC?
 
 Er, yeah.
 
  >  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
 
 kern.timecounter.choice = TSC(q=3000, f=3517182870 Hz) clockinterrupt(q=0, f=100 Hz) lapic(q=-100, f=200982000 Hz) i8254(q=100, f=1193182 Hz) dummy(q=-1000000, f=1000000 Hz)
 kern.timecounter.hardware = i8254
 kern.timecounter.timestepwarnings = 0
 
 Other than the lapic entry, which doesn't appear to be particularly
 interesting, no information that wasn't in the dmesg output.
 
 (The hardware is now i8254 because I changed it; it started as TSC.)
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost