From owner-freebsd-stable@FreeBSD.ORG Tue Dec 14 06:47:25 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F2C416A4CE for ; Tue, 14 Dec 2004 06:47:25 +0000 (GMT) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96BF343D46 for ; Tue, 14 Dec 2004 06:47:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iBE6lMqT014208 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 14 Dec 2004 17:47:22 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iBE6lLxP088633; Tue, 14 Dec 2004 17:47:22 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iBE6lLIN088632; Tue, 14 Dec 2004 17:47:21 +1100 (EST) (envelope-from pjeremy) Date: Tue, 14 Dec 2004 17:47:21 +1100 From: Peter Jeremy To: Doug White Message-ID: <20041214064721.GI804@cirb503493.alcatel.com.au> References: <20041213190532.GA4781@meer.net> <20041213183518.N97507@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041213183518.N97507@carver.gumbysoft.com> User-Agent: Mutt/1.4.2i cc: Joe Rhett cc: freebsd-stable@freebsd.org Subject: Re: is rebooting after a page fault disabled in 5.3-release? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 06:47:25 -0000 On Mon, 2004-Dec-13 18:37:29 -0800, Doug White wrote: >I in fact tested this on Saturday and it in fact rebooted. With GENERIC, >even. The digi driver sort of got left behind with the tty changes and >handed out uninitialized mutexes that trip null pointer panics. Machine >came back up fine, so unless you have some type of panic that screws up >the system enough to disrupt booting then it should work. I missed the previous reference to digi(4). Check out http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/72436 which includes a patch to fix this. -- Peter Jeremy