Date: Sat, 9 Dec 2006 20:51:16 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Maxim Konovalov <maxim@macomnet.ru> Cc: freebsd-current@freebsd.org, yal <yal@yal.hopto.org> Subject: Re: CURRENT freezes on Laitude D520 Message-ID: <20061209204924.N9926@fledge.watson.org> In-Reply-To: <20061209195519.B60055@mp2.macomnet.net> References: <52944.192.168.1.110.1165679313.squirrel@yal.hopto.org> <20061209195519.B60055@mp2.macomnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 9 Dec 2006, Maxim Konovalov wrote: > On Sat, 9 Dec 2006, 16:48+0100, yal wrote: > >> Last kernel compilation working was on november 27th. Dell Latitude D520 >> freezes within a few minutes after boot. No errors are show in dmesg. The >> internal speaker sounds and acpi stops working. > > Try with > > debug.mpsafenet="0" > > in /boot/loader.conf. I have similar symptoms with my with my sony > pcg505bx. Please report back your experience. While this may be useful in doing some initial debugging and working around the problem, I'd really appreciate it if people didn't run with debug.mpsafenet="0" for any extended period, as it masks bugs rather than fixing them, and results in them not getting fixed. It also leads to a significant performance hit, and we really don't want people running with debugging features like this turned on by default; I'd rather they used the cycles on INVARIANTS and WITNESS. Do you have any information about the actual source of this problem? Would it motivate solving the problem if I were to remove the debug.mpsafenet tunable? :-) Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061209204924.N9926>