dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 65448] New: Driver fails to compile complex shaders
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=65448 Priority: medium Bug ID: 65448 Assignee: dri-devel(a)lists.freedesktop.org Summary: Driver fails to compile complex shaders Severity: normal Classification: Unclassified OS: Linux (All) Reporter: greg(a)chown.ath.cx Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa The r600 driver fails to translate TGSI to bytecode for complex shaders. https://www.shadertoy.com/view/MdX3Rr is an example for this. The fragment shader compiles into a pretty big TGSI program (about 6500 instructions). r600 takes a long time (tens of seconds) trying to transform it into bytecode, but in then end it fails: EE ../../../../../mesa/src/gallium/drivers/r600/r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed ! EE ../../../../../mesa/src/gallium/drivers/r600/r600_state_common.c:753 r600_shader_select - Failed to build shader variant (type=1) -1 This happens with many of the shaders from shadertoy.com. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 65316] New: [r600g] Game window turns completely black occasionally in WoW.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=65316 Priority: medium Bug ID: 65316 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] Game window turns completely black occasionally in WoW. Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rankincj(a)googlemail.com Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa When playing WoW in 32 bit mode, the game window occasionally turns completely black for a second or two before correctly redrawing itself. However, the UI elements remain visible throughout. I have reproduced this problem with a RV730XT card (HD4670 AGP) and a CAICOS HD6450, but not with my RV790. Note that the HD4670 AGP can only run in 32 bit mode, but the CAICOS runs WoW correctly in 64 bit mode. This is not a new problem (at all!), but I have only recently discovered that it happens with my CAICOS card in 32 bit mode while I was investigating a bug with the sound. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 64819] New: GPU fault detected flood at A8-5600K Trinity 7560D
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64819 Priority: medium Bug ID: 64819 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU fault detected flood at A8-5600K Trinity 7560D Severity: normal Classification: Unclassified OS: Linux (All) Reporter: p00hzone(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa Created attachment 79612 --> https://bugs.freedesktop.org/attachment.cgi?id=79612&action=edit dmesg.log I have exactly similar bug as described at https://bugs.freedesktop.org/show_bug.cgi?id=59089 with Trinity 7560D at A8-5600K. I'm using latest git drivers. As that bug marked as fixed should i claim that my problem is unrelated and caused by hardware and/or other malfunctions? My problem consists of NOT log flood only, but the whole machine usually freezes and nothing except hard reboot can fix this. Problem detects in both idle and high load mode. The temperature of APU is about 20-40C. #uname -a Linux multiseat 3.9.2-1-gpgpu #lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Trinity [Radeon HD 7560D] -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 64649] New: [r600g] Anomaly 2 (Steam) crashes with GLX_EXT_swap_control not supported, unable to set vertical sync
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64649 Priority: medium Bug ID: 64649 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] Anomaly 2 (Steam) crashes with GLX_EXT_swap_control not supported, unable to set vertical sync Severity: critical Classification: Unclassified OS: Linux (All) Reporter: romulasry(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Game update: AppID 236730 "Anomaly 2", ProcID 7610, IP 0.0.0.0:0 ERROR: ld.so: object 'gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded: ignored. GLX_EXT_swap_control not supported, unable to set vertical sync. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 64508] New: Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64508 Priority: medium Bug ID: 64508 Assignee: dri-devel(a)lists.freedesktop.org Summary: Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: maxrd2(a)hotmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.1 Component: Drivers/DRI/R600 Product: Mesa Created attachment 79212 --> https://bugs.freedesktop.org/attachment.cgi?id=79212&action=edit screenshots in order: test9.1, test9.2, test16 Overview: Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290. As a consequence all text in warzone2100 game is unreadable. Steps to Reproduce: wget http://surfnet.dl.sourceforge.net/project/quesoglc/QuesoGLC/0.7.2/quesoglc-… tar -xjf quesoglc-0.7.2.tar.bz2 ./configure && make check Actual Results: Following tests look very bad... letters look like a bunch of overlapping triangles/primitives (attached screenshots) - test9.2 - Render style : GLC_TEXTURE without GL objects without user list - test16 Expected Results: Normally rendered text Platform: Arch Linux x86_64 Kernel: 3.8.12-1-ck #1 SMP PREEMPT x86_64 GNU/Linux mesa 9.1.2-1 ati-dri 9.1.2-1 glu 9.0.0-2 xorg-server 1.14.1-1 xf86-video-ati 1:7.1.0-3 lspci output: 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6290] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 0598 Flags: bus master, fast devsel, latency 0, IRQ 41 Memory at e0000000 (32-bit, prefetchable) [size=256M] I/O ports at 4000 [size=256] Memory at f0400000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 64225] New: bfgminer --scyte generates Segmentation Fault on Northern Island
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64225 Priority: medium Bug ID: 64225 Assignee: dri-devel(a)lists.freedesktop.org Summary: bfgminer --scyte generates Segmentation Fault on Northern Island Severity: normal Classification: Unclassified OS: Linux (All) Reporter: spamjunkeater(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 78869 --> https://bugs.freedesktop.org/attachment.cgi?id=78869&action=edit ./bfgminer -v1 --benchmark --scrypt &> OpenSUSE LLVM-trunk (patched version using: https://bugs.freedesktop.org/attachment.cgi?id=78831) with Mesa trunk 3.9 kernel x86_64 "./bfgminer -v1 --benchmark --scrypt" Generated segmentation fault. Log attached. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 64099] New: Mesa 9.0.3 implementation error: In _mesa_DeleteHashTable, found non-freed data
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64099 Priority: medium Bug ID: 64099 Assignee: dri-devel(a)lists.freedesktop.org Summary: Mesa 9.0.3 implementation error: In _mesa_DeleteHashTable, found non-freed data Severity: minor Classification: Unclassified OS: Linux (All) Reporter: bogomancer(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.0 Component: Drivers/Gallium/r600 Product: Mesa I'm playing around with GL, and I'm receiving this message when my application ends: "Mesa 9.0.3 implementation error: In _mesa_DeleteHashTable, found non-freed data Please report at bugs.freedesktop.org" The problem seems to be with GL_ARB_debug_output, since the message only appears if I make a call to glDebugMessageInsertARB during my application. If you need any more information, please ask. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 63579] New: Savage 2 Edges render white [r600g]
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=63579 Priority: medium Bug ID: 63579 Assignee: dri-devel(a)lists.freedesktop.org Summary: Savage 2 Edges render white [r600g] Severity: major Classification: Unclassified OS: All Reporter: romulasry(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 78046 --> https://bugs.freedesktop.org/attachment.cgi?id=78046&action=edit Edges of the screen renders just white It is almost impossible to see in the distance due to it rendering the edges or sky in just white. -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 63564] New: Radeon HD 5870 CP lockup / Stall with OpenGL load
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=63564 Priority: medium Bug ID: 63564 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD 5870 CP lockup / Stall with OpenGL load Severity: major Classification: Unclassified OS: Linux (All) Reporter: kallisti5(a)unixzen.com Hardware: All Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa Playing Team Fortress 2 under ArchLinux with mainline git mesa + xorg 1.14 Get random GPU lockups and stalls. The driver does recover, however recovery takes around 10 seconds. dmesg gets the following stall warning on every stall: [ 2377.378560] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 2377.378568] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000051691 last fence id 0x000000000005168a) [ 2377.379628] radeon 0000:01:00.0: Saved 279 dwords of commands on ring 0. [ 2377.379635] radeon 0000:01:00.0: GPU softreset: 0x00000003 [ 2377.389578] radeon 0000:01:00.0: GRBM_STATUS = 0xF5700828 [ 2377.389581] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x88000003 [ 2377.389583] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xFC000001 [ 2377.389585] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2377.389586] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 2377.389588] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x400C0000 [ 2377.389590] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048006 [ 2377.389592] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 [ 2377.389593] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 2377.389645] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 2377.389647] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 2377.389648] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2377.389650] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2377.389652] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 2377.389653] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 2377.389655] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 2377.389656] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 2377.407070] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 2377.474159] [drm] probing gen 2 caps for device 1002:5a16 = 2/0 [ 2377.474161] [drm] PCIE gen 2 link speeds already enabled [ 2377.477011] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 2377.477093] radeon 0000:01:00.0: WB enabled [ 2377.477095] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8804270e7c00 [ 2377.477097] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8804270e7c0c [ 2377.493165] [drm] ring test on 0 succeeded in 1 usecs [ 2377.493240] [drm] ring test on 3 succeeded in 1 usecs [ 2377.506450] [drm] ib test on ring 0 succeeded in 0 usecs [ 2377.506483] [drm] ib test on ring 3 succeeded in 1 usecs [ 3733.413723] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 3733.413731] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000000d3f80 last fence id 0x00000000000d3f7d) [ 3733.414789] radeon 0000:01:00.0: Saved 151 dwords of commands on ring 0. [ 3733.414796] radeon 0000:01:00.0: GPU softreset: 0x00000003 [ 3733.419144] radeon 0000:01:00.0: GRBM_STATUS = 0xF5500828 [ 3733.419148] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x88000003 [ 3733.419152] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xEC000001 [ 3733.419155] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 3733.419159] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 3733.419162] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x400C0000 [ 3733.419166] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048004 [ 3733.419169] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 [ 3733.419172] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 3733.419227] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 3733.419230] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 3733.419234] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 3733.419237] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 3733.419241] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 3733.419244] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 3733.419247] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 3733.419251] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 3733.436635] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 3733.503442] [drm] probing gen 2 caps for device 1002:5a16 = 2/0 [ 3733.503444] [drm] PCIE gen 2 link speeds already enabled [ 3733.505831] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 3733.505909] radeon 0000:01:00.0: WB enabled [ 3733.505911] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8804270e7c00 [ 3733.505913] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8804270e7c0c [ 3733.521972] [drm] ring test on 0 succeeded in 1 usecs [ 3733.522028] [drm] ring test on 3 succeeded in 1 usecs [ 3733.534027] [drm] ib test on ring 0 succeeded in 0 usecs [ 3733.534049] [drm] ib test on ring 3 succeeded in 1 usecs kallisti5@eris ~ :) $ sudo lspci -vv -s 01:00.0 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cypress LE [Radeon HD 5800 Series] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device 3070 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 90 Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fea20000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at e000 [size=256] Expansion ROM at fea00000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000feeff00c Data: 41e3 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: radeon -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 61690] New: Graphic issue on PCSX2 with Gallium 0.4 on AMD RS780
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=61690 Priority: medium Bug ID: 61690 Assignee: dri-devel(a)lists.freedesktop.org Summary: Graphic issue on PCSX2 with Gallium 0.4 on AMD RS780 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: pablo11_up(a)yahoo.com Hardware: x86 (IA32) Status: NEW Version: 9.1 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 75782 --> https://bugs.freedesktop.org/attachment.cgi?id=75782&action=edit trace of "Checking MEMORY CARD" first message Hello, Upgrading Mesa 8 to 9.1 got me a graphic problem with PCSX2 emulator Attached an apitrace's trace generated in Mesa 8.0.4. When I replay it on Mesa 9.1 I got bad rendering, some shapes appar to be messed up. http://imageshack.us/a/img32/7455/sshote.jpg http://imageshack.us/a/img202/4097/startw.jpg "configure" Mesa 8.0.4 flags: ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --libdir=/usr/lib \ --mandir=/usr/man \ --docdir=/usr/doc/mesa-$VERSION \ --with-dri-driverdir=/usr/lib/xorg/modules/dri \ --with-dri-drivers=i915,i965,nouveau,r200,radeon,swrast \ --with-gallium-drivers=nouveau,swrast,r300,r600 \ --enable-gallium-llvm \ --build=i486 "configure" Mesa 9.1 flags: ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --libdir=/usr/lib --mandir=/usr/man \ --docdir=/usr/doc/mesa-$VERSION \ --with-dri-driverdir=/usr/lib/xorg/modules/dri \ --with-dri-drivers=i915,i965,intel,nouveau,r200,radeon,swrast \ --with-gallium-drivers=nouveau,swrast,r300,r600 \ --enable-gallium-llvm \ --enable-shared-glapi \ --build=i486 -- You are receiving this mail because: You are the assignee for the bug.

1 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015