Date: Fri, 18 Sep 2009 10:51:17 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Robert Noland <rnoland@freebsd.org> Cc: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net>, freebsd-current@freebsd.org Subject: Re: misc/compat6x port no longer sufficient for DRI under head? Message-ID: <20090918075117.GK47688@deviant.kiev.zoral.com.ua> In-Reply-To: <1253214222.2038.18.camel@balrog.2hip.net> References: <20090917134924.GZ1212@albert.catwhisker.org> <b269bc570909170832u792f851fk4ace6bfa4c9a7321@mail.gmail.com> <1253208550.49704.4014.camel@balrog.2hip.net> <200909172010.22513.mel.flynn%2Bfbsd.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>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090918075117.GK47688>