From owner-freebsd-x11@FreeBSD.ORG Fri Sep 25 21:55:32 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 D4040106566B for ; Fri, 25 Sep 2009 21:55:32 +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 A5A258FC16 for ; Fri, 25 Sep 2009 21:55:32 +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 n8PLtS60028563 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 25 Sep 2009 17:55:30 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Richard Kolkovich In-Reply-To: <20090925173416.GF61689@divination.portal.sigil.org> References: <20090923210626.GC46493@magus.portal.sigil.org> <1253741283.2031.334.camel@balrog.2hip.net> <20090924145417.GA2539@magus.portal.sigil.org> <1253812603.2031.1528.camel@balrog.2hip.net> <1253814434.2031.1561.camel@balrog.2hip.net> <20090924181427.GD2539@magus.portal.sigil.org> <20090925143910.GD61689@divination.portal.sigil.org> <1253897144.2065.150.camel@balrog.2hip.net> <20090925173416.GF61689@divination.portal.sigil.org> Content-Type: text/plain Organization: FreeBSD Date: Fri, 25 Sep 2009 16:55:23 -0500 Message-Id: <1253915723.2145.53.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.0 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: Fri, 25 Sep 2009 21:55:33 -0000 On Fri, 2009-09-25 at 12:34 -0500, Richard Kolkovich wrote: > On Fri, Sep 25, 2009 at 11:45:44AM -0500, Robert Noland wrote: > > Could you also apply this debugging patch. It should print the kernel > > perspective of things at allocation time to dmesg. > > > > sysctl hw.dri.0: > > hw.dri.0.name: radeon 0xba pci:0000:02:00.0 > hw.dri.0.vm: > slot offset size type flags address mtrr > 0 0x00000000f3ce0000 0x00010000 REG 0x82 0x00000000dc826000 no > 1 0x000000008ec5a000 0x00002000 SHM 0x20 0x000000008ec5a000 no > 2 0x00000000d0000000 0x0fff0000 FB 0x10 0x0000000000000000 yes > 3 0x00000000dc836000 0x00101000 SG 0x0e 0x00000000dc836000 no > 4 0x00000000dc937000 0x00001000 SG 0x0e 0x00000000dc937000 no > 5 0x00000000dc938000 0x00200000 SG 0x00 0x00000000dc938000 no > 6 0x00000000dcb38000 0x01c80000 SG 0x00 0x0000000000000000 no > > hw.dri.0.clients: > a dev pid uid magic ioctls > y dri/card0 2278 0 0 2760 > > hw.dri.0.bufs: > o size count free segs pages kB > 16 65536 32 0 0 0 0 > > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > hw.dri.0.vblank: > crtc ref count last enabled inmodeset > 00 00 00000000 00000000 01 00 > 01 00 00000000 00000000 01 00 > hw.dri.0.debug: 0 > > > dmesg output when drm is loaded: > > drm0: on vgapci0 > info: [drm] MSI enabled 1 message(s) > vgapci0: child drm0 requested pci_enable_busmaster > info: [drm] Initialized radeon 1.31.0 20080613 > info: [drm] SG handle=dc836000, kva=0xdc836000, contents=00000000 So, things are all correct at this point... and not much happens between here and the userland print that show corrupted values. Basically all that happens is an mmap to userspace and print the values from the userspace perspective... You're not the first report that I have had of this. (It doesn't appear to be r600 related at all, IIRC prior reports were on like 9200's) I think it is restricted to PCI/PCI-E radeons, though given where it appears to be happening I don't see any reason that it couldn't effect other cards as well. I'm really not certain how to move forward debugging really, without being able to reproduce it and break out into gdb to try and inspect memory. There is something "special" about your setup, since this seems to be a relatively rare issue. The only other thing that I can think of to do, is to start adding a bunch of debugging into the mmap routines, but that is going to get really noisy. robert. > info: [drm] Setting GART location based on new memory map > info: [drm] Loading RV710 Microcode > info: [drm] Resetting GPU > info: [drm] writeback test succeeded in 1 usecs > drm0: [ITHREAD] > > > xorg log attached > -- Robert Noland FreeBSD