From owner-freebsd-current@FreeBSD.ORG Tue Aug 26 13:54:07 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 4366216A4BF; Tue, 26 Aug 2003 13:54:07 -0700 (PDT) Received: from babyruth.hotpop.com (babyruth.hotpop.com [204.57.55.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76D7E43FAF; Tue, 26 Aug 2003 13:54:06 -0700 (PDT) (envelope-from kitbsdlists@HotPOP.com) Received: from hotpop.com (kubrick.hotpop.com [204.57.55.16]) by babyruth.hotpop.com (Postfix) with SMTP id E985121697B; Tue, 26 Aug 2003 20:54:00 +0000 (UTC) Received: from fortytwo. (ip68-109-49-234.lu.dl.cox.net [68.109.49.234]) by smtp-2.hotpop.com (Postfix) with SMTP id 3FAF11800B5; Tue, 26 Aug 2003 20:53:56 +0000 (UTC) Date: Tue, 26 Aug 2003 20:51:45 -0500 From: Vulpes Velox To: Eric Anholt Message-Id: <20030826205145.2270e05a.kitbsdlists@HotPOP.com> In-Reply-To: <1061929630.620.22.camel@leguin> References: <1773423.1061925721167.JavaMail.nobody@kermit.psp.pas.earthlink.net> <20030826200552.68dd58ec.kitbsdlists@HotPOP.com> <1061929630.620.22.camel@leguin> X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Sean_Welch@alum.wofford.org cc: welchsm@earthlink.net 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2003 20:54:07 -0000 On Tue, 26 Aug 2003 13:27:11 -0700 Eric Anholt wrote: > On Tue, 2003-08-26 at 18:05, Vulpes Velox wrote: > > I had similar problem with a 7200 and OGL. I solved the problem by turning > > off some of the options in the X config. > > > > On Tue, 26 Aug 2003 12:21:56 -0500 (GMT) > > Sean Welch wrote: > > > > > Is anyone else seeing this issue? I'm running into it > > > on desktop boxes and a laptop running 4.8-RELEASE with > > > up to date ports collections and various versions of > > > DRI installed over a ports version of X. I'm also seeing > > > this under 5.1-RELEASE on the laptop. > > > > > > Everything works perfectly unless/until I restart the X > > > server. This appears to be initiated automatically when > > > running GDM -- ie, GDM starts, you log in using that X > > > session, you log out and the session stops, GDM starts X > > > again and displays the login screen. > > > > > > This seems to happen a bit more than 1/3 of the times I > > > try it (intentionally or not). It isn't much of a problem > > > on the laptop as I'm the only user and tend to turn the > > > machine off when I log out but it is causing all sorts of > > > issues on the desktops because they are intended to be > > > used as multi-user (serially and also simultaneously) > > > systems. > > > > > > Any ideas? The instability goes away completely with DRI > > > disabled, but part of the use of these desktops is in the > > > accelerated OpenGL rendering... > > > > > > Sean > > (CC'ed to -current since it's not -stable specific) > > This is an example of why people need to send PRs and not just emails. > I realize now I've seen emails on this before, but I had forgotten about > them because they seemed isolated and I didn't have them piling up in my > assigned prs list (things pile up in my mailboxes easily, and I don't go > back and check very often). > > I've tried to reproduce this with a radeon, by doing startx, C-A-B to > kill the server, then startx again. The second time, the screen > displays for a brief moment then goes black. The system isn't hung, and > I can exit using C-A-B again. Is this what everyone else sees? > > Everyone that's experiencing this and is using the DRI, what version of > the radeon DRM is loaded? (dmesg | grep drm) Is anyone experiencing > this without the DRI loaded? The ForcePCIMode workaround is > interesting, I'll take a look at what could be going on there. drm0: port 0x9800-0x98ff mem 0xdfe80000-0xdfefffff,0xd8000000-0xdbffffff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe0000000 64MB info: [drm] Initialized radeon 1.8.0 20020828 on minor 0