From owner-freebsd-current@FreeBSD.ORG Fri Feb 11 00:02:26 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 18B6116A4CE; Fri, 11 Feb 2005 00:02:26 +0000 (GMT) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87D0443D3F; Fri, 11 Feb 2005 00:02:25 +0000 (GMT) (envelope-from skip.ford@verizon.net) Received: from pool-70-104-70-104.pskn.east.verizon.net ([70.104.70.104]) by out005.verizon.netESMTP <20050211000224.MGVL6130.out005.verizon.net@pool-70-104-70-104.pskn.east.verizon.net>; Thu, 10 Feb 2005 18:02:24 -0600 Date: Thu, 10 Feb 2005 19:02:24 -0500 From: Skip Ford To: Jeremie Le Hen Message-ID: <20050211000224.GA717@lucy.pool-70-104-70-104.pskn.east.verizon.net> References: <200502090737.36020.syjef@mdanderson.org> <200502101420.35641.jhb@FreeBSD.org> <20050210200259.GA31485@thingy.tbd.co.nz> <200502101513.48491.jhb@FreeBSD.org> <20050210231723.GB31485@thingy.tbd.co.nz> <20050210232028.GJ82324@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050210232028.GJ82324@obiwan.tataz.chchile.org> User-Agent: Mutt/1.4.2.1i X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [70.104.70.104] at Thu, 10 Feb 2005 18:02:24 -0600 cc: Ian Dowse 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:02:26 -0000 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. -- Skip