dri-devel April 2018

dri-devel@lists.freedesktop.org

267 participants
1852 discussions

[Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=105425 --- Comment #14 from MirceaKitsune <sonichedgehog_hyperblast00(a)yahoo.com> --- (In reply to iive from comment #13) Like I said, I don't currently believe this is a hardware defect: My video card isn't even 3 years old. It's a card from Gigabyte which makes high quality products. The temperature of the GPU is within bounds at all times (45°C to 70°C). Its GPU clock seems to be at the right frequency, whereas the memory clock appears to be at 1/3 the supported frequency so it already is under-clocked and more stable! Also why does only 3D ever produce the freeze, even simple scenes that don't stress either the GPU nor the VRAM... whereas 2D never does it even when it's intensive (eg: games, desktop compositing)? If people believe hardware hasn't been ruled out, please suggest a GPU stressing tool for Linux (I use openSUSE Tumbleweed) which you believe is adequate for this situation. I no longer have Windows and can't redo my entire setup by installing another OS, this is my main desktop on which I do my work and activities. I still think this is related to a driver or kernel vulnerability of some sort. Please let me know which logs I can post or what else I can monitor to confirm this and see exactly where and how it's happening. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 103056] Artifacts in CS:GO
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=103056 Bug ID: 103056 Summary: Artifacts in CS:GO Product: Mesa Version: git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: network723(a)rkmail.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 134597 --> https://bugs.freedesktop.org/attachment.cgi?id=134597&action=edit Artifacts on Cache There are flashing artifacts on the ground textures in CS:GO on certain maps. The affected maps are: cache, overpass. openSUSE 42.3 Mesa: git master d5e7ce28b5f6e0a7e4857d1e56143c00eba0c265 LLVM: trunk revision 314551 Kernel: 4.13.4 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 104683] WebGL crashes the kernel driver and Xorg
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=104683 Bug ID: 104683 Summary: WebGL crashes the kernel driver and Xorg Product: Mesa Version: 17.3 Hardware: Other OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: freedesktop(a)linux-geek.org QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136827 --> https://bugs.freedesktop.org/attachment.cgi?id=136827&action=edit kernel log Running the GraphicsFuzz benchmark (https://www.graphicsfuzz.com/benchmark/android-v1.html) on Chromium 63.0.3239.132. On shader 15, Xorg briefly freezes and then Xorg and the radeon kernel driver crash. This is on an Arch Linux with mesa 17.3.2. $ glxinfo | grep "OpenGL renderer string" OpenGL renderer string: AMD PITCAIRN (DRM 2.50.0 / 4.14.13-1-ARCH, LLVM 5.0.1) -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=105425 --- Comment #13 from iive(a)yahoo.com --- (In reply to MirceaKitsune from comment #10) > Created attachment 138438 [details] > Screenshot of the Blender window glitching > > I should add another detail to the discussion. I know this may be a separate > issue which might have nothing to do with the crash, but at the same time I > wouldn't be surprised if it does: Glitched graphics often indicate something > going wrong with the display, such as corrupt textures in video memory, > which may ultimately lead to just such a lockup. > > On occasion, certain programs (namely Firefox and Blender) glitch out and > draw broken rectangles all over the window. Some of those glitches are just > boxes of random colors, others contain pieces of past images (for instance I > saw patterns from my lock screen background). Sometimes they quickly > disappear on their own, at other times I have to restart the program as it > becomes illegible and unusable. If I move anything the squares flicker all > over the place. The glitches continue even after I disable desktop effects, > thus KDE compositing should have nothing to do with it. > > Attached is a screenshot of the glitch happening in Blender, showing its > window covered in the corrupt squares. I'm curious what your opinion is. > Again I know this may be an unrelated issue, but I'm wondering whether it > indicates some video storage corruption that's also leading up to the > lockups. I think you should try running your hardware under Windows. You might also want to check if you still have warranty on the card and act quickly if it expires soon. I do suspect that it is a common hardware fault that happens with most video cards over time. I also had it on my very old HD5670, but with some help I did manage to salvage it, for now. My first symptoms were problems with RAM, that could be "workaround"-ed by lowering the memory frequency to half of the nominal frequency. The problem is in micro BGA (Ball Grid Array). The GPU chip is the size of a fingernail and is placed on a "pad" that is usually about square inch size. The chip and the pad are connected with microBGA. The pad has a normal BGA on its other side that is soldered to the GPU card. With thermal expansion and contraction the soldier of the micro pad fractures and starts to misbehave. It's common to point out that lead-free soldier is not as reliable under temperature changes. You might have heard about solutions like baking the card or re-balling the BGA. I do not recommending trying these. Baking the card might damage other components on it (capacitors, everything plastic). Re-balling changes the soldier of the normal BGA, but it is very expensive manual labor that is not even fixing the BGA which causes the problems. All these "solutions" work because they also heat the small GPU chip and melt the microBGA soldier. If you are sure that this is your problem, you can find somebody who knows how to use a hot air soldering station and heat just the small GPU chip with 200-250C for about 2-5 minutes. These the the temperatures and duration used for manufacturing the card, so they should be safe. Good luck. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[DPU PATCH v2 0/2] Add hardware catalog information in driver source for SDM845
by Sravanthi Kollukuduru 02 Apr '18

02 Apr '18

This patch series aims at adding the target specific hardware catalog information in driver source. As a result, the current logic of dt based parsing is removed. The DT clean up patch corresponding to this driver change will be posted separately. [V2] * Addressed Rob Herring's comment to update the commit message. * Addressed Sean's comment to restructure the catalog data in a way that different hardware versions can reuse. - Removed the target specific catalog file and moved the initialization logic to the main catalog file. Updated the driver patch title to reflect the same. - Added config handler structure to define the mapping between the hardware versions read from the register and the respective config init functions. - Added new structures for various sub blocks of the dpu driver and also, for any common configuration shared by the different blocks. Sravanthi Kollukuduru (2): dt-bindings: msm/disp: Remove hw block offset DT entries for SDM845 drm/msm: Add hardware catalog data in driver source for SDM845 .../devicetree/bindings/display/msm/dpu.txt | 530 --- drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 17 +- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 5 +- drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 3542 +++----------------- drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 124 +- drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c | 2 +- drivers/gpu/drm/msm/disp/dpu1/dpu_hw_top.c | 2 +- drivers/gpu/drm/msm/disp/dpu1/dpu_hw_wb.c | 2 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 5 +- drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 24 +- 10 files changed, 636 insertions(+), 3617 deletions(-) -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

3 5

[PATCH v2 0/6] drm/msm: Switch to atomic helpers
by Sean Paul 02 Apr '18

02 Apr '18

I noticed a couple of rough edges yesterday as I was running some tests, so here's v2 which fixes them. Most notably, I was experiencing issues when the crtc was being disabled with abandoned events and vblank timeouts. Note that I've bundled the private_obj change into this set since it shares the same theme. It's technically v5, but I'll label it v2 with the rest of the set. PTAL, Sean Sean Paul (6): drm/msm: Use drm_private_obj/state instead of subclassing drm/msm: Refactor complete_commit() to look more the helpers drm/msm: Mark the crtc->state->event consumed drm/msm: Issue queued events when disabling crtc drm/msm: Remove msm_commit/worker, use atomic helper commit drm/msm: Switch to atomic_helper_commit() drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c | 1 + drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c | 10 + drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c | 77 +++---- drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.h | 11 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_mixer.c | 12 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_pipe.c | 28 ++- drivers/gpu/drm/msm/disp/mdp5/mdp5_smp.c | 19 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_smp.h | 4 +- drivers/gpu/drm/msm/msm_atomic.c | 223 +-------------------- drivers/gpu/drm/msm/msm_drv.c | 95 ++++++++- drivers/gpu/drm/msm/msm_drv.h | 10 +- drivers/gpu/drm/msm/msm_kms.h | 21 +- 12 files changed, 204 insertions(+), 307 deletions(-) -- Sean Paul, Software Engineer, Google / Chromium OS

2 10

[Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
by bugzilla-daemon＠freedesktop.org 01 Apr '18

01 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=105425 --- Comment #12 from MirceaKitsune <sonichedgehog_hyperblast00(a)yahoo.com> --- Created attachment 138483 --> https://bugs.freedesktop.org/attachment.cgi?id=138483&action=edit Output of: watch cat /sys/kernel/debug/dri/0/amdgpu_pm_info I decided to turn my attention to the last logical thing I can imagine: DPM (Dynamic Power Management) and the clocks on my video card. The kernel added support for realtime tuning of the frequencies a while ago, so I was pondering if the default setup may have led to excess overclocking. I left a console to watch the file /sys/kernel/debug/dri/0/amdgpu_pm_info which I understand contains the video card frequencies. The maximum "power level" I seem to reach is 4, at sclk 101500 and mclk 140000. I'm attaching the peak output of this file here. My video card is supposed to run at 1015 MHz (core clock) + 5600 MHz (memory clock). I don't fully understand how those numbers translate to frequencies, but from what I heard that represents the MHz * 100. If such is the case, my GPU clock is just right whereas my VRAM is actually under-clocked to a quarter of its default frequency! Can anyone confirm this so at least the hypothesis of bad clocks is out of the way? I may try testing with the kernel parameters "radeon.dpm=0 amdgpu.dpm=0" later: I tried doing so briefly but the performance is too horrible to play a game, so I'll instead leave a bot match running in spectator mode while I'm away. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
by bugzilla-daemon＠freedesktop.org 01 Apr '18

01 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=105425 --- Comment #11 from MirceaKitsune <sonichedgehog_hyperblast00(a)yahoo.com> --- I'm still struggling to debug this. The more I see the more my jaw drops. First of all, the rule that disabling anti-aliasing decreases the frequency of the freeze (see the comments above) was just patched out: AA no longer has any effect either, it always freezes between 0 and 30 minutes now. I ran the following new tests in Xonotic, none of which had any influence: - Running with the following environment variable set: R600_DEBUG=checkir,precompile,nooptvariant,nodpbb,nodfsm,nodma,nowc,nooutoforder,nohyperz,norbplus,no2d,notiling,nodcc,nodccclear,nodccfb,nodccmsaa - Disabling all shaders, even turning off OpenGL 2.0 support entirely. - Resetting the entire BIOS to its failsafe defaults, making sure that neither overclocking nor any other settings are involved. - Running under both an X11 and Wayland session (Plasma). In Wayland it crashes instantly so it's even worse. - Verified that this occurs on both the "radeon" and "amdgpu" modules, meaning the video driver makes no difference either. It's clear to me at this point that this is the work of a professional: The code causing the crash is carefully maintained and injected into my system. If this was just a bug, at least one of the countless things I tried would have affected it somehow, it's impossible for a randomly occurring bug to survive so many different settings and environments... the issue instead is adaptive, so that the moment I find and disable one implementation another is activated within minutes to keep the crashes going. I imagine the objective is to block the user from finding a solution and ultimately censor them from using specific programs. I find it unbelievable that someone out there is actively doing this. Please help me get to the bottom of this: The crash clearly acts by simulating some sort of bug, so there must be a vulnerability deep in the system which hidden code is exploiting. I offered a lot of test data on this report: If the developers read this, please let me know what to try next! -- You are receiving this mail because: You are the assignee for the bug.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2018