From owner-freebsd-current@FreeBSD.ORG Fri Feb 11 00:21:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AECC216A4CE; Fri, 11 Feb 2005 00:21:09 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id B16B643D3F; Fri, 11 Feb 2005 00:21:08 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Feb 2005 00:21:08 +0000 (GMT) To: Skip Ford In-Reply-To: Your message of "Thu, 10 Feb 2005 19:02:24 EST." <20050211000224.GA717@lucy.pool-70-104-70-104.pskn.east.verizon.net> Date: Fri, 11 Feb 2005 00:21:04 +0000 From: Ian Dowse Message-ID: <200502110021.aa31278@salmon.maths.tcd.ie> cc: Jeremie Le Hen cc: current@FreeBSD.org cc: John Baldwin Subject: Re: Console freeze but still alive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 11 Feb 2005 00:21:09 -0000 In message <20050211000224.GA717@lucy.pool-70-104-70-104.pskn.east.verizon.net> , Skip Ford writes: >Jeremie Le Hen wrote: >> > Ive found that it is not 100% certain to freeze which has made my >> > testing so far worthless. :( >> > I have applied Ian's callout patch and after about a dozen reboots the >> > console has not stopped. It looks promising so far but I will keep my >> > eye on it. >> >> Same thing here. I switched between console and X a few times, played >> with my mouse in console mode and used my computer for a while, and I've >> not seen a console freeze yet. But I have not been able to guess how >> to repeat the problem, so ... I'll go on using my computer :-). > >Are either of you using a splash screen? > >I've found that an unpatched tree using splash_bmp, if the image >can't be displayed then the console eventually messes up in the >way I described. If it can be displayed, the console continues to >work fine. > >Using the patch he posted, it works correctly either way. Patch committed - thanks for the quick testing and feedback! Ian