From owner-freebsd-x11@FreeBSD.ORG Thu Oct 1 10:16:40 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E339F106566B for ; Thu, 1 Oct 2009 10:16:39 +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 B26DB8FC08 for ; Thu, 1 Oct 2009 10:16:39 +0000 (UTC) Received: from [192.168.1.4] (adsl-157-40-167.bna.bellsouth.net [70.157.40.167]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n91AGZw9091748 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 1 Oct 2009 06:16:37 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Richard Kolkovich In-Reply-To: <20091001021855.GE36488@magus.portal.sigil.org> References: <1253897144.2065.150.camel@balrog.2hip.net> <20090925173416.GF61689@divination.portal.sigil.org> <1253915723.2145.53.camel@balrog.2hip.net> <20090926001158.GA42914@divination.portal.sigil.org> <1253925689.2065.81.camel@balrog.2hip.net> <20090926045706.GB42914@divination.portal.sigil.org> <1253977337.2048.17.camel@balrog.2hip.net> <1253993801.2048.295.camel@balrog.2hip.net> <20090926194802.GA67832@divination.portal.sigil.org> <1254001621.2048.431.camel@balrog.2hip.net> <20091001021855.GE36488@magus.portal.sigil.org> Content-Type: text/plain Organization: FreeBSD Date: Thu, 01 Oct 2009 05:16:30 -0500 Message-Id: <1254392190.98309.750.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=-2.1 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: freebsd-x11@freebsd.org Subject: Re: HD4550 DRI issues X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2009 10:16:40 -0000 On Wed, 2009-09-30 at 21:18 -0500, Richard Kolkovich wrote: > On Sat, Sep 26, 2009 at 04:47:01PM -0500, Robert Noland wrote: > > > > Ok, that eliminates everything to do with the card and X. Let me talk > > to some folks and see if we can figure out where to go from here... I'm > > wondering if this might be BIOS or CPU related now... > > > > Any ideas yet? For some reason, I now need to disable mtrr for my nvidia-driver to work (the card > my 4550 is hopefully replacing...I'm having other issues with nvidia-driver and would prefer an > open-source solution). I don't think I've tried the radeon with mtrr disabled. > > My 30 day return window on this card is almost up, so I may end up returning it if we can't figure > this out. Apparently, a different card wouldn't help, either. :-\ All of the evidence suggests that this has nothing to do with the card. Basically, with the test program the only card specific things that happen are those that happen at driver load time. We haven't even told the card about the memory that we have allocated yet. It has been suggested that it might be a bug in drm's mmap routine, but I can't find it at this point. It has also been suggested that you run memcheck to verify the ram, but since things seem to be correct from the kernel perspective, I don't think that is the issue. The mtrr issue, might be a clue though. It sets the caching mode for the memory allocation. I'm mostly using PAT now, (particularly with the patch that I gave you). Did you send me a "memcontrol list", I don't recall at this point. The x58 appears to deal with memory rather differently than traditional chipsets, so I wonder if it might not be a chipset or BIOS bug. As for nvidia, you can always use nouveau. That will (*should*) get you EXA and Xv acceleration, but not 3d at this point. Follow the instructions in the xf86-video-nouveau for getting my kernel patch how to set things up. However, that driver also uses scatter-gather memory, perhaps even more so than the radeon driver. So, given what we have seen so far, I don't know that it will not produce corruption or possibly worse. I've spent a fair amount of time digging through the mmap and memory allocation bits in the kernel, but haven't found anything that looks wrong. What I don't understand is, why this doesn't effect all or at least all i386 systems. So, I think it almost has to be chipset specific. .... Well, I just went back and found one of the prior reports of this. It looks like that (assuming it is the same cause) was on an intel 945 chipset running 7.2-RELEASE i386. Have you considered running amd64? Your i7 is certainly worthy of it and I would be curious to see if the problem exists when running amd64 also. robert. > > Thanks, > -- Robert Noland FreeBSD