Date: Tue, 09 Oct 2007 10:18:50 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@deepcore.dk> 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 Message-ID: <470B396A.5030400@FreeBSD.org> In-Reply-To: <470B1DB1.1030700@deepcore.dk> References: <48190.89022.qm@web53907.mail.re2.yahoo.com> <470B1DB1.1030700@deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?470B396A.5030400>