Date: Wed, 24 Oct 2001 12:11:38 -0600 From: Nate Williams <nate@yogotech.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Hajimu UMEMOTO <ume@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/modules Makefile src/sys/modules/apm Makefile Message-ID: <15319.1114.52674.966040@caddis.yogotech.com> In-Reply-To: <xzp6694zzka.fsf@flood.ping.uio.no> References: <200110241653.f9OGrsL58421@freefall.freebsd.org> <xzp6694zzka.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Log: > > Make apm a module. > > We need further work to be able to specify an equivalence of `flags 0x20'. > > Many PCs should work for now. But, some PCs need `flags 0x20'. > > I know that "flags 0x20" means "broken statclock", but can you tell me > what symptoms a machine with a broken statclock would exhibit if that > flag were not set? It would hang when doing any APM commands (most notably, suspend). > Also, are there any disadvantages to setting that > flag on a machine that does not need it? Yes, the profiling and load average calculations don't work as well, so a process could theoretically get more CPU than it should. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15319.1114.52674.966040>