From owner-freebsd-current@FreeBSD.ORG Thu Feb 10 23:34:20 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 D562116A4CE for ; Thu, 10 Feb 2005 23:34:20 +0000 (GMT) Received: from out004.verizon.net (out004pub.verizon.net [206.46.170.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id D58FD43D3F for ; Thu, 10 Feb 2005 23:34:19 +0000 (GMT) (envelope-from skip.ford@verizon.net) Received: from pool-70-104-70-104.pskn.east.verizon.net ([70.104.70.104]) by out004.verizon.netESMTP <20050210233419.BVSY15146.out004.verizon.net@pool-70-104-70-104.pskn.east.verizon.net>; Thu, 10 Feb 2005 17:34:19 -0600 Date: Thu, 10 Feb 2005 18:34:18 -0500 From: Skip Ford To: Ian Dowse Message-ID: <20050210233418.GA683@lucy.pool-70-104-70-104.pskn.east.verizon.net> Mail-Followup-To: Ian Dowse , Jonathan Fosburgh , haro@kgt.co.jp, freebsd-current@freebsd.org, jeremie@le-hen.org References: <20050210210002.GA679@lucy.pool-70-104-70-104.pskn.east.verizon.net> <200502102216.ab00205@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502102216.ab00205@salmon.maths.tcd.ie> User-Agent: Mutt/1.4.2.1i X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [70.104.70.104] at Thu, 10 Feb 2005 17:34:19 -0600 cc: jeremie@le-hen.org cc: haro@kgt.co.jp cc: freebsd-current@freebsd.org cc: Jonathan Fosburgh 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: Thu, 10 Feb 2005 23:34:21 -0000 Ian Dowse wrote: > In message <20050210210002.GA679@lucy.pool-70-104-70-104.pskn.east.verizon.net> > , Skip Ford writes: >>Ian Dowse wrote: >>> FYI, I saw something similar once when I was testing my recent >>> callout changes, but I haven't seen it happen since. If the problem >>> did just appear around Sunday/Monday then I guess it could be >>> related... >> >>Yes, reverting your callout changes fixes the problem for me. >> >>In my case, with your changes the console worked fine unless I >>started X. When switching from or exiting X, the screen would >>stay blank. The shell still works at that point, I just couldn't >>see it. >> >>Changing video modes with vidcontrol didn't help. My startup >>scripts do change the video mode for all screens. I don't use >>moused at all FWIW. > > Thanks for the information. Could you try the following patch? It's > probably unlikely to help, but is the only potential issue I've > spotted so far. I think it worked but now I can't be sure. The screen behaves correctly when booting with your patch, but now it also seems to be working correctly without it. All of a sudden, I can't get any kernel to behave incorrectly, even though it did that consistenly over the last few days. -- Skip