dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 100393] Cemu wiiu emulator crashes after selecting game on radeonsi
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=100393 Bug ID: 100393 Summary: Cemu wiiu emulator crashes after selecting game on radeonsi Product: Mesa Version: git 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: giovanni.nicola(a)ticino.com QA Contact: dri-devel(a)lists.freedesktop.org under wine staging 2.3 after selecting game cemu crashes with page fault error and this message is displayed Mesa: User error: GL_INVALID_ENUM in glGetString(GL_EXTENSIONS) note i am using MESA_GL_VERSION_OVERRIDE="4.0" MESA_GLSL_OVERRIDE="400" in nvidia proprietary drivers it works fine so i suggest it is a mesa problem -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 94202] Driver stalls from time to time
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=94202 Bug ID: 94202 Summary: Driver stalls from time to time Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: mail.jpcs(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 121824 --> https://bugs.freedesktop.org/attachment.cgi?id=121824&action=edit /var/log/Xorg.1.log Hello first time posting a bug i'm not sure if this is the right place. If some information is missing please let me know. The issue: Sometimes the screens just goes black, the after a while i get messages reading something along the lines *something* stalled at ring 0 or something like that. I attached /var/log/Xorg.1.log file which i think is the relevant log file. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[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 103881] New: HP Compaq dc5750 fails to resume from suspend
by bugzilla-daemon＠bugzilla.kernel.org 02 Apr '18

02 Apr '18

https://bugzilla.kernel.org/show_bug.cgi?id=103881 Bug ID: 103881 Summary: HP Compaq dc5750 fails to resume from suspend Product: Drivers Version: 2.5 Kernel Version: 4.1.6.i386 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: jefferym(a)gmail.com Regression: No Created attachment 186431 --> https://bugzilla.kernel.org/attachment.cgi?id=186431&action=edit Patch adding the dc5750 to the list of radeon rs4xxx quirks The HP Compaq dc5750 is unable to resume from the suspend state. With the system suspended and I press the power button on the front of the machine I expect it to wake up. When the button is pressed the HDD and CD drive lights activate briefly and the fan powers on. The video output does not appear to resume and stays black. I have to hard power the system to bring it back. Attempting to suspend/resume has this issue every time I have tried it. I observed this behavior on kernels 4.1.6 and 4.0.5. Setting devices in /sys/power/pm_debug resulted in the system failing to resume. The freezer method in /sys/power/pm_debug did not have an issue resuming. I enabled /sys/power/pm_trace and after the hard boot I was able to find a reasonable hash matches line: ' pci 0000:01:05.0: hash matches'. Additionally /sys/power/pm_trace_dev_match was able to resolve this to `radeon`. I was able to boot using a serial console and prevented the radeon driver from loading. In this state it was able to suspend and resume properly. From this state I let the radeon driver load again and the system would fail to resume from suspend. I was able to add this system to the list of RS480 quirks. The system was able to suspend and resume normally with the change. It worked with the Xserver running as well. It appears to be running normally. I have attached the patch I tested against the 4.0.5 and 4.1.6 kernels. Is there anything else I should test? -- You are receiving this mail because: You are watching the assignee of the bug.

1 8

[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 100990] Not running a lot of games on the graphics card Radeon R9 290
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=100990 Bug ID: 100990 Summary: Not running a lot of games on the graphics card Radeon R9 290 Product: Mesa Version: 17.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: negry.mischa(a)yandex.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131298 --> https://bugs.freedesktop.org/attachment.cgi?id=131298&action=edit Log start Superhot Hello. After updating to the new version 17.0.3 mesa(the same thing happens on version 17.1.0) do not run many games, such as Superhot, Screencheat, Yooka-Laylee, Pinstripe. That is, when I start the game hangs a black screen after a few seconds it dies. The characteristics of my computer is the Radeon R9 290, CPU AMD FX-8350. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 96271] TF2: GPU lockup on HD 7950
by bugzilla-daemon＠freedesktop.org 31 Mar '18

31 Mar '18

https://bugs.freedesktop.org/show_bug.cgi?id=96271 Bug ID: 96271 Summary: TF2: GPU lockup on HD 7950 Product: Mesa Version: git 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: hi+freedesktop(a)stephenliang.pw QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 124165 --> https://bugs.freedesktop.org/attachment.cgi?id=124165&action=edit dmesg on kernel 4.7 I'm getting a GPU lockup on Team Fortress 2 which seems to be related to bug #80419 since my dmesg is the same as comment #44 but this is occurring on Team Fortress 2 rather than XCOM. If I run native TF2 with GALLIUM_DDEBUG=800, I cannot reproduce the bug but the frame rate drops significantly. With GALLIUM_DDEBUG="800 noflush", I was able to reproduce the hang. This leads me to believe that the issue is related how high the FPS is running. My kernel is: Linux localhost.localdomain 4.4.9-300.fc23.x86_64 I've also tried 4.6 and 4.7, all of which hangs. My ATI driver is: 7.7.99-3.20160524git040a7b8.fc23 (latest commit in git for radeon) I've also tried 7.6.1-3.20160215gitd41fccc.fc23 (the latest stable from fedora 23), all of which hangs. My mesa version is: 11.3.0-0.37.git357495b.fc23 I've also tried 11.1.0-2.20151218.fc23 (the latest stable from fedora 23), all of which hangs. I've attached the GALLIUM_DDEBUG output and dmesg. One curious thing is that on kernel 4.7, the kernel detects a hang and is able to reset the GPU resulting in a temporary freeze that eventually resumes. However, the freeze will come again after a short while (and resumes). As a data point, I don't get any lockups while playing Skyrim on Wine. -- You are receiving this mail because: You are the assignee for the bug.

1 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017