dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 34969] New: [nouveau] Card lockup on openarena
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=34969 Summary: [nouveau] Card lockup on openarena Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mad.f3ka(a)gmail.com Created an attachment (id=44068) --> (https://bugs.freedesktop.org/attachment.cgi?id=44068) messages.log part Each time I try to start openarena or any other game, card locks up (not in menu, but in game). I'm not sure, but log in messages seems to be related to this issue (see messages attachment). Software versions: kernel 2.6.37.2 libdrm 2.4.23 mesa 7.10.1 xf86-video-nouveau 0.0.16_git20101217 Hardware: 06:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 22

[Bug 63192] New: [nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=63192 Priority: medium Bug ID: 63192 Assignee: dri-devel(a)lists.freedesktop.org Summary: [nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor Severity: normal Classification: Unclassified OS: Linux (All) Reporter: vova7890(a)mail.ru Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/other Product: DRI Weston runned in drm-mode provide very high cpu load on mouse moving. I don`t think that the bug of weston, seems problem in nouveau drm. At launch weston have a log: ... [24465.734894] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 [24465.748153] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 [24521.950788] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 [24521.955032] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 ... ioread32_native(ioread32 on litle-endian) using 100% of cpu core. If in weston comment out drmModeSetCursor - cpu load is normal, but no see cursor ofcourse. They copying cursor(64x64) from bo-object. Seems TTM iomem access provide very high cpu load... On radeon it works smoothly and no have very high cpu load. Kernel 3.9-rc5 (x86_64) Wayland/Weston: git Mesa: git libdrm: git -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 57352] New: [nouveau] Kernel Tux logo incorrectly displayed at boot
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=57352 Priority: medium Bug ID: 57352 Assignee: dri-devel(a)lists.freedesktop.org Summary: [nouveau] Kernel Tux logo incorrectly displayed at boot Severity: normal Classification: Unclassified OS: All Reporter: bonbons67(a)internet.lu Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI When booting with build-in nouveau (KMS enabled) the Tux logos displayed are not recognizable. It looks like incorrect tiling configuration of either source or destination buffer when rendering the logo. Normal fbcon console text displays as expected. This happens with linux-3.7-rc5 and newer (don't know since when). Hardware is MacBookAir with GeForce 9400M (C79) [10de:0870]. (screenshot following later on) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 34296] New: Failure loading nouveau for nVidia GeForce 8600 GT on ASUS XG Station(external 1x PCIe encasing for an GPU)
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=34296 Summary: Failure loading nouveau for nVidia GeForce 8600 GT on ASUS XG Station(external 1x PCIe encasing for an GPU) Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: revellion(a)gmail.com loading Nouveau fails with Feb 15 01:39:21 localhost kernel: [drm] nouveau 0000:0c:00.0: Detected 256MiB VRAM Feb 15 01:39:21 localhost kernel: mtrr: zero sized request Feb 15 01:39:21 localhost kernel: [drm] nouveau 0000:0c:00.0: 512 MiB GART (aperture) Feb 15 01:39:21 localhost kernel: [drm] nouveau 0000:0c:00.0: Error mapping EVO DMA push buffer: -12 Feb 15 01:39:21 localhost kernel: [drm] nouveau 0000:0c:00.0: Error creating EVO channel: -12 Feb 15 01:39:21 localhost kernel: nouveau 0000:0c:00.0: PCI INT A disabled Feb 15 01:39:21 localhost kernel: nouveau: probe of 0000:0c:00.0 failed with error -12 And nothing gets outputted on any of the connected monitors during any part of the driver loading, not even a mode switch or anything. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 28095] New: X crash with PFIFO_CACHE_ERROR. (Nouveau on Riva TNT).
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=28095 Summary: X crash with PFIFO_CACHE_ERROR. (Nouveau on Riva TNT). Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bzipitidoo(a)hotmail.com Created an attachment (id=35642) --> (https://bugs.freedesktop.org/attachment.cgi?id=35642) lernel log System is a Pentium II with a Diamond Viper V550 (Riva TNT) card. OS is Arch Linux, with latest versions of Nouveau from git repositories on freedesktop.org: kernel 2.6.34-rc5 libdrm 2.4.20 xf86-video-nouveau 0.0.16 I have "options drm debug=1" in /etc/modprobe.d/modprobe.conf. Acceleration is enabled. With this setup, X works for a few minutes and then crashes. I was running Firefox and lxterminal (am using lxde with openbox window manager). The first problem I saw was the titlebar for lxterminal was not always rendered. Grabbed the graphics from the web page behind it. The crash happened when I tried to search for something in Firefox's search dialog at the upper left. Went into a loop in which the pop up menu of suggested search terms flickered on and off perhaps 10 times, then X crashed. Saw many of these messages in kernel.log: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 15/5 Mthd 0x0638 Data 0x00dcdad5 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 61533] New: GPU lockups uccurs regularilly on kernel 3.8 caused by Opera browser hardware accelerated rendering
by bugzilla-daemon＠freedesktop.org 04 Dec '14

04 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=61533 Priority: medium Bug ID: 61533 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU lockups uccurs regularilly on kernel 3.8 caused by Opera browser hardware accelerated rendering Severity: critical Classification: Unclassified OS: Linux (All) Reporter: ken20001(a)ukr.net Hardware: x86-64 (AMD64) Status: NEW Version: XFree86 4.4.0 Component: DRM/Radeon Product: DRI Just upgraded kernel to version 3.8 on my system and several GPU lockups uccured when I opened pastebin link in Opera browser. (Here is expample link: http://paste.ubuntu.com/5568971/ or http://paste.ubuntu.com/5568954/). Several times I opened such several links in Opera and one time it caused GPU lockup and other times it even freezes. After turning off Opera Hardware Acceleration there was no lokups. And the thing is that with kernel 3.5 no lockups occured even with hardware acceleration turned on. Software: Kubuntu 12.10 x86_64 Linux 3.8.0-7-generic #16~lp1084783v1 KDE 4.10, desktop effects enabled. OpenGL version string: 3.0 Mesa 9.2-devel (git-533dc3b quantal-oibaf-ppa) libdrm-radeon1: 2.4.42+git1302251607.41fc2c~gd~q xserver-xorg-video-radeon: 1:7.1.0+git1302220944.f1059e~gd~q xserver-xorg-core: 2:1.13.0-0ubuntu6.1 Hardware: Intel C2D 7200 ASUS P5B Deluxe AMD Radeon HD 2600 XТ -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 31532] New: rv670 AGP gart + gallium - GPU lockups. PCIE gart runs but stalls.
by bugzilla-daemon＠freedesktop.org 19 Nov '14

19 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=31532 Summary: rv670 AGP gart + gallium - GPU lockups. PCIE gart runs but stalls. Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: lists(a)andyfurniss.entadsl.com Running d-r-t kernels, xserver 1.9 and git mesa, ddx, lib drm. Any non trivial mesa demo with r600g will cause a gpu lockup/reset unless I use PCIE gart and turn off writebacks. Tiling on/off makes no difference. Not a regression AFAICT, this box was retired a while back, before 600g was really usable, so I don't have and have been unable to find a time when it ever worked. Classic KMS + AGP gart works OK. Both Classic KMS and Gallium with agpmode=-1 have stalling problems. Classic runs demos fine, but will stall for 1/2 sec on some games and some levels eg. openarena anholt is OK but other levels will stutter a bit. These do not show with latencytop. Classic + UMS does not stall. Gallium has far worse stalling problems than classic. Some mesa demos will stall, gearbox shows the most - up to a second when running sometimes more at start. Latency top will show gallium stalls - radeon_fence_wait often shows 488ms but never more. Long stalls such as when starting games/demos seem to be in - radeon_cs_ioctl I have seen 3000ms for games and 1000ms for demos. Openarena anholt demo 600g behaves strangely - it will stall so much while loading and rendering the first few frames that this takes minutes. After this the demo will run at full speed to completion (sometimes stalls again midway). Benchmark results have shown it took 8 seconds to render one of the early frames - 840 frames 45.0 seconds 18.7 fps 7.0/53.5/8004.0/23.7 ms. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 64376] New: radeon fatal error during GPU init (Radeon 5850, KVM GPU passthrough)
by bugzilla-daemon＠freedesktop.org 18 Nov '14

18 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=64376 Priority: medium Bug ID: 64376 Assignee: dri-devel(a)lists.freedesktop.org Summary: radeon fatal error during GPU init (Radeon 5850, KVM GPU passthrough) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: luke-jr+freedesktopbugs(a)utopios.org Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Booting on a KVM instance tested to work fine with fglrx: [ 3.771157] [drm] Initialized drm 1.1.0 20060810 [ 4.006077] [drm] radeon kernel modesetting enabled. [ 4.006350] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 4.006714] [drm] initializing kernel modesetting (CYPRESS 0x1002:0x6899 0x1458:0x21E4). [ 4.006723] [drm] register mmio base: 0xFEB80000 [ 4.006724] [drm] register mmio size: 131072 [ 4.006785] radeon 0000:00:05.0: Expecting atombios for evergreen GPU [ 4.006786] radeon 0000:00:05.0: Fatal error during GPU init [ 4.006789] [drm] radeon: finishing device. [ 4.006792] [TTM] Memory type 2 has not been initialized [ 4.008077] radeon: probe of 0000:00:05.0 failed with error -22 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 29226] New: on r600 3d applications are rendered too bright
by bugzilla-daemon＠freedesktop.org 11 Nov '14

11 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=29226 Summary: on r600 3d applications are rendered too bright Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hramrach(a)centrum.cz I am running r600 card with 2.6.34 kernel and Mesa 7.8.2. ATI Technologies Inc RV710 [Radeon HD 4350] Since switching to the card I noticed rendering issues the most prominent being incorrect colors. The colors of many objects seem overly bright and lack saturation, the lighted areas show large patches of white or nearly white color. The UI which is 2d/unlit looks OK and so do glxgears. This does not happen on r300 card or Intel card. I tried running planeshift with software rendering and the character preview after logging in looked much better. However, after running with software renderer the issue is gone. This might be because planeshift calculates some lighting information during runtime and it was changed by the calculations performed on the software renderer. Planeshift can be found at http://www.planeshift.it/download.html I am not sure what the exact issue is. So far I was unable to reproduce it visibly with a trivial program. However, it also happens when running a 3D program through wine. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 19

[Bug 59649] New: [r600][RV635] GPU lockup CP stall / GPU resets over and over - Kernel 3.7, 3.8-rcX
by bugzilla-daemon＠freedesktop.org 10 Nov '14

10 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=59649 Priority: medium Bug ID: 59649 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600][RV635] GPU lockup CP stall / GPU resets over and over - Kernel 3.7, 3.8-rcX Severity: major Classification: Unclassified OS: Linux (All) Reporter: shawn.starr(a)rogers.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.0 Component: Drivers/Gallium/r600 Product: Mesa Using Linux kernel 3.7 and up to 3.8-rc3 Unable to have a stable session with my RV635 GPU Jan 19 03:45:26 segfault kernel: [15008.313696] radeon 0000:01:00.0: Saved 185 dwords of commands on ring 0. Jan 19 03:45:26 segfault kernel: [15008.313704] radeon 0000:01:00.0: GPU softreset Jan 19 03:45:26 segfault kernel: [15008.313711] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 Jan 19 03:45:26 segfault kernel: [15008.313717] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 Jan 19 03:45:26 segfault kernel: [15008.313723] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 Jan 19 03:45:26 segfault kernel: [15008.313730] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 19 03:45:26 segfault kernel: [15008.313736] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jan 19 03:45:26 segfault kernel: [15008.313742] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000006 Jan 19 03:45:26 segfault kernel: [15008.313748] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80000645 Jan 19 03:45:26 segfault kernel: [15008.313761] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE Jan 19 03:45:26 segfault kernel: [15008.328772] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 Jan 19 03:45:26 segfault kernel: [15008.344782] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 Jan 19 03:45:26 segfault kernel: [15008.344785] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 Jan 19 03:45:26 segfault kernel: [15008.344787] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200080C0 Jan 19 03:45:26 segfault kernel: [15008.344789] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 19 03:45:26 segfault kernel: [15008.344792] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jan 19 03:45:26 segfault kernel: [15008.344794] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jan 19 03:45:26 segfault kernel: [15008.344797] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80100000 Jan 19 03:45:26 segfault kernel: [15008.345799] radeon 0000:01:00.0: GPU reset succeeded, trying to resume Jan 19 03:45:26 segfault kernel: [15008.348414] [drm] probing gen 2 caps for device 8086:2a41 = 1/0 Jan 19 03:45:26 segfault kernel: [15008.350360] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). Jan 19 03:45:26 segfault kernel: [15008.350399] radeon 0000:01:00.0: WB enabled Jan 19 03:45:26 segfault kernel: [15008.350403] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff880229236c00 Jan 19 03:45:26 segfault kernel: [15008.381778] [drm] ring test on 0 succeeded in 1 usecs Jan 19 03:45:26 segfault kernel: [15008.384549] [drm] ib test on ring 0 succeeded in 0 usecs Jan 19 03:46:12 segfault kernel: [15053.625108] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec ... Jan 19 03:46:12 segfault kernel: [15053.975428] radeon 0000:01:00.0: Wait for MC idle timedout ! Jan 19 03:46:12 segfault kernel: [15054.123890] radeon 0000:01:00.0: Wait for MC idle timedout ! Jan 19 03:46:12 segfault kernel: [15054.125748] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). Jan 19 03:46:12 segfault kernel: [15054.125785] radeon 0000:01:00.0: WB enabled Jan 19 03:46:12 segfault kernel: [15054.125789] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff880229236c00 Jan 19 03:46:12 segfault kernel: [15054.157608] [drm] ring test on 0 succeeded in 0 usecs Jan 19 03:46:23 segfault kernel: [15064.657103] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec Jan 19 03:46:23 segfault kernel: [15064.657114] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000000441b6 last fence id 0x00000000000441a8) Jan 19 03:46:23 segfault kernel: [15064.657121] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). Jan 19 03:46:23 segfault kernel: [15064.657134] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). Jan 19 03:46:23 segfault kernel: [15064.657140] radeon 0000:01:00.0: ib ring test failed (-35). Jan 19 03:46:23 segfault kernel: [15064.658211] radeon 0000:01:00.0: GPU softreset Jan 19 03:46:23 segfault kernel: [15064.658218] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xE57C24E0 Jan 19 03:46:23 segfault kernel: [15064.658224] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00113303 Jan 19 03:46:23 segfault kernel: [15064.658230] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200030C0 Jan 19 03:46:23 segfault kernel: [15064.658236] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000 Jan 19 03:46:23 segfault kernel: [15064.658242] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00001002 Jan 19 03:46:23 segfault kernel: [15064.658248] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00028482 Jan 19 03:46:23 segfault kernel: [15064.658254] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80838645 Jan 19 03:46:23 segfault kernel: [15064.829116] radeon 0000:01:00.0: Wait for MC idle timedout ! Jan 19 03:46:23 segfault kernel: [15064.829123] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE Jan 19 03:46:23 segfault kernel: [15064.844133] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 Jan 19 03:46:23 segfault kernel: [15064.860144] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 Jan 19 03:46:23 segfault kernel: [15064.860150] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 an 19 03:46:23 segfault kernel: [15064.860163] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x2000B0C0 Jan 19 03:46:23 segfault kernel: [15064.860169] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 19 03:46:23 segfault kernel: [15064.860175] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jan 19 03:46:23 segfault kernel: [15064.860181] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jan 19 03:46:23 segfault kernel: [15064.860191] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80100000 Jan 19 03:46:23 segfault kernel: [15064.861197] radeon 0000:01:00.0: GPU reset succeeded, trying to resume Jan 19 04:39:23 segfault kernel: [ 2791.671107] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). Jan 19 04:39:23 segfault kernel: [ 2791.671115] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). Then floods console with [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! radeon 0000:01:00.0: couldn't schedule ib (over and over) mesa-dri-drivers-9.0.1-3.fc18.x86_64 libdrm-2.4.40-1.fc18.x86_64 kernels: kernel-3.7.3-201.fc18.x86_64, kernel-devel-3.8.0-0.rc3.git1.2.fc19.x86_64 I have not tried on 3.8-rc4 yet Laptop: Lenovo ThinkPad W500 -- You are receiving this mail because: You are the assignee for the bug.

1 28

← Newer
1
...
28
29
30
31
32
33
34
...
73
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013