Date: Wed, 24 Oct 2001 12:45:18 -0600 From: Nate Williams <nate@yogotech.com> To: Hajimu UMEMOTO <ume@mahoroba.org> Cc: nate@yogotech.com, des@ofug.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.3134.821325.222080@caddis.yogotech.com> In-Reply-To: <20011025.034150.85324385.ume@mahoroba.org> References: <200110241653.f9OGrsL58421@freefall.freebsd.org> <xzp6694zzka.fsf@flood.ping.uio.no> <15319.1114.52674.966040@caddis.yogotech.com> <20011025.034150.85324385.ume@mahoroba.org>
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? > > nate> It would hang when doing any APM commands (most notably, suspend). > > Yup, I met hang up probably this, just now. X-( > statclock_disable affect not apm.c but clock.c. So, I wish to add > something like machdep.disable_rtc_statclock into clock.c. How about > this idea? The thing is that this only effects apm, so it really belongs to the APM module. Also, a patch was proposed a while back to fix this in a manner that doesn't effect non-broken machines negatively. I don't remember who proposed it, but the name 'John' stands out in my mind. (It may have been Jonathen Lemons...) Unfortunately, I was unable to test it since my new laptop no longer has a problem. 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.3134.821325.222080>