dri-devel December 2012

dri-devel@lists.freedesktop.org

121 participants
687 discussions

[Bug 56081] New: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=56081 Priority: medium Bug ID: 56081 Assignee: dri-devel(a)lists.freedesktop.org Summary: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS Severity: major Classification: Unclassified OS: Linux (All) Reporter: autonymous(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 68683 --> https://bugs.freedesktop.org/attachment.cgi?id=68683&action=edit Xorg.0.log Using AMD A4-3420M APU, have NOT been able to use the R600 driver on either Suse (12.x, factory), Arch Linux (latest built, or git xorg/mesa/dri build), or Ubuntu (12.04, 12.10b2). ALL various combinations of xorg 1.12/1.13, xorg-video-ati, mesa, and kernel 3.5-3.6 give the same black screen after startup, transition to Xorg corrupts all VT's. KMS for Single user or non-X sessions works fine. Grub boot with "radeon.audio=0" does alleviate some corruption on VT7 (but not enough to be usable). Changing accel options or even disabling accel has no effect. Appears there is something specific to the A4-3420M(6410D, chipID 0x9644, identified by system as a Sumo2) that is affected by this. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 55688] New: 3650HD card stalls while playing urbanterror
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=55688 Priority: medium Bug ID: 55688 Assignee: dri-devel(a)lists.freedesktop.org Summary: 3650HD card stalls while playing urbanterror Severity: normal Classification: Unclassified OS: All Reporter: stompdagger1(a)yahoo.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 68149 --> https://bugs.freedesktop.org/attachment.cgi?id=68149&action=edit relevant log part I have a multiseat setup with two radeon cards, 5450HD and 3650HD, I was playing urbanterror on the seat that uses 3650HD and the gpu stalled. my kernel version is 3.6.0, libdrm, mesa and xf86-video-ati are from git where the last update was yesterday. I'm attaching the relevant part from /var/log/messages. yesterday I've played the same game on the same setup and it didn't stalled. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 55006] New: video playback causes total freeze on RV350
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=55006 Bug #: 55006 Summary: video playback causes total freeze on RV350 Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: spamfang1199(a)yahoo.de Video playback and switching between tabs while browsing often leads to total freeze of my system. Even the magic SysRQ keys wont work then. steps to reproduce: Watching movies with vlc, or switching between tabs is often enough to freeze the system. It all started with introducing KernelModeSetting to Linux. This bug has been affecting me since i upgraded from Debian Lenny to Squeeze and thus to Kernel 2.6.32. I could avoid that bug however by adding "radeon.modeset=0" at the boot prompt from 2.6.32. Now with Linux 3.2 even passing "radeon.modeset=0" at the boot prompt does not work any more for me. I reported the bug to Debian and they told me to try Linux 3.5, which also freezes often. For reference here is the link to my bug report: http://bugs.debian.org/680097 This is a very serious regression for my RV350 and causes file system corruption & data loss (for my work progress) I cannot add a log from the freeze, since nothing gets logged then. If you know a way i could give you one, let me know. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 54675] New: [RADEON:KMS:RV730XT:HDMI:AUDIO] Screaming audio IRQ with 3.5.3 kernel
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=54675 Bug #: 54675 Summary: [RADEON:KMS:RV730XT:HDMI:AUDIO] Screaming audio IRQ with 3.5.3 kernel Classification: Unclassified Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rankincj(a)googlemail.com Created attachment 66851 --> https://bugs.freedesktop.org/attachment.cgi?id=66851 dmesg output when radeon.audio=1 I have recently added a HD4670 AGP to one of my older machines, and I am noticing problems with the HDMI audio device. Specifically: irq 17: nobody cared (try booting with the "irqpoll" option) Pid: 0, comm: swapper/0 Not tainted 3.5.3 #2 Call Trace: [<c1063806>] ? __report_bad_irq+0x11/0x94 [<c1063a2d>] ? note_interrupt+0x120/0x19b [<c1062325>] ? handle_irq_event_percpu+0xe8/0xfb [<c1062361>] ? handle_irq_event+0x29/0x40 [<c10640fc>] ? handle_level_irq+0x93/0x93 [<c1064163>] ? handle_fasteoi_irq+0x67/0x90 <IRQ> [<c1003625>] ? do_IRQ+0x2e/0x83 [<c1229829>] ? common_interrupt+0x29/0x30 [<c106007b>] ? audit_update_watch+0x59/0x285 [<c1007479>] ? default_idle+0x23/0x3b [<c1007b38>] ? cpu_idle+0x4b/0x7e [<c1314877>] ? start_kernel+0x2a4/0x2a7 handlers: [<f8575b75>] azx_interrupt [snd_hda_intel] Disabling IRQ #17 This is with radeon.audio=0. With radeon.audio=1, the KMS IRQ has similar problem and is also disabled. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 54338] New: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=54338 Bug #: 54338 Summary: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: lyssdod(a)gmail.com Hi, I'm using the most recent kernel — 3.5.3, before switching to it I used 3.5.0. I'm using amd64 Gentoo Linux. The problem is radeon driver is completely unable to load on my laptop (Dell Vostro 3350) Here're some outputs: $ dmesg | grep radeon [ 6.062962] [drm] radeon defaulting to kernel modesetting. [ 6.062966] [drm] radeon kernel modesetting enabled. [ 6.063009] radeon 0000:01:00.0: enabling device (0000 -> 0003) [ 6.628886] radeon 0000:01:00.0: Invalid ROM contents [ 6.628941] radeon 0000:01:00.0: Invalid ROM contents [ 6.628948] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM [ 6.628950] radeon 0000:01:00.0: Fatal error during GPU init [ 6.628953] [drm] radeon: finishing device. [ 6.629996] radeon 0000:01:00.0: no bo for sa manager [ 6.630126] radeon: probe of 0000:01:00.0 failed with error -22 $ uname -a Linux 3.5.3 #1 SMP PREEMPT Fri Aug 31 20:42:09 EEST 2012 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Seymour XT/PRO [Radeon HD 7400M Series] # lsmod | grep radeon radeon 831358 0 cfbfillrect 3717 2 i915,radeon cfbimgblt 2073 2 i915,radeon cfbcopyarea 3289 2 i915,radeon ttm 61238 1 radeon i2c_algo_bit 5079 2 i915,radeon drm_kms_helper 31193 2 i915,radeon drm 212584 5 ttm,i915,drm_kms_helper,radeon # eix -e xorg-server [D] x11-base/xorg-server Available versions: 1.9.5-r1 1.10.6-r1 1.11.4-r1 1.12.2 (~)1.12.3 (~)1.12.99.903 {{dmx doc ipv6 kdrive minimal nptl selinux static-libs tslib +udev xnest xorg xvfb}} Installed versions: 1.12.99.905(05:55:47 PM 08/31/2012)(ipv6 nptl udev xnest xorg -dmx -doc -kdrive -minimal -selinux -static-libs -tslib -xvfb) Homepage: http://xorg.freedesktop.org/ Description: X.Org X servers I'm not using xorg.conf file. http://bpaste.net/show/43054/ — dmesg http://bpaste.net/show/43055/ — kernel config -- 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 54133] New: [radeon][RV620] Resuming from suspend/hibernation randomly fails since kernel 3.5.0
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=54133 Bug #: 54133 Summary: [radeon][RV620] Resuming from suspend/hibernation randomly fails since kernel 3.5.0 Classification: Unclassified Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: loic.yhuel(a)gmail.com Since 3.5.0 kernel (currently 3.5.2-3.fc17.x86_64), resuming from suspend or hibernation randomly fails. There is no display, and the screen flashes every few seconds (probably due to the backlight). Hardware: Toshiba Satellite Pro A300 laptop 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series Here are the relevant kernel messages : [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff880134cc6c00 [drm] ring test on 0 succeeded in 0 usecs [drm] ib test on ring 0 succeeded in 0 usecs [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35! radeon 0000:01:00.0: GPU reset succeed [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). ... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 14

[Bug 53971] New: [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=53971 Bug #: 53971 Summary: [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8 Classification: Unclassified Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: trivial Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: orion(a)cora.nwra.com [ 1.003495] [drm] Initialized drm 1.1.0 20060810 [ 1.032838] [drm] radeon defaulting to kernel modesetting. [ 1.032842] [drm] radeon kernel modesetting enabled. [ 1.036619] [drm] initializing kernel modesetting (RS480 0x1002:0x5954 0x103C:0x3009). [ 1.036645] [drm] register mmio base: 0xFDAF0000 [ 1.036647] [drm] register mmio size: 65536 [ 1.036867] [drm] Generation 2 PCI interface, using max accessible memory [ 1.036883] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 1.036885] [drm] Driver supports precise vblank timestamp query. [ 1.036904] [drm] radeon: irq initialized. [ 1.037130] [drm] Detected VRAM RAM=64M, BAR=128M [ 1.037133] [drm] RAM width 128bits DDR [ 1.040862] [drm] radeon: 64M of VRAM memory ready [ 1.040864] [drm] radeon: 512M of GTT memory ready. [ 1.040884] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1.044037] [drm] radeon: ib pool ready. [ 1.044111] [drm] radeon: 3 quad pipes, 1 z pipes initialized. [ 1.048814] [drm] PCIE GART of 512M enabled (table at 0x0000000134C80000). [ 1.053590] [drm] fence driver on ring 0 use gpu addr 0x80000000 and cpu addr 0xffff88013533f000 [ 1.053656] [drm] Loading R300 Microcode [ 1.059591] [drm] radeon: ring at 0x0000000080001000 [ 1.059611] [drm] ring test succeeded in 1 usecs [ 1.059753] [drm] ib test succeeded in 0 usecs [ 1.059922] [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8 [ 1.059966] [drm] Radeon Display Connectors [ 1.059967] [drm] Connector 0: [ 1.059968] [drm] VGA [ 1.059971] [drm] DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68 [ 1.059972] [drm] Encoders: [ 1.059973] [drm] CRT1: INTERNAL_DAC2 [ 1.059975] [drm] Connector 1: [ 1.059976] [drm] DVI-D [ 1.059977] [drm] HPD1 [ 1.059979] [drm] DDC: 0x198 0x198 0x19c 0x19c 0x1a0 0x1a0 0x1a4 0x1a4 [ 1.059980] [drm] Encoders: [ 1.059982] [drm] DFP1: INTERNAL_DVO1 [ 1.105608] [drm] fb mappable at 0xD0040000 [ 1.105610] [drm] vram apper at 0xD0000000 [ 1.105612] [drm] size 7680000 [ 1.105613] [drm] fb depth is 24 [ 1.105615] [drm] pitch is 6400 [ 1.105739] fbcon: radeondrmfb (fb0) is primary device [ 1.186275] fb0: radeondrmfb frame buffer device [ 1.186277] drm: registered panic notifier [ 1.186313] [drm] Initialized radeon 2.16.0 20080528 for 0000:01:05.0 on minor 0 Doesn't seem to cause any problems, is this worthy of "*ERROR*"? 01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] HP dx5150 MT BIOS 1.09 11/22/2005 Kernel 3.4.9-1.fc16.x86_64 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 53122] New: X lockups /
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=53122 Bug #: 53122 Summary: X lockups / Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 201208bugzillaz(a)moo.uklinux.net Created attachment 65122 --> https://bugs.freedesktop.org/attachment.cgi?id=65122 X log file Upon swapping video cards, I have started getting intermittent freezes of X on my Slackware65 13.37 AMD Opteron box (kernel 3.4.4) The display freezes up totally, including mouse pointer; occasionally there are short (eg ~10s) freezes which might be related, and usually it happens when web browsing (mostly when there is embedded flash on the bbc.co.uk olympics pages) I hope the below is sufficient info; I need to swap video cards back because I can't afford such lockups ATM. Here's the lspci lines: 0a:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4550] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device 21ae Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 74 Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f0500000 (64-bit, non-prefetchable) [size=64K] Region 4: I/O ports at 4000 [size=256] [virtual] Expansion ROM at f0520000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon This appears in /var/log/messages (if I wait 20+mins, it seems to unfreeze fairly reliably) Aug 3 17:28:11 fishpond acpid: client 2126[0:0] has disconnected Aug 3 17:28:11 fishpond acpid: client connected from 2126[0:0] Aug 3 17:28:11 fishpond acpid: 1 client rule loaded Aug 3 17:48:19 fishpond kernel: [68040.346054] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 17:50:19 fishpond kernel: [68160.346048] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 17:52:19 fishpond kernel: [68280.346054] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 17:54:19 fishpond kernel: [68400.346054] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 17:56:19 fishpond kernel: [68520.346048] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 17:58:19 fishpond kernel: [68640.346053] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 18:00:19 fishpond kernel: [68760.346054] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 18:02:19 fishpond kernel: [68880.346047] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 18:04:19 fishpond kernel: [69000.346052] X D ffffffff816065c0 0 2111 2098 0x00400004 Aug 3 18:06:19 fishpond kernel: [69120.346052] X D ffffffff816065c0 0 2111 2098 0x00400004 And instances of this in /var/log/syslog [69120.346044] INFO: task X:2111 blocked for more than 120 seconds. [69120.346049] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [69120.346052] X D ffffffff816065c0 0 2111 2098 0x00400004 [69120.346058] ffff8801743d9b58 0000000000000082 ffff8801743d9ae8 0000000000011dc0 [69120.346062] 0000000000011dc0 ffff880179dd06d0 0000000000011dc0 ffff8801743d9fd8 [69120.346066] ffff8801743d8000 0000000000011dc0 ffff8801743d9fd8 0000000000011dc0 [69120.346071] Call Trace: [69120.346083] [<ffffffff81562859>] schedule+0x29/0x70 [69120.346087] [<ffffffff81562ade>] schedule_preempt_disabled+0xe/0x10 [69120.346091] [<ffffffff815613b9>] __mutex_lock_slowpath+0xd9/0x150 [69120.346095] [<ffffffff815610fb>] mutex_lock+0x2b/0x50 [69120.346125] [<ffffffffa0222820>] radeon_bo_create+0x150/0x2a0 [radeon] [69120.346141] [<ffffffffa0233e6a>] radeon_gem_object_create+0x5a/0x100 [radeon] [69120.346155] [<ffffffffa0234254>] radeon_gem_create_ioctl+0x54/0xe0 [radeon] [69120.346160] [<ffffffff815610ee>] ? mutex_lock+0x1e/0x50 [69120.346174] [<ffffffffa023470c>] ? radeon_gem_get_tiling_ioctl+0xbc/0xf0 [radeon] [69120.346189] [<ffffffffa013405f>] drm_ioctl+0x2cf/0x520 [drm] [69120.346204] [<ffffffffa0234200>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon] [69120.346210] [<ffffffff81142ad7>] do_vfs_ioctl+0x97/0x540 [69120.346213] [<ffffffff81143011>] sys_ioctl+0x91/0xa0 [69120.346217] [<ffffffff815640d2>] system_call_fastpath+0x16/0x1b There is no error logged by X, but here its (but note that I run 6 simultaneaous X's on vt7-vt12). I've attached a log file -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 52467] New: Radeon HD6450 KMS garbled screen on boot.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=52467 Bug #: 52467 Summary: Radeon HD6450 KMS garbled screen on boot. Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sowadski(a)miner.mst.edu Just recently upgraded to a Radeon HD6450. Upon boot, as soon as fbcon takes over, the screen gets corrupted. (note X is not started on boot). SSHing into the box and starting and restarting X a couple time sometimes fixes the issue, sometimes locks of the machine. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 15

[Bug 52345] New: KMS Power Management have no effect
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=52345 Bug #: 52345 Summary: KMS Power Management have no effect Classification: Unclassified Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: d2xdt2(a)gmail.com Using OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD SUMO2 OpenGL version string: 2.1 Mesa 8.0.3 OpenGL shading language version string: 1.20 AMD A4-3400 APU with Radeon(tm) HD Graphics Fedora 17 64bit Linux amd 3.4.5-2.fc17.x86_64 #1 SMP Mon Jul 16 20:52:08 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux According to http://wiki.x.org/wiki/RadeonFeature should echo profile > /sys/class/drm/card0/device/power_method echo high > /sys/class/drm/card0/device/power_profile put the GPU in high performance mode and echo profile > /sys/class/drm/card0/device/power_method echo low > /sys/class/drm/card0/device/power_profile in low performance mode. glxgears gives 60 FPS in both cases, which leads me to beleive that power management does work. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2012