dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 70910] New: [radeonsi&r600g] wrong colors on radeonsi screen in some places when radeonsi and r600g gpus are installed
by bugzilla-daemon＠freedesktop.org 10 Apr '18

10 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=70910 Priority: medium Bug ID: 70910 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi&r600g] wrong colors on radeonsi screen in some places when radeonsi and r600g gpus are installed Severity: minor Classification: Unclassified OS: All Reporter: ptpzz(a)yandex.ru Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 88176 --> https://bugs.freedesktop.org/attachment.cgi?id=88176&action=edit screenshot Looks like in some cases there is RGB <-> BGR mismatch, so that red icons become blue, etc. On the attached screenshot xchat icon on the xfce panel is rendered normally - red/yellow, but the same icon on a tooltip below is blue. Similar issues can be seen in some other places - e.g. window decorations, icons on buttons in dialog windows, but in many other cases the colors are correct - e.g. with glxgears. AFAICS there is no such problem on r600g screen. Also, without r600g card there is no such problem on radeonsi screen as well, it happens only when two cards are installed. r600g uses EXA in my config, but IIRC it was the same when both drivers use glamor. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 66940] New: Mobility Radeon HD 5650 doesn't resume from suspend on kernel 3.11 (linus and drm_next)
by bugzilla-daemon＠freedesktop.org 10 Apr '18

10 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=66940 Priority: medium Bug ID: 66940 Assignee: dri-devel(a)lists.freedesktop.org Summary: Mobility Radeon HD 5650 doesn't resume from suspend on kernel 3.11 (linus and drm_next) Severity: normal Classification: Unclassified OS: All Reporter: mail(a)3v1n0.net Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 82459 --> https://bugs.freedesktop.org/attachment.cgi?id=82459&action=edit dmesg I've tried running linux 3.11 from both linus and drm_next branches, but when using the radeon drivers it's impossible to resume from suspension. It's quite sure that the problem is in radeon module, because unloading it (and switching to my intel card with vgaswitcheroo) works fine. Also, enabling the pm_trace sys-node it highlights that the radeon device caused the freeze: from dmesg: [ 1.286810] Magic number: 0:660:725 [ 1.286815] hash matches /home/marco/Dev/debs/linux/drivers/base/power/main.c:575 [ 1.286829] block loop5: hash matches [ 1.286867] pci 0000:01:00.0: hash matches ^ This is the PCI id of my radeon card cat /sys/power/pm_trace_dev_match: block radeon This is a regression, since linux 3.10 works well. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 89685] Cripling Dota 2 freeze with Morphling at hero selection or loadout
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89685 Bug ID: 89685 Summary: Cripling Dota 2 freeze with Morphling at hero selection or loadout Product: Mesa Version: 10.5 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: wittyman37(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org So I am having a very bizare issue as recently. I noticed yesterday that I cannot play Morphling! If I select him during the hero selection or even try to view him in the loadout screen, my system completely freezes with no option but to do a hard reset. I cannot alt-tab, minimize to desktop, switch to any TTY and REISUB does not work. This ONLY happens with the hero morphling and seems to be an issue with graphics because it seems to happen when I am about to see his model loaded. I even deleted the one item I had for him. I verified the game files; no good. I deleted all local content and downloaded the game again...no good. This is either an issue with my graphics drivers and morphling or a Dota 2 and Linux issue. My wife is using Windows 8.1 and does not have this problem. I am running an AMD R9 270X with linux 3.19.2 and mesa 10.5.1 where everything else works wonderfully! -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 89954] Dota2 crashes computer while playing when probably loading new particles
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89954 Bug ID: 89954 Summary: Dota2 crashes computer while playing when probably loading new particles Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: dogmadefe(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org It's been happening during the last month or so, around the first big team clash, when the ultis are used, the computer freezes for like 5 seconds, and then reboots. Before this, the computer used to freeze during the first clash, but it recovered. Before that, I played Dota2 for a lot of months without any problem. I have an FX6100 and HD7770. I use the open source drivers. Checking the error out log, I get something like this: Apr 06 21:39:24 arch gdm-Xorg-:0[307]: (WW) RADEON(0): flip queue failed: Device or resource busy Apr 06 21:39:24 arch gdm-Xorg-:0[307]: (WW) RADEON(0): Page flip failed: Device or resource busy Apr 06 21:40:21 arch steam.desktop[6478]: [2015-04-0Installing breakpad exception handler for appid(steam)/version(1424305157) Apr 06 21:40:22 arch steam.desktop[6478]: Installing breakpad exception handler for appid(steam)/version(1424305157) Apr 06 21:40:23 arch steam.desktop[6478]: Installing breakpad exception handler for appid(steam)/version(1424305157) Apr 06 21:48:08 arch gdm-Xorg-:0[307]: (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc 331918 < target_msc 331919 Apr 06 21:51:52 arch kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x000c0401 Apr 06 21:51:52 arch kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF80000 Apr 06 21:51:52 arch kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C004001 Apr 06 21:51:52 arch kernel: VM fault (0x01, vmid 6) at page 267911168, read from TC (4) Apr 06 21:52:02 arch kernel: radeon 0000:01:00.0: ring 4 stalled for more than 10083msec Apr 06 21:52:02 arch kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000028b69 last fence id 0x0000000000028b6e on ring 4) Apr 06 21:52:03 arch kernel: radeon 0000:01:00.0: Saved 652 dwords of commands on ring 0. Apr 06 21:52:03 arch kernel: radeon 0000:01:00.0: GPU softreset: 0x000000ED Apr 06 21:52:03 arch kernel: radeon 0000:01:00.0: GRBM_STATUS = 0xE65E4028 Apr 06 21:52:03 arch kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xCF800000 Apr 06 21:52:03 arch kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 84232] New: PHINode containing itself causes segfault in LLVM when compiling Blender OpenCL kernel with R600 backend
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=84232 Priority: medium Bug ID: 84232 Assignee: dri-devel(a)lists.freedesktop.org Summary: PHINode containing itself causes segfault in LLVM when compiling Blender OpenCL kernel with R600 backend Severity: normal Classification: Unclassified OS: All Reporter: vitalif(a)yourcmc.ru Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 106717 --> https://bugs.freedesktop.org/attachment.cgi?id=106717&action=edit Blender output with R600_DEBUG=compute,fs,vs,gs,ps,cs I'm trying to run Blender using Mesa OpenCL implementation on a radeonsi card. First the kernel didn't want to compile, but that was caused by a bug in it (they were using . instead of -> in 1 place), and after fixing this bug I've got the kernel to compile... ...But after that, LLVM started to crash during translation of IR into shader code with R600 backend. I've done some investigation and figured out that the crash is caused by a PHINode containing itself. SIAnnotateControlFlow::handleLoopCondition() can't handle such situation - it recurses into itself, calls Phi->eraseFromParent() inside the inner execution, returns into outer one, gets zeroed out object and crashes when trying to do something with its members... for example when trying to erase it again. I've tried to understand the semantics of such PHINodes from reading the code and got a suspicion that the rest of LLVM code just ignores PHINodes equal to their parent, so I've tried to fix the bug by making handleLoopCondition() skip IncomingValues equal to the Phi itself, but the bug didn't go away! Surprisingly, PHINode may not just contain itself directly, but it also may contain itself inside another PHINode, i.e. Phi->getIncomingValue(0)->getIncomingValue(0) == Phi, which results in the same problem with SIAnnotateControlFlow... I'll attach Blender output with R600_DEBUG = trace everything and a stack trace of the crash. The bug reproduced with llvm 3.5 and snapshot of 3.6; blender is 2.71; Mesa is from OIBAF's repository. sudo -E CYCLES_OPENCL_TEST=1 R600_DEBUG=compute,fs,vs,gs,ps,cs blender cup\ of\ coffee\ 5.blend &> kernel-llvm.log -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 89659] GPU Hangs with dota2
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89659 Bug ID: 89659 Summary: GPU Hangs with dota2 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: kontakt(a)ib-guder.de Created attachment 114442 --> https://bugs.freedesktop.org/attachment.cgi?id=114442&action=edit dmesg after a crash Hello, I get reproducible GPU hangs often within one minute spectating a game in dota2. Other OpenGL applications runs without hangs. The screen stays black, the keyboard doesn't work after a crash. Networking via ssh works. Archlinux 64bit Mesa: 10.5.1 Linux: 3.18.6 and 3.14.53 Thank you and best wishes Tom Guder -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89059] Dota crashes constantly before 10min mark
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89059 Bug ID: 89059 Summary: Dota crashes constantly before 10min mark Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: jarkko_korpi(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org I got oibaf ppa. They started to use LLVM 3.6 compiler around that time I started to have unstable dota. I cant finnish any dota 2 games. The computer hangs before 10min mark while in dota. But I have played around 2hour episode of game of thrones from tell tale. So this sounds only dota 2 issue for me. I could see console a message something like this: "Still active bo inside vm" The computer freezes, most of the times I could only force boot. Gpu r9 290 3.19.0-031900rc7 OpenGL renderer string: Gallium 0.4 on AMD HAWAII OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel (git-08a06b6 2015-02-10 trusty-oibaf-ppa) -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 90284] radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed.
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=90284 Bug ID: 90284 Summary: radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed. Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: niklas(a)trippler.no Created attachment 115515 --> https://bugs.freedesktop.org/attachment.cgi?id=115515&action=edit journalctl -r -x --boot=-4 Graphics card: AMD R9 290 Kernel: Linux archfractal 4.0.1-1-ARCH #1 SMP PREEMPT Monitors connected: 2 DE: Xfce Relevant packages: local/xf86-video-ati 1:7.5.0-2 (xorg-drivers xorg) local/lib32-mesa 10.5.4-1 local/lib32-mesa-libgl 10.5.4-1 local/lib32-mesa-vdpau 10.5.4-1 local/linux 4.0.1-1 (base) local/xorg-server 1.17.1-5 (xorg) This bug, which is triggered by dota2 (Valve game), locks up both displays for a few seconds before they blink black and freeze in the last frame displayed, requireing a system reboot. The bug seems to happen with others (same symptoms / log messages) using other applications (chrome html5 video was mentioned), but dota2 seems like one of the few recreatable ways to trigger the bug. Steps to recreate: Have steam and dota 2 installed (might have to remove steams own bundled libstdc++ libraries as they conflict with mesa). Launch dota 2 with any video settings Start a new lobby with "cheats enabled" and "all pick" game mode (these don't matter, but make it faster to recreate) Pick the hero "Chaos Knight" and enter the game Type in chat "-lvlup 24" to gain max level and skill up everything Click R to use ulti (which spawns copies of himself) Hold-drag mouse over all the illusions and the hero. When the mouse button is released the above bug triggers, crashing the displaydriver and taking the computer down with it. In the log attached (journal_log) the bug is triggered at 17:43:50, the first line there is: "kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x000cc801" I noticed a few lines later the following lines appeared: May 02 17:44:01 archfractal kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed May 02 17:44:01 archfractal kernel: [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed I guessed the bug had something to do with dpm, and disabled it (kernel parameter radeon.dpm=0). When I had done this the bug could still be recreated, but the log showed completely different error messages. This log is also attached as "journal_log_radeon_dpm_is_0" I had to gzip the first log to fit within the 3M file size limit -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 79895] New: Google Hangout crashes radeon
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=79895 Priority: medium Bug ID: 79895 Assignee: dri-devel(a)lists.freedesktop.org Summary: Google Hangout crashes radeon Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Kernel 3.15.0-rc8 + PTE patches [380782.919272] Watchdog[21745]: segfault at 0 ip 00007f405eb822b8 sp 00007f404b8b9850 error 6 in chrome[7f405afc6000+5807000] [380783.427655] radeon 0000:01:00.0: ring 0 stalled for more than 11720msec [380783.427659] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000006e62e5 last fence id 0x00000000006e62e4 on ring 0) [380783.427662] radeon 0000:01:00.0: failed to get a new IB (-35) [380783.852997] radeon 0000:01:00.0: Saved 240 dwords of commands on ring 0. [380783.853042] radeon 0000:01:00.0: GPU softreset: 0x0000006C [380783.853043] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 [380783.853044] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [380783.853045] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [380783.853046] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [380783.853080] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [380783.853082] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [380783.853083] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 [380783.853084] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002 [380783.853085] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243 [380783.853086] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483106 [380783.853087] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [380783.853089] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [380783.853090] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [380784.261939] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF [380784.261993] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100140 [380784.263140] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 [380784.263141] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [380784.263142] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [380784.263143] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [380784.263177] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [380784.263178] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [380784.263180] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [380784.263181] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [380784.263182] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [380784.263183] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [380784.263184] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [380784.263261] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [380784.301675] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [380784.301678] [drm] PCIE gen 3 link speeds already enabled [380784.303658] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [380784.303740] radeon 0000:01:00.0: WB enabled [380784.303742] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff880417946c00 [380784.303743] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff880417946c04 [380784.303744] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff880417946c08 [380784.303745] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff880417946c0c [380784.303746] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff880417946c10 [380784.304140] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90006135a18 [380784.625264] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [380784.625268] [drm:si_resume] *ERROR* si startup failed on resume [380784.625304] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed [380784.625374] switching from power state: [380784.625376] ui class: none [380784.625377] internal class: boot [380784.625378] caps: [380784.625379] uvd vclk: 0 dclk: 0 [380784.625380] power level 0 sclk: 50000 mclk: 15000 vddc: 950 vddci: 875 pcie gen: 3 [380784.625381] status: c b [380784.625382] switching to power state: [380784.625383] ui class: performance [380784.625384] internal class: none [380784.625385] caps: [380784.625386] uvd vclk: 0 dclk: 0 [380784.625387] power level 0 sclk: 30000 mclk: 15000 vddc: 850 vddci: 875 pcie gen: 3 [380784.625388] power level 1 sclk: 50100 mclk: 125000 vddc: 950 vddci: 875 pcie gen: 3 [380784.625390] power level 2 sclk: 81000 mclk: 125000 vddc: 1090 vddci: 875 pcie gen: 3 [380784.625390] status: r -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 69670] New: KWin crashes when switching to OpenGL 3.1 + Raster
by bugzilla-daemon＠freedesktop.org 31 Mar '18

31 Mar '18

https://bugs.freedesktop.org/show_bug.cgi?id=69670 Priority: medium Bug ID: 69670 Assignee: dri-devel(a)lists.freedesktop.org Summary: KWin crashes when switching to OpenGL 3.1 + Raster Severity: normal Classification: Unclassified OS: Linux (All) Reporter: omegatype(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.2 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 86306 --> https://bugs.freedesktop.org/attachment.cgi?id=86306&action=edit kwin stderr KWin crashes with the following message after switching from OpenGL 2.0 + Raster to OpenGL 3.1 + Raster: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. kwin: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Some information about the system (Arch Linux x86_64): $ uname -srvm Linux 3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 19:30:21 CEST 2013 x86_64 $ sudo lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] $ yaourt -Qs mesa | egrep '^[^ ]' extra/ati-dri 9.2.0-2 extra/glu 9.0.0-2 multilib/lib32-ati-dri 9.2.0-1 multilib/lib32-glu 9.0.0-2 multilib/lib32-libtxc_dxtn 1.0.1-5 multilib/lib32-mesa 9.2.0-1 multilib/lib32-mesa-libgl 9.2.0-1 extra/mesa 9.2.0-2 extra/mesa-demos 8.1.0-1 extra/mesa-libgl 9.2.0-2 $ yaourt -Qs xf86-video-ati extra/xf86-video-ati 1:7.2.0-1 (xorg-drivers xorg) # cat /etc/X11/xorg.conf.d/05-glamor.conf Section "Module" Load "dri2" Load "glamoregl" EndSection # cat /etc/X11/xorg.conf.d/50-device.conf Section "Device" Identifier "Default Device" Driver "radeon" Option "SwapbuffersWait" "off" Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "EnablePageFlip" "on" Option "AccelDFS" "on" Option "XV_VSYNC" "on" Option "AccelMethod" "glamor" #Option "AccelMethod" "EXA" EndSection -- You are receiving this mail because: You are the assignee for the bug.

1 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015