From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 06:20:35 2007 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 61F5516A418 for ; Tue, 9 Oct 2007 06:20:35 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id 0231B13C459 for ; Tue, 9 Oct 2007 06:20:34 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.deepcore.dk (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id l996KXjh089976; Tue, 9 Oct 2007 08:20:34 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <470B1DB1.1030700@deepcore.dk> Date: Tue, 09 Oct 2007 08:20:33 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Dave Frantz References: <48190.89022.qm@web53907.mail.re2.yahoo.com> In-Reply-To: <48190.89022.qm@web53907.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Kip Macy , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2007 06:20:35 -0000 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=20 > CPUFREQ is compiled in, the system will not boot. However, it can be=20 > safely kldloaded in later. > > I'm not entirely sure why my system dislikes CPUFREQ, but I can live=20 > without it. If you guys have any questions or anything, just let me kno= w. 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=20 fine afterwards. -S=F8ren