dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 97861] [amdgpu SI] purple line is visible on left side of the screen connected by HDMI
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97861 Bug ID: 97861 Summary: [amdgpu SI] purple line is visible on left side of the screen connected by HDMI Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: arek.rusi(a)gmail.com Created attachment 126615 --> https://bugs.freedesktop.org/attachment.cgi?id=126615&action=edit the purple line kernel - 3 days old drm-next-4.9-wip mesa/llvm/libdrm - latest xorg - 1.18.4 / ~1.19 I have two displays: DVI monitor, always "on" and HDMI (TV) usually "off". When i turn on HDMI screen: $xrandr --output DVI-I-1 --primary --mode 1680x1050 --output HDMI-A-0 --mode 1920x1080 On left side TV screen appears purple vertical line. 1) this is 80-90% bug 91041, but amdgpu here and srcreen isn't blurry $xrandr --output HDMI-A-0 --auto --set audio off works for me 2) option audio=0 did the job as well 3) Before Xorg/wayland start tty's are clean&black after X/wayland purple line is visible. 4) problem is probably related to hdmi-audio so i don't even know if it's bug at all -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 97730] Monitor not recognized after upgrading to a Radeon RX 480
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97730 Bug ID: 97730 Summary: Monitor not recognized after upgrading to a Radeon RX 480 Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: damien(a)grassart.com Created attachment 126413 --> https://bugs.freedesktop.org/attachment.cgi?id=126413&action=edit /sys/class/drm/card0-DP-2/edid I upgraded my video card from a Radeon HD 8770 to a Radeon RX 480 after which my monitor stopped working. I believe it is an EDID problem since dmesg contains this repeated 4 times: [ +0.120622] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 128 [ +0.000011] Raw EDID: [ +0.000005] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000004] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000005] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000004] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000005] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000005] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000004] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ +0.000005] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff As well as: [ +0.000005] amdgpu 0000:01:00.0: DP-2: Ignoring invalid EDID block 1. [ +0.149608] amdgpu 0000:01:00.0: No connectors reported connected with modes xrandr shows this error message when I run it: "xrandr: Output DisplayPort-1 is not disconnected but has no modes". I can actually get the monitor working by manually adding a mode: $ cvt 2560 1440 # 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz Modeline "2560x1440_60.00" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync $ xrandr --newmode "2560x1440" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync $ xrandr --addmode DisplayPort-1 2560x1440 I've attached the /sys/class/drm/card0-DP-2/edid file if that is helpful. Please let me know if I can provide anything else. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 97634] [amdgpu SI] multigpu setup crashes during boot when dpm=1
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97634 Bug ID: 97634 Summary: [amdgpu SI] multigpu setup crashes during boot when dpm=1 Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: arek.rusi(a)gmail.com Created attachment 126300 --> https://bugs.freedesktop.org/attachment.cgi?id=126300&action=edit kernel log tested on drm-next-4.9-wip: 1) 832c6ef + 2 patches from Tom and Michel (another bugs) 2) 2c0d731 the same behavior on both. With dpm=0 amdgpu doesn't complain and works with intel. Hard to say it's regression because when I tried DRI_PRIME few month ago dpm didn't work at all. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 97556] amdgpu fan behavior doesn't match windows
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97556 Bug ID: 97556 Summary: amdgpu fan behavior doesn't match windows Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: notasas(a)gmail.com CC: alexdeucher(a)gmail.com, notasas(a)gmail.com Some AIB vendor cards have fan profiles tuned to them, which include marketing features like "Zero Frozr", "0 RPM", "Mute Fan" and so on that stop the fan completely while idle. This doesn't seem to be working with amdgpu, the fan always spins although some thermal control does seem to work. My card is MSI RX 470 Gaming X 8G, which has the following vBIOS: https://www.techpowerup.com/vgabios/185500/185500 Dumping ATOM_Fiji_Fan_Table shows: usTMin: 4000 usTMed: 6500 usTHigh: 8500 usPWMMin: 2000 usPWMMed: 4000 usPWMHigh: 6000 usTMax: 10900 ucFanControlMode: 1 usFanPWMMinLimit: 18 usFanPWMMaxLimit: 100 usFanPWMStep: 1 usDefaultMaxFanPWM: 100 usMaxFanPWM: 100 usFanRPMMinLimit: 18 usFanRPMMaxLimit: 100 This doesn't seem to really correspond to how it works on Windows, where the fan stops completely while under 60C (which is how it's also advertised by the vendor). I've not installed any MSI tools there, just the base AMD driver, it also doesn't depend on any autorun .exe, only the base driver is needed for it to behave as advertised on Windows. So does anyone know what is done different by the Windows driver? Perhaps a different fan table is used from the vBIOS? Or perhaps the driver has this logic hardcoded for each partner card? Can it be done on Linux too? -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 97403] AMDGPU/Iceland DPM not properly working on 4.9-wip
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97403 Bug ID: 97403 Summary: AMDGPU/Iceland DPM not properly working on 4.9-wip Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: krejzi(a)email.com 4.9-wip branch should have proper DPM support for Iceland. However, this doesn't seem to work. I can't manually force "high" performance by issuing: # echo high > /sys/class/drm/card1/device/power_dpm_force_performance_level bash: echo: write error: Invalid argument dmesg has one weird note, and that is: [ 20.998755] VI should always have 2 performance levels Full dmesg output related to amdgpu: [ 15.084442] [drm] amdgpu kernel modesetting enabled. [ 15.084452] vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle [ 15.084530] ATPX version 1, functions 0x00000003 [ 15.084576] ATPX Hybrid Graphics [ 15.391373] CRAT table not found [ 15.391375] Finished initializing topology ret=0 [ 15.391388] kfd kfd: Initialized module [ 15.391676] amdgpu 0000:01:00.0: enabling device (0006 -> 0007) [ 15.391869] [drm] initializing kernel modesetting (TOPAZ 0x1002:0x6900 0x103C:0x811C 0x83). [ 15.391879] [drm] register mmio base: 0xE2000000 [ 15.391879] [drm] register mmio size: 262144 [ 15.391883] [drm] doorbell mmio base: 0xE0000000 [ 15.391884] [drm] doorbell mmio size: 2097152 [ 15.391891] [drm] probing gen 2 caps for device 8086:9d10 = 1724843/e [ 15.391892] [drm] probing mlw for device 8086:9d10 = 1724843 [ 15.391903] vga_switcheroo: enabled [ 15.395046] ATOM BIOS: HP/Quanta [ 15.395060] [drm] GPU not posted. posting now... [ 15.398467] [drm] Changing default dispclk from 0Mhz to 600Mhz [ 15.450307] iwlwifi 0000:03:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm [ 15.549634] [TTM] Zone kernel: Available graphics memory: 4027938 kiB [ 15.549636] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 15.549637] [TTM] Initializing pool allocator [ 15.549640] [TTM] Initializing DMA pool allocator [ 15.549655] amdgpu 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used) [ 15.549657] amdgpu 0000:01:00.0: GTT: 3933M 0x0000000080000000 - 0x0000000175D887FF [ 15.549658] [drm] Detected VRAM RAM=2048M, BAR=256M [ 15.549659] [drm] RAM width 64bits DDR3 [ 15.549669] [drm] amdgpu: 2048M of VRAM memory ready [ 15.549669] [drm] amdgpu: 3933M of GTT memory ready. [ 15.549681] [drm] GART: num cpu pages 1006984, num gpu pages 1006984 [ 15.550554] [drm] PCIE GART of 3933M enabled (table at 0x0000000000040000). [ 15.550580] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 15.550580] [drm] Driver supports precise vblank timestamp query. [ 15.550614] amdgpu 0000:01:00.0: amdgpu: using MSI. [ 15.550639] [drm] amdgpu: irq initialized. [ 15.559808] amdgpu: powerplay initialized [ 15.686674] amdgpu 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000010, cpu addr 0xffff880231108010 [ 15.686788] amdgpu 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000020, cpu addr 0xffff880231108020 [ 15.686831] amdgpu 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000030, cpu addr 0xffff880231108030 [ 15.686863] amdgpu 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000040, cpu addr 0xffff880231108040 [ 15.686881] amdgpu 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000050, cpu addr 0xffff880231108050 [ 15.686897] amdgpu 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000080000060, cpu addr 0xffff880231108060 [ 15.686915] amdgpu 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000070, cpu addr 0xffff880231108070 [ 15.686930] amdgpu 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000080, cpu addr 0xffff880231108080 [ 15.686947] amdgpu 0000:01:00.0: fence driver on ring 8 use gpu addr 0x0000000080000090, cpu addr 0xffff880231108090 [ 15.773983] amdgpu 0000:01:00.0: fence driver on ring 9 use gpu addr 0x00000000800000a0, cpu addr 0xffff8802311080a0 [ 15.774017] amdgpu 0000:01:00.0: fence driver on ring 10 use gpu addr 0x00000000800000b0, cpu addr 0xffff8802311080b0 [ 15.835172] [drm] ring test on 0 succeeded in 10 usecs [ 15.835361] [drm] ring test on 1 succeeded in 14 usecs [ 15.835383] [drm] ring test on 2 succeeded in 11 usecs [ 15.835389] [drm] ring test on 3 succeeded in 2 usecs [ 15.835392] [drm] ring test on 4 succeeded in 1 usecs [ 15.835397] [drm] ring test on 5 succeeded in 2 usecs [ 15.835403] [drm] ring test on 6 succeeded in 2 usecs [ 15.835408] [drm] ring test on 7 succeeded in 2 usecs [ 15.835411] [drm] ring test on 8 succeeded in 1 usecs [ 15.835445] [drm] ring test on 9 succeeded in 4 usecs [ 15.835449] [drm] ring test on 10 succeeded in 3 usecs [ 15.835649] [drm] ib test on ring 0 succeeded [ 15.835829] [drm] ib test on ring 1 succeeded [ 15.835939] [drm] ib test on ring 2 succeeded [ 15.836043] [drm] ib test on ring 3 succeeded [ 15.836153] [drm] ib test on ring 4 succeeded [ 15.836256] [drm] ib test on ring 5 succeeded [ 15.836274] [drm] ib test on ring 6 succeeded [ 15.836291] [drm] ib test on ring 7 succeeded [ 15.836307] [drm] ib test on ring 8 succeeded [ 15.836321] [drm] ib test on ring 9 succeeded [ 15.836333] [drm] ib test on ring 10 succeeded [ 15.838598] [drm] Initialized amdgpu 3.3.0 20150101 for 0000:01:00.0 on minor 1 [ 20.998755] VI should always have 2 performance levels Contents of various pp_* files from /sys/class/drm/card1/device # cat power_dpm_force_performance_level off # cat power_dpm_state performance # cat pp_cur_state 0 # cat pp_dpm_mclk 0: 300Mhz 1: 600Mhz 2: 1000Mhz # cat pp_dpm_pcie 0: 2.5GB, x8 1: 2.5GB, x8 2: 8.0GB, x16 3: 8.0GB, x16 4: 8.0GB, x16 5: 8.0GB, x16 # cat pp_dpm_sclk 0: 300Mhz 1: 551Mhz 2: 678Mhz 3: 754Mhz 4: 810Mhz 5: 867Mhz 6: 943Mhz 7: 1021Mhz # cat pp_force_state (empty, not the actual output) # cat pp_mclk_od 0 # cat pp_num_states states: 3 0 boot 1 performance 2 battery # cat pp_sclk_od 0 -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 97362] Low performance after suspend on RX 480
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97362 Bug ID: 97362 Summary: Low performance after suspend on RX 480 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: haagch(a)frickel.club Created attachment 125811 --> https://bugs.freedesktop.org/attachment.cgi?id=125811&action=edit dmesg 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Polaris10] (rev c7) Tried on vanilla Linux 4.7 and 4.8-rc2 with the async pageflip commit reverted. I'm testing with a very simple directx9 application (without nine) because the impact is extremely obvious with wine: http://www.codesampler.com/dx9src/dx9src_1.htm#dx9_initialization Before suspending it runs with 5000+ FPS, after suspending it runs with <1000. Also, if you keep the mouse pointer over the window moving, it will have a very small performance drop before suspending and a huuuge performance drop after suspending. I looked at the powerplay values in sysfs while that application is running in wine and before suspend, pcie is 0: 2.5GB, x8 1: 8.0GB, x16 * and sclk is 0: 300Mhz 1: 608Mhz 2: 910Mhz 3: 1077Mhz 4: 1145Mhz 5: 1191Mhz 6: 1236Mhz 7: 1288Mhz * after suspend it's pcie 0: 2.5GB, x8 * 1: 8.0GB, x16 and sclk 0: 300Mhz 1: 608Mhz * 2: 910Mhz 3: 1077Mhz 4: 1145Mhz 5: 1191Mhz 6: 1236Mhz 7: 1288Mhz mclk is 0: 300Mhz 1: 2000Mhz * in both cases. I then tried echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level and the sclk clock goes to max and pcie goes to 16x again, but the performance of the application does NOT increase so it looks like the low clocks are a symptom of whatever causes low performance. dmesg from 4.8-rc2 attached, shows some errors: [ 574.369317] failed to send message 5e ret is 0 [ 574.369317] [drm:amdgpu_vce_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 12 test failed [ 574.369317] [drm:amdgpu_resume [amdgpu]] *ERROR* resume of IP block <vce_v3_0> failed -110 [ 574.369317] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed (-110). -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 97240] VCE encoding sometimes locks up since 4.8-rc1
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97240 Bug ID: 97240 Summary: VCE encoding sometimes locks up since 4.8-rc1 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: haagch(a)frickel.club RX 480 with mesa git etc. Running this gstreamer pipeline gst-launch-1.0 -e filesrc location=big_buck_bunny_720p_1mb.mp4 ! qtdemux ! decodebin ! videoconvert ! omxh264enc ! h264parse ! matroskamux ! filesink location=/tmp/output.mkv works fine on 4.7. On 4.8-rc1 running it a couple of times randomly locks up the gst-launch process. Then while it hangs, running glxgears or so locks up everything. On the plus side, when it works, it works a lot quicker on 4.8. I'll look into bisecting unless someone else can reproduce and already knows why it happens. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 97025] flip queue failed: Device or resource busy
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97025 Bug ID: 97025 Summary: flip queue failed: Device or resource busy Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: linux(a)bernd-steinhauser.de Since last week I have random freezes with the amdgpu driver (running on Kaveri). Once the issue occurs the display freezes. It's not fixable by switch to VT2 and back. In Xorg.0.log I can find multiple times: [ 92357.021] (WW) AMDGPU(0): flip queue failed: Device or resource busy [ 92357.021] (WW) AMDGPU(0): Page flip failed: Device or resource busy [ 92357.021] (EE) AMDGPU(0): present flip failed No related messages in the journal or dmesg afaics. It does not seem to be related to a specific event (like a video playing), but just happens out of nowhere. I didn't find a way to reproduce it specifically. Possibly related packages that I built in that time: * dev-lang/llvm-scm::arbor 2016-06-11 07:42:19 UTC * dev-lang/llvm-scm::arbor 2016-06-19 07:29:42 UTC * x11-dri/mesa-12.0.0-rc4::x11 2016-06-21 21:40:48 UTC * dev-lang/llvm-scm::arbor 2016-07-02 11:57:34 UTC * dev-lang/clang-scm::arbor 2016-07-02 12:43:00 UTC * dev-lang/llvm-3.8.0-r1::arbor 2016-07-12 20:04:14 UTC * dev-lang/clang-3.8.0::arbor 2016-07-12 20:48:27 UTC * x11-dri/mesa-12.0.0::x11 2016-07-13 04:42:47 UTC * x11-dri/mesa-12.0.1::x11 2016-07-17 14:25:44 UTC * x11-server/xorg-server-1.18.4::x11 2016-07-20 16:06:18 UTC I couldn't get mesa 12 to built with llvm-scm anymore, so I downgraded. Still, I doubt it's related. It's hard to be certain about this, but it could have been a regressing coming with mesa 12 and possibly mesa-12.0.0. I'm pretty sure I haven't seen the freeze before 12.0.0 final, but it's hard to be certain about this with an issue so random. In case it matters, my xorg settings are: Section "Device" Identifier "AMDGPU" Driver "amdgpu" Option "TearFree" "Off" Option "EnablePageFlip" "On" Option "DRI" "3" EndSection IIRC, this is now standard, so nothing special here. -- You are receiving this mail because: You are the assignee for the bug.

1 31

[Bug 96956] amdgpu disables fan by default and burns HW
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=96956 Bug ID: 96956 Summary: amdgpu disables fan by default and burns HW Product: DRI Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: stsp(a)list.ru I have radeon R9 380. After the KMS driver activates, the fans on the GPU stops. They can be activated again by properly setting up fancontrol, but this wasn't configured on my PC. As the result, for the last few years I have replaced many motherboards, all starting to have bad capacitors around the video card. But only now I have noticed that the fans are not rotating... :( The driver should activate fans by default, or don't touch the initial settings (fans are rotating before linux have started), but not stop them by default. Bug reports for the reference: https://bugzilla.kernel.org/show_bug.cgi?id=119211 https://bugzilla.redhat.com/show_bug.cgi?id=1340949 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 96243] GPU initialization fails
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=96243 Bug ID: 96243 Summary: GPU initialization fails Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: hiwatari.seiji(a)gmail.com Created attachment 124126 --> https://bugs.freedesktop.org/attachment.cgi?id=124126&action=edit dmesg output after modprobing amdgpu Setup: QEMU + VFIO running VM with Ubuntu 16.04 and the latest amdgpu driver (amdgpu-pro 16.20.3) If the system is started normally, the kernel crashes during boot with various errors (varies from boot to boot!). If the module (amdgpu) is blacklisted during boot (grub.cfg) and modprobed afterwards the error always the same [see attached file]: sw_init 5 failed -12 amdgpu_init failed memory type 2 has not been initialized amdgpu probe failed with error -12 Experiments: - Using the amdgpu version shipped with Ubuntu 16.04, booting works ONCE. Rebooting/Shutting-Down the VM leads to consecutive errors of not beeing able to init the GPU again, probably due to Bonaire PCI-Reset issues. Restarting the Host itself allows booting the VM once more. Hereafter: Same error. - A Windows 10 VM does not suffer from those issues. Rebooting/Shutting-Down this VM works without issues / host-reboot -- You are receiving this mail because: You are the assignee for the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017