From owner-freebsd-current@FreeBSD.ORG Fri Sep 18 07:51:23 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 2B8ED1065670; Fri, 18 Sep 2009 07:51:23 +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 9DFA98FC08; Fri, 18 Sep 2009 07:51:22 +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 n8I7pHsC047096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Sep 2009 10:51:17 +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 n8I7pHZa077439; Fri, 18 Sep 2009 10:51:17 +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 n8I7pH6C077438; Fri, 18 Sep 2009 10:51:17 +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: Fri, 18 Sep 2009 10:51:17 +0300 From: Kostik Belousov To: Robert Noland Message-ID: <20090918075117.GK47688@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> <20090917182810.GG47688@deviant.kiev.zoral.com.ua> <1253214222.2038.18.camel@balrog.2hip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2IWEGlOlRvYPWKAG" Content-Disposition: inline In-Reply-To: <1253214222.2038.18.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: Fri, 18 Sep 2009 07:51:23 -0000 --2IWEGlOlRvYPWKAG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 17, 2009 at 02:03:42PM -0500, Robert Noland wrote: > On Thu, 2009-09-17 at 21:28 +0300, Kostik Belousov wrote: > > I spent some time with David looking at the debugging information. > > In particular, David has access to the serial console on the machine. > >=20 > > 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. > >=20 > > 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(). >=20 > I'm not certain what to suggest here. MTRR is fail on almost every > newer board that I have, due to the fact that the BIOS sets a global WB > MTRR, which we don't have the ability to split or overlap. In any case Could you, please, give me some more details ? On the machine I am writing this from, default MTRR settings for uncovered region are UC. Also, there is a variable MTRR covering whole region of RAM from 1M to the end of physical RAM as WB. Is this what you mean ? > every MTRR attempt by X/drm is to set WC. I have easily produced hard > system lockups by attempting to manually manipulate MTRRs via > memcontrol, even to states that should be valid. This is one of the > many reasons that I'm trying to move to using PAT for everything. If > the attempt to set MTRR is not failing and returning an appropriate > error, that could very well be the source of the lockup. --2IWEGlOlRvYPWKAG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqzO/QACgkQC3+MBN1Mb4j/YgCg0TMwK/of4MDa9JzbJkAHZOlL zjoAn1xlQAdxWS/pDqHOdEggnA478jK7 =8YXo -----END PGP SIGNATURE----- --2IWEGlOlRvYPWKAG--