Date: Mon, 24 Mar 2008 14:18:38 +0000 From: "Igor Mozolevsky" <igor@hybrid-lab.co.uk> To: freebsd-current@freebsd.org Subject: Re: Compiling 6.3->7: lapic frequency madness Message-ID: <a2b6592c0803240718y1620e99hbfe1a9d4402c2003@mail.gmail.com> In-Reply-To: <200803190920.28633.jhb@freebsd.org> References: <a2b6592c0803151921rdc78b37reea65fef221ca153@mail.gmail.com> <200803181324.51136.jhb@freebsd.org> <a2b6592c0803181225q124ef663xa8c677fadbb2a33e@mail.gmail.com> <200803190920.28633.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/03/2008, John Baldwin <jhb@freebsd.org> wrote: > > On Tuesday 18 March 2008 03:25:00 pm Igor Mozolevsky wrote: > > > Well, I wouldn't say I'm sure it's 100% cpufreq related, but removing > > it from the kernel fixes the problem... It's also possible that > > cpufreq is interfering with something else... Anyhow, I've got both > > est and p4tcc attaching. > > > Can you try disabling one or the other to see if it's limited to one > driver? For the benefit of the rest of the list, since as I replied to jhb only by mistake: hint.est.0.disabled="1" seems to give lapic frequency within a reasonable range. cheers, Igor :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a2b6592c0803240718y1620e99hbfe1a9d4402c2003>