From owner-freebsd-current@FreeBSD.ORG Thu Feb 10 21:00:06 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 8FE3E16A4CE for ; Thu, 10 Feb 2005 21:00:06 +0000 (GMT) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7ACB43D1D for ; Thu, 10 Feb 2005 21:00:03 +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 <20050210210003.JMWV6130.out005.verizon.net@pool-70-104-70-104.pskn.east.verizon.net>; Thu, 10 Feb 2005 15:00:03 -0600 Date: Thu, 10 Feb 2005 16:00:02 -0500 From: Skip Ford To: Ian Dowse Message-ID: <20050210210002.GA679@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: <200502090737.36020.syjef@mdanderson.org> <200502091724.ab92170@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502091724.ab92170@salmon.maths.tcd.ie> 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 15:00:02 -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 21:00:06 -0000 Ian Dowse wrote: > In message <200502090737.36020.syjef@mdanderson.org>, Jonathan Fosburgh writes: > >I'm running -current as of yesterday and having the same problem. X is > >working fine for me, I just can't make use of any of /dev/ttyv*. WHen I sh>ut > >the system down I do notice that all of the output suddenly appears and I c>an > >watch the shutdown generally from about the point disks start to sync. This> > >is on an old HP Kayak workstation. > > 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. -- Skip, who doesn't work for Verizon.