From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 20:51:18 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0240416A47B for ; Sat, 9 Dec 2006 20:51:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B5043CA0 for ; Sat, 9 Dec 2006 20:50:11 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 91DE346D08; Sat, 9 Dec 2006 15:51:16 -0500 (EST) Date: Sat, 9 Dec 2006 20:51:16 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Maxim Konovalov In-Reply-To: <20061209195519.B60055@mp2.macomnet.net> Message-ID: <20061209204924.N9926@fledge.watson.org> References: <52944.192.168.1.110.1165679313.squirrel@yal.hopto.org> <20061209195519.B60055@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, yal Subject: Re: CURRENT freezes on Laitude D520 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: Sat, 09 Dec 2006 20:51:18 -0000 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