Date: Thu, 6 Apr 2000 11:10:26 -0600 (MDT) From: Nate Williams <nate@yogotech.com> To: "Jose M. Alcaide" <jose@we.lc.ehu.es> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: proposal of a better solution for "statclock broken" laptops Message-ID: <200004061710.LAA22387@nomad.yogotech.com> In-Reply-To: <38ECA91E.F98AE48@we.lc.ehu.es> References: <38ECA91E.F98AE48@we.lc.ehu.es>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Moved to -mobile only ] > Some laptops suffer of the "statclock broken" problem: APM suspend > does not work while the RTC is generating periodic interrupts (which > are used for the statistical clock). Currently, the "solution" consists > of setting the 0x20 flag for the apm(4) driver. If this flag is set, > the cpu_initclocks() routine in sys/i386/isa/clock.c does not > initialize the statclok at all. As a consequence, the functionality > of the statclock is lost. > > I tried another solution which seems to work for my laptop (a Dell I3.7k). This is good stuff Jose. Unfortunately, as the author and bug-finder of the original 'broken statclock' code, I don't have time to delve into if your new solution works. Partly because the machine in question is no longer in my service, and partly because I don't have time to do '-current' development anymore. Note also that someone (you?) sent a patch a few days ago that caused the statclock to start working again due to a missing read call to the interrupt, which also might fix it. I don't have the reference handy, but it may be that the statclock has worked the entire time, it just that something forgot to read a critical register. Ahh, it was *you* that proposed the fix, and later assigned it to Bruce. Can you tell me what is different about the fix you posted in your PR vs. this one? Finally, not having the statclock is *really* not that big of a deal. It makes for better heuristics in the scheduler, but in fact makes very little difference in most machines as far as performance goes. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004061710.LAA22387>