From owner-freebsd-current@FreeBSD.ORG  Tue Oct  9 08:18:52 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 04FC216A41A
	for <freebsd-current@freebsd.org>; Tue,  9 Oct 2007 08:18:52 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx1.freebsd.org (Postfix) with ESMTP id 7448013C43E;
	Tue,  9 Oct 2007 08:18:50 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <470B396A.5030400@FreeBSD.org>
Date: Tue, 09 Oct 2007 10:18:50 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@deepcore.dk>
References: <48190.89022.qm@web53907.mail.re2.yahoo.com>
	<470B1DB1.1030700@deepcore.dk>
In-Reply-To: <470B1DB1.1030700@deepcore.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Dave Frantz <imperial_courier@yahoo.com>, Kip Macy <kip.macy@gmail.com>,
	freebsd-current@freebsd.org
Subject: Re: FreeBSD 7.0-current Locks During Device Probe--Solved
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2007 08:18:52 -0000

Søren Schmidt wrote:
> Dave Frantz wrote:
>> I finally figured out what was causing FreeBSD 7.0-current to crash on 
>> my machine during the device probe. It turns out that if options 
>> CPUFREQ is compiled in, the system will not boot. However, it can be 
>> safely kldloaded in later.
>>
>> I'm not entirely sure why my system dislikes CPUFREQ, but I can live 
>> without it. If you guys have any questions or anything, just let me know.
> Thanks for the report!
> 
> I've had problems with cpufreq before, but that was when running gdm, it 
> would lock the system solid if loaded before gdm was started but worked 
> fine afterwards.

The only problems I had were to do with acpi throttling in conjunction 
with cpufreq, which would hang my dual core opteron.  Unfortunately I 
have forgotten the tunable to disable this but you should be able to 
google for it.  Disabling acpi would also do it with a sledgehammer on i386.

Kris