From owner-freebsd-arch@FreeBSD.ORG Sun Oct 30 10:48:15 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A502E16A41F for ; Sun, 30 Oct 2005 10:48:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DD5443D46 for ; Sun, 30 Oct 2005 10:48:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 39E491A3C1A; Sun, 30 Oct 2005 02:48:15 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AB2A151376; Sun, 30 Oct 2005 05:48:14 -0500 (EST) Date: Sun, 30 Oct 2005 05:48:14 -0500 From: Kris Kennaway To: "M. Warner Losh" Message-ID: <20051030104814.GA32477@xor.obsecurity.org> References: <12768156.1130520253107.JavaMail.root@vms073.mailsrvcs.net> <200510281435.41700.jhb@freebsd.org> <4362B611.B4A12AF8@verizon.net> <20051028.215049.102576958.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <20051028.215049.102576958.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i Cc: gbergling@0xfce3.net, babkin@users.sourceforge.net, babkin@verizon.net, phk@phk.freebsd.dk, freebsd-arch@freebsd.org Subject: Re: wscons for FreeBSD? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:48:15 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 28, 2005 at 09:50:49PM -0600, M. Warner Losh wrote: > In message: <4362B611.B4A12AF8@verizon.net> > Sergey Babkin writes: > : John Baldwin wrote: > : >=20 > : > On Friday 28 October 2005 01:24 pm, Sergey Babkin wrote: > : > > >From: John Baldwin > : > > > > :=20 > : > > * When entering panic/debugger mode the console > : > > should reset its video mode to the one where > : > > the panic information is visible. > : >=20 > : > I think this might be kind of hard since you really don't know what X= has done > : > to the hardware unless you make X talk to the console driver to do > : > everything. > :=20 > : Can you re-initialize the device from scratch? My knowledge > : about the video hardware dates to SVGA times and even that > : is not too deep. > :=20 > : Maybe provide a basic SVGA re-initialization routine on x86 and have > : an interface for the third-party in-kernel drivers that > : would contain the re-initialization routine. >=20 > When this has come up in the past, those in the know say that it takes > card specific registers and knowledge to reset these cards' video > modes. Even if it doesn't work on all cards, if there's some method that will at least work for a subset of configurations it may be worth investigating: by that point the machine has panicked anyway, so what's the worst that can happen? Kris --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZKTuWry0BWjoQKURAi+4AKD2Dn4NElcm2UoiJ89tgr5xNla5mACg3QPc cApA2hb9fnvMD7dNeVIEdUs= =GwCl -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--