Re: New DRI interface changes landed
On Tue, 2007-10-16 at 20:30 +0200, Vincent Vanackere wrote: On 10/16/07, Michel Dänzer [EMAIL PROTECTED] wrote: On Mon, 2007-10-15 at 19:54 +0200, Vincent Vanackere wrote: (II) AIGLX: enabled GLX_MESA_copy_sub_buffer (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control Update from xserver and mesa Git and try again. [ I had to also update libdrm from git to make everything compile. ] The good news : X doesn't segfault anymore when running compiz... The bad one : I now have another problem and I'm now getting an infinite loop instead (100% cpu taken by Xorg). I'm getting the following message ad nauseam in the logs : tossed event which came in late mieqEnequeue: out-of-order valuator event; dropping. tossed event which came in late mieqEnequeue: out-of-order valuator event; dropping. [...] Here's what I get if I attach a debugger : (gdb) bt #0 0x2aed809c16c7 in ioctl () from /lib/libc.so.6 #1 0x2aed81fc2926 in drmFenceWait (fd=10, flags=value optimized out, fence=0x1611fa0, flush_type=value optimized out) at xf86drm.c:2520 #2 0x2aed9300b9e6 in dri_ttm_fence_wait (fence=0x1611f80) at intel_bufmgr_ttm.c:694 #3 0x2aed92fee12e in intelFinish (ctx=0x15f79a0) at intel_context.c:318 #4 0x2aed8175e8be in __glXDisp_Finish (cl=0x1627f48, pc=value optimized out) at ../../../GL/glx/single2.c:238 Looks like a GPU lockup. Does this also happen if you use the i915 kernel module from your kernel instead of from drm Git? The Mesa i915 driver is currently very slow using the TTM due to issues to be worked out in the DRM anyway. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: New DRI interface changes landed
2007/10/17, Michel Dänzer [EMAIL PROTECTED]: Here's what I get if I attach a debugger : (gdb) bt #0 0x2aed809c16c7 in ioctl () from /lib/libc.so.6 #1 0x2aed81fc2926 in drmFenceWait (fd=10, flags=value optimized out, fence=0x1611fa0, flush_type=value optimized out) at xf86drm.c:2520 #2 0x2aed9300b9e6 in dri_ttm_fence_wait (fence=0x1611f80) at intel_bufmgr_ttm.c:694 #3 0x2aed92fee12e in intelFinish (ctx=0x15f79a0) at intel_context.c:318 #4 0x2aed8175e8be in __glXDisp_Finish (cl=0x1627f48, pc=value optimized out) at ../../../GL/glx/single2.c:238 Looks like a GPU lockup. Does this also happen if you use the i915 kernel module from your kernel instead of from drm Git? The Mesa i915 driver is currently very slow using the TTM due to issues to be worked out in the DRM anyway. Indeed the non-git i195 kernel module makes things working again with compiz, except that I now occasionnaly get some screen corruption (a typical case occurs when minimising/maximising some windows, it looks like the some parts of the screen are not refreshed correctly). How can I help debug this issue better ? Vincent - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [patch] post superioctl inteface removal.
Dave Airlie wrote: DRM_BO_HINT_DONT_FENCE is implied, and use that instead of the set pin interface. We can perhaps rename it to drmBOSetStatus or something more suitable. This will get rid of the user-space unfenced list access (which I believe was the main motivation behind the set pin interface?) while keeping the currently heavily used (at least in Poulsbo) functionality to move out NO_EVICT scanout buffers to local memory before unpinning them, (to avoid VRAM and TT fragmentation, as DRI clients may still reference those buffers, so they won't get destroyed before a new one is allocated). It would also allow us to specify where we want to pin buffers. If we remove the memory flag specification from drmBOCreate there's no other way to do that, except running the buffer through a superioctl which isn't very nice. Also it would make it much easier to unbreak i915 zone rendering and derived work. If we can agree on this, I'll come up with a patch. Have you had a chance to look at this I can probably spend some time on this to get the interface finalised.. Dave. Hi, Dave, So, I did some quick work on this with the result in the drm-ttm-finalize branch. Basically what's done is to revert the setPin interface, and replace drmBOValidate with drmBOSetStatus. drmBOSetStatus is a single buffer interface with the same functionality as previously drmBOValidate but with the exception that it implies DRM_BO_HINT_DONT_FENCE, NO_MOVE buffers have been blocked pending a proper implementation, and optional tiling info has been added. The OP linked interface is gone, but the arguments are kept in drm.h for now, for driver specific IOCTLS. Looking at the buffer object create interface, I think it's a better idea to remove the need for locking and specify the memory flags rather than to assume a buffer in system memory before first validation. Consider a driver that wants to put a texture buffer in VRAM. It does createbuffer, copies the texture in, and then it gets validated as part of the superioctl. If we don't specify the VRAM flag at buffer creation, DRM will go ahead and create a ttm, allocate a lot of pages and then at validate do a copy and free all pages again. If we specify the VRAM flag, the buffer will on creation just reserve a vram area and point any mapped pages to it. Buffer creation and destruction in fixed memory areas was quite fast previously, since no cache flushes were needed, and I'd like to keep it that way. If we don't care or know how buffers are created, we just specify DRM_BO_FLAG_MEM_LOCAL, which will give the modified behavior currently present in master. But we need to remove the need for locking in the buffer manager. Locking was previosly needed a) to protect the ring buffer of i915 as the X server might use it. The i915 buffer driver used it for blit moves to and from VRAM, but there are driver cases (eviction, pagefaults of non-mappable buffers) where we cannot assume that we have the lock. Better to disable i915 blit buffer moves until only DRM is allowed to touch the ring. It must be up to the driver code to ensure that the lock is not needed for any buffer move operations. b) To protect against memory region allocations / validations during take-down and vt-switches when certain memory regions are cleaned and all buffers are swapped out. Before this is merged, we need to disable i915 blit buffer moves and come up with an in-kernel fix for b). For b) we should be able to use something like a condition variable. Basically we want to interruptibly block validation if cleaned or on takedown. Also the unfenced list cleaning could probably be removed. It should be considered a bug to leave something on the unfenced list outside of the super-ioctl. /Thomas - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 12835] New: No RGB GLX visuals
http://bugs.freedesktop.org/show_bug.cgi?id=12835 Summary: No RGB GLX visuals Product: Mesa Version: CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] Since I've upgraded to Mesa GIT and Xorg-server GIT, my glxinfo outputs the following: [EMAIL PROTECTED] LIBGL_DEBUG=verbose glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) libGL: OpenDriver: trying /opt/X11/lib/X11/modules/dri/r300_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: Searching for BusID pci::02:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports pci::02:00.0 libGL warning: 3D driver claims to not support visual 0x23 libGL warning: 3D driver claims to not support visual 0x24 libGL warning: 3D driver claims to not support visual 0x25 libGL warning: 3D driver claims to not support visual 0x26 libGL warning: 3D driver claims to not support visual 0x27 libGL warning: 3D driver claims to not support visual 0x28 libGL warning: 3D driver claims to not support visual 0x29 libGL warning: 3D driver claims to not support visual 0x2a libGL warning: 3D driver claims to not support visual 0x2b libGL warning: 3D driver claims to not support visual 0x2c libGL warning: 3D driver claims to not support visual 0x2d libGL warning: 3D driver claims to not support visual 0x2e libGL warning: 3D driver claims to not support visual 0x2f libGL warning: 3D driver claims to not support visual 0x30 libGL warning: 3D driver claims to not support visual 0x31 libGL warning: 3D driver claims to not support visual 0x32 Error: couldn't find RGB GLX visual Attaching xorg.conf and Xorg.0.log soon. Also, this didn't happen with Mesa 7.0.1 and Xorg-server 1.4. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 12835] No RGB GLX visuals
http://bugs.freedesktop.org/show_bug.cgi?id=12835 --- Comment #1 from [EMAIL PROTECTED] 2007-10-17 10:21 PST --- Created an attachment (id=12088) -- (http://bugs.freedesktop.org/attachment.cgi?id=12088action=view) Xorg log file -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 12835] No RGB GLX visuals
http://bugs.freedesktop.org/show_bug.cgi?id=12835 --- Comment #2 from [EMAIL PROTECTED] 2007-10-17 10:22 PST --- Created an attachment (id=12089) -- (http://bugs.freedesktop.org/attachment.cgi?id=12089action=view) Xorg configuration file -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 12835] No RGB GLX visuals
http://bugs.freedesktop.org/show_bug.cgi?id=12835 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #3 from [EMAIL PROTECTED] 2007-10-17 12:07 PST --- commit 6c753ad51d05fcff260fcf8cccf613d47027171f Author: Kristian Høgsberg [EMAIL PROTECTED] Date: Wed Oct 17 15:05:47 2007 -0400 Pull workaround for unset GLX_DRAWABLE_TYPE back in. The old version just set GLX_DRAWABLE_TYPE to GLX_WINDOW_BIT for configs received through glXGetVisualConfigs and to GLX_WINDOW_BIT | GLX_PIXMAP_BIT for configs received as FBConfigs. The X server needs to send this info, but keep the workaround for now. Fixes #12835. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 11870] AIGLX DRM Probe Removes RADEON DRM Lock
http://bugs.freedesktop.org/show_bug.cgi?id=11870 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #13 from [EMAIL PROTECTED] 2007-10-17 12:52 PST --- jkim's version committed. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 12838] New: Fix drm regression tests
http://bugs.freedesktop.org/show_bug.cgi?id=12838 Summary: Fix drm regression tests Product: DRI Version: DRI CVS Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: medium Component: DRM modules AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] A race condition exists in auth.c causing it to fail when debugging is enabled. A race also exists in lock.c as well as a prematurely closed drmfd by ther server. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 12838] Fix drm regression tests
http://bugs.freedesktop.org/show_bug.cgi?id=12838 --- Comment #1 from [EMAIL PROTECTED] 2007-10-17 13:14 PST --- Created an attachment (id=12090) -- (http://bugs.freedesktop.org/attachment.cgi?id=12090action=view) [Patch] Fix regression tests -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 11131] Mesa 6.5.2 implementation error: i915_program_error: Exceeded max nr indirect texture lookups
http://bugs.freedesktop.org/show_bug.cgi?id=11131 [EMAIL PROTECTED] changed: What|Removed |Added Component|Drivers/DRI/i810|Drivers/DRI/i915 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
