From owner-freebsd-current@FreeBSD.ORG Wed Mar 19 13:24:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E101C106566C for ; Wed, 19 Mar 2008 13:24:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D23DE8FC1A for ; Wed, 19 Mar 2008 13:24:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id D93D61A4D86; Wed, 19 Mar 2008 06:23:34 -0700 (PDT) From: John Baldwin To: "Igor Mozolevsky" Date: Wed, 19 Mar 2008 09:20:28 -0400 User-Agent: KMail/1.9.7 References: <200803181324.51136.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803190920.28633.jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Compiling 6.3->7: lapic frequency madness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2008 13:24:58 -0000 On Tuesday 18 March 2008 03:25:00 pm Igor Mozolevsky wrote: > On 18/03/2008, John Baldwin wrote: > > On Tuesday 18 March 2008 11:49:29 am Igor Mozolevsky wrote: > > > On 18/03/2008, John Baldwin 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