Date: Sun, 18 Apr 1999 16:51:02 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: peter@netplex.com.au (Peter Wemm) Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! Message-ID: <199904181451.QAA73581@zibbi.mikom.csir.co.za> In-Reply-To: <19990418114321.DFE051F58@spinner.netplex.com.au> from Peter Wemm at "Apr 18, 1999 07:43:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> John Hay wrote:
> > > As of a few minutes ago, a minimal set of changes to bring the so-called
> > > 'new-bus' functionality to the i386 kernel in -current.
> > >
> >
> > It looks like the stat clock isn't started after this. I have tried a SMP
> > and UNI kernel and both behave the same. Looking with vmstat -i and
> > systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate
> > also have profhz and stathz as 100. A kernel of about a week ago doesn't
> > have this problem.
>
> Hmm...
>
> [7:38pm]~-103# sysctl kern.clockrate
> kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024,
> stathz = 128 }
>
Ok, I have found it. My kernel still had the apm line from its GENERIC
days, which didn't hurt me before:
device apm0 at nexus? disable flags 0x31 # Advanced Power Management
It seems that the disable keyword is ignored, because the apm0 device
suddenly appeared in the probe messages and that set statclock_disable to 1.
I have removed apm from my kernel config file and all is well again.
John
--
John Hay -- John.Hay@mikom.csir.co.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904181451.QAA73581>