From owner-freebsd-current@FreeBSD.ORG Fri Sep 18 13:53:50 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 3898E10656C3 for ; Fri, 18 Sep 2009 13:53:50 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id F28458FC26 for ; Fri, 18 Sep 2009 13:53:49 +0000 (UTC) Received: from [192.168.1.4] (adsl-241-169-177.bna.bellsouth.net [74.241.169.177]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n8IDrk5v041232 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 18 Sep 2009 09:53:48 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Kostik Belousov In-Reply-To: <1253280980.2038.1148.camel@balrog.2hip.net> 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> <20090918075117.GK47688@deviant.kiev.zoral.com.ua> <1253280980.2038.1148.camel@balrog.2hip.net> Content-Type: text/plain Organization: FreeBSD Date: Fri, 18 Sep 2009 08:53:41 -0500 Message-Id: <1253282021.2038.1168.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net 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 13:53:50 -0000 On Fri, 2009-09-18 at 08:36 -0500, Robert Noland wrote: > On Fri, 2009-09-18 at 10:51 +0300, Kostik Belousov wrote: > > 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. > > > > > > > > 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(). > > > > > > 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 ? > > Yes, on my boards I have something like the following: > > 0x0/0x100000000 BIOS write-back set-by-firmware active > > The specs state that we cannot overlap WC on this, so without being able > to split the above variable MTRR, setting WC always fails. It is > further complicated by the fact that we only have 7 variable MTRR > registers to work with. It is valid to set WB using PAT though. ^WC robert. > robert. > > > > 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. -- Robert Noland FreeBSD