From owner-freebsd-current@FreeBSD.ORG Tue Aug 26 23:44:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF45C16A4BF for ; Tue, 26 Aug 2003 23:44:17 -0700 (PDT) Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A97C43FF3 for ; Tue, 26 Aug 2003 23:44:15 -0700 (PDT) (envelope-from welchsm@earthlink.net) Received: from fozzie.psp.pas.earthlink.net ([207.217.78.218]) by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19ru2L-0000qM-00; Tue, 26 Aug 2003 23:44:09 -0700 Received: from [207.217.78.11] by EarthlinkWAM via HTTP; Tue Aug 26 23:44:09 PDT 2003 Message-ID: <3560563.1061966649778.JavaMail.nobody@fozzie.psp.pas.earthlink.net> Date: Tue, 26 Aug 2003 23:42:52 -0500 (GMT) From: Sean Welch To: Glenn Johnson , Eric Anholt , Vulpes Velox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Web Access Mail version 3.0 cc: freebsd-current@freebsd.org Subject: Re: Radeon 7500 w/ DRI locking on restart of X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2003 06:44:17 -0000 Okay, one more message before I *finally* go to bed. I got kind of excited by the stuff below... I decided to update my DRI install to see if things would improve. Now 4.8-RELEASE responds to the forcepcimode option nearly as well as 5.1-RELEASE does for me! I thought I had it made -- I've even found that a resume from hard drive with DRI enabled doesn't lock the machine!! That has *NEVER* worked before! Then I tried a switch to a virtual terminal and back. I get a corrupted color map with lock followed shortly thereafter by a reboot. I booted up under 5.1 and verified that this does *not* happen there. I didn't try a suspend/resume sequence there but I expect it works there as well. I'm guessing this is just a glitch in the DRI CVS code at the moment. The source is from around 9 08/26/03 and the output of 'dmesg | grep drm' is: drm0: port 0xcc00-0xccff mem 0xfcff0000-0xfcffffff,0xe0000000-0xe7ffffff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe8000000 64MB info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 It also seems that in most cases the performance hit is not as great as I had thought. If this works as well on the desktop machines I think I can work around the vt switching issue for the moment. Does any of this suggest anything to you, Eric? Anything I can help test? Sean