Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Mar 2008 09:20:28 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        "Igor Mozolevsky" <igor@hybrid-lab.co.uk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Compiling 6.3->7: lapic frequency madness
Message-ID:  <200803190920.28633.jhb@freebsd.org>
In-Reply-To: <a2b6592c0803181225q124ef663xa8c677fadbb2a33e@mail.gmail.com>
References:  <a2b6592c0803151921rdc78b37reea65fef221ca153@mail.gmail.com> <200803181324.51136.jhb@freebsd.org> <a2b6592c0803181225q124ef663xa8c677fadbb2a33e@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 18 March 2008 03:25:00 pm Igor Mozolevsky wrote:
> On 18/03/2008, John Baldwin <jhb@freebsd.org> wrote:
> > On Tuesday 18 March 2008 11:49:29 am Igor Mozolevsky wrote:
> >  > On 18/03/2008, John Baldwin <jhb@freebsd.org> wrote:
> >  > > First, which one is broken?  Have you tried a RELENG_7_0 kernel and
> >  > > does
> >
> >  it do
> >
> >  > >  the same as a release CD kernel?
> >  >
> >  > Tried both ISO image and RELENG_7_0, they both work ok, but RELENG_7
> >
> >  doesn't...
> >
> >
> > Ok, and it is cpufreq related?  Which cpufreq drivers are attaching to
> > your CPU?
>
> 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?

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803190920.28633.jhb>