From owner-freebsd-current@FreeBSD.ORG Thu Sep 17 18:28:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADCD3106566B; Thu, 17 Sep 2009 18:28:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 45EE38FC1A; Thu, 17 Sep 2009 18:28:17 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n8HISBUq095423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2009 21:28:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n8HISBAt072762; Thu, 17 Sep 2009 21:28:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n8HISA50072761; Thu, 17 Sep 2009 21:28:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 17 Sep 2009 21:28:10 +0300 From: Kostik Belousov To: Robert Noland Message-ID: <20090917182810.GG47688@deviant.kiev.zoral.com.ua> References: <20090917134924.GZ1212@albert.catwhisker.org> <1253208550.49704.4014.camel@balrog.2hip.net> <200909172010.22513.mel.flynn+fbsd.current@mailing.thruhere.net> <1253211613.49704.4073.camel@balrog.2hip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s+08+7ZBU1+8TAHN" Content-Disposition: inline In-Reply-To: <1253211613.49704.4073.camel@balrog.2hip.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Mel Flynn , freebsd-current@freebsd.org Subject: Re: misc/compat6x port no longer sufficient for DRI under head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2009 18:28:17 -0000 --s+08+7ZBU1+8TAHN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 17, 2009 at 01:20:13PM -0500, Robert Noland wrote: > On Thu, 2009-09-17 at 20:10 +0200, Mel Flynn wrote: > > On Thursday 17 September 2009 19:29:10 Robert Noland wrote: > > > On Thu, 2009-09-17 at 08:32 -0700, Freddie Cash wrote: > > > > On Thu, Sep 17, 2009 at 8:29 AM, David Wolfskill=20 > > wrote: > > > > > On Thu, Sep 17, 2009 at 05:04:31PM +0200, Gary Jennejohn wrote: > > > > > > ... > > > > > > Maybe you need to install misc/compat7x also for things to work= with > > > > > > head? Don't forget options COMPAT_FREEBSD7 in your kernconf for > > > > > > head. > > > > > > > > > > > :-) As I was writing the previous message, that thought occurred= , so I > > > > > > > > > > did install it, re-tried, and the symptoms persisted: with DRI en= abled, > > > > > the keyboard & mouse were non-functional; with DRI disabled, Xorg > > > > > worked. > > > > > > > > > > (I had intended to install misc/compat7x under head as soon as it= had > > > > > been committed, but it slipped what passes for my mind. And the = file > > > > > system where /usr/ports lives is not one I normally even mount wh= en > > > > > running head....) > > > > > > > > > > But thanks for the thought! > > > > > > > > Have you tried re-enabling hald and dbus and configuring X to use t= hose? > > >=20 > > > So, the DRI option has absolutely nothing to do with kbd/mouse. I > > > expect that what you are actually seeing is a hard lockup, quite > > > possibly a gpu crash. > >=20 > > If that's the case, having a root vty open before starting X and upon g= pu=20 > > crash, blind type (no cookies for typos!) shutdown -r NOW should= result=20 > > in some /var/log/messages entries at the very least and quite possible = reboot,=20 > > right? >=20 > Maybe... It really depends on exactly what state X has left things in > when it crashed/hung. If X crashes and catches the signals, it should > try to restore the console to a usable state. If it is a gpu crash then > X may still be functioning, but hung on a lock. In this case, you can > generally ssh in or get serial console. It is also possible for > something entirely more evil to occur, such that things get hung with > interrupts disabled which results in a case where nothing but the power > button will remedy it. In any case, if X isn't able to cleanly exit and > call LeaveVT, then your console is likely hosed. I spent some time with David looking at the debugging information. In particular, David has access to the serial console on the machine. I was unable to decide with some certainity what happens, in particular, whether the machine was locked, only X was locked, or just keyboard and mouse input not working. But, the reliable state of the system where it spent quite a time during X startup was mtrr setup. Xorg was sitting in kernel, in i686_mrstore(). It seems that after some time, X starts sleeping in select(2). --s+08+7ZBU1+8TAHN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqyf7oACgkQC3+MBN1Mb4i7FQCgmVkSbV8NV657NrgWuCvnLXGs vRYAmwfG+nf7hY6unxzeqHXcv8w1IVv/ =4djk -----END PGP SIGNATURE----- --s+08+7ZBU1+8TAHN--