From owner-freebsd-current@FreeBSD.ORG Fri Nov 7 13:40: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 08BAF16A4CE for ; Fri, 7 Nov 2003 13:40:17 -0800 (PST) Received: from lewis.lclark.edu (nedc.org [149.175.1.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 6694843FAF for ; Fri, 7 Nov 2003 13:40:16 -0800 (PST) (envelope-from eta@lclark.edu) Received: from [149.175.34.27] ([149.175.34.27]) by lewis.lclark.edu (SAVSMTP 3.1.1.32) with SMTP id M2003110713400716153 ; Fri, 07 Nov 2003 13:40:07 -0800 From: Eric Anholt To: Ralf Folkerts In-Reply-To: <31371.1068240189@www55.gmx.net> References: <31371.1068240189@www55.gmx.net> Content-Type: text/plain Message-Id: <1068241207.684.8.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 07 Nov 2003 13:40:07 -0800 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Radeon DRM-Problem 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: Fri, 07 Nov 2003 21:40:17 -0000 On Fri, 2003-11-07 at 13:23, Ralf Folkerts wrote: > Hi, > > I have a Problem with DRM (Radeon) on my "Current"-Box. > > I cvsuped and made my last buildworld/-kernel/installkernel/-world last week > (Oct 31). > > FreeBSD penguin.home.folkerts-net.de 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri > Oct 31 20:04:27 CET 2003 > toor@penguin.home.folkerts-net.de:/usr/obj/usr/src/sys/PENGUINKERNEL i386 > > >From this List I think this Problem should have been fixed a while ago?! > > When starting X I get > > agp0: binding memory at bad offset 0 > error: [drm:pid704:radeon_cp_init] *ERROR* radeon_cp_init called without > lock held > error: [drm:pid704:radeon_unlock] *ERROR* Process 704 using kernel context 0 > > on the Console. When I then shutdown X and start it up again I don't get any > display any > longer (however, the machine still works and i.e. can be shutdown -r now, > but w/o seing > anything until the reboot). > > Pls note: Except for these Problems (Lock when restarting X and no DRM) X > runs nice and w/o > any other Problems! > > Does anyone have a hint? Did I shred my Config(s)? Or is this a real > Problem? Linux users have also been experiencing those *ERROR* messages. I'm not sure what's going on here. I don't think the hangs are related to the error, since Linux people haven't been complaining about hangs. The agp message, however, is something I haven't seen or heard about before. What does dmesg| grep agp say? -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org