dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 91790] TONGA hang in amdgpu_ring_lock
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91790 Bug ID: 91790 Summary: TONGA hang in amdgpu_ring_lock 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: master.homer(a)gmail.com Created attachment 117962 --> https://bugs.freedesktop.org/attachment.cgi?id=117962&action=edit dmesg of hang I've been getting random hangs in amdgpu_ring_lock, this causes X to hang, meaning I can't use the computer at all. I can sometimes switch to a tty, but this doesn't always work either. I'm running Ubuntu 15.04 with mesa and libdrm from the oibaf ppa, with a self-compiled xf86-video-amdgpu and a self-compiled kernel from agd5f, drm-next-4.3-wip (9066b0c318589f47b754a3def4fe8ec4688dc21a). I haven't been able to predict when the hang will happen, sometimes I can use it for several hours before it hangs, other times it happens just a few minutes after booting. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 91727] alloca means including <alloca.h> on SunOS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91727 Bug ID: 91727 Summary: alloca means including <alloca.h> on SunOS Product: DRI Version: XOrg git Hardware: Other OS: Solaris Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: richard(a)netbsd.org came across this issue in amdgpu/amdgpu_cs.c while building libdrm-2.4.64 The following patch get over it for me: >$NetBSD: patch-amdgpu_amdgpu__cs.c,v 1.1 2015/08/18 13:26:29 richard Exp $ >at least on SunOS, alloca needs alloca.h >--- amdgpu/amdgpu_cs.c.orig 2015-08-13 22:27:03.000000000 +0000 >+++ amdgpu/amdgpu_cs.c >@@ -32,7 +32,9 @@ > #include <pthread.h> > #include <sched.h> > #include <sys/ioctl.h> >- >+#ifdef HAVE_ALLOCA_H >+#include <alloca.h> >+#endif > #include "xf86drm.h" > #include "amdgpu_drm.h" > #include "amdgpu_internal.h" -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 91386] Tonga HDMI Audio needs CPU load
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91386 Bug ID: 91386 Summary: Tonga HDMI Audio needs CPU load 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: adf.lists(a)gmail.com There are other reports I know for 270x/280x about HDMI audio needing CPU load I've been testing again on this issue recently with R9 285 and wanted to get a clean report out. Cpu phenom II x4 965be now in a new mobo (asrock) with the tonga. Previous mobo (asus) with 270x also had the issue. I see from other si bugs that people with intel cpu/boards are also affected. rv 790 and onboard rs880 on old mobo didn't have the issue. rv770 on current setup didn't have the issue. Symptoms are that with no cpu load it sounds like the same buffer gets played out repeatedly. With a bit more load progress can be made but there are repeats as well. With almost enough load sounds like a bit of analogue crackle. I've recently found that saying "cpu load" is not really accurate - I can spin cpus without curing the sound, with eg. dd if=/dev/urandom of=/dev/null or tests like cpuburn-1.4a and certain p95/mprime loads. Using mprime it seems what is needed is actually ram/memory controller load. The "torture test" has three options described as - Choose a type of torture test to run. 1 = Small FFTs (maximum heat and FPU stress, data fits in L2 cache, RAM not tested much). 2 = In-place large FFTs (maximum power consumption, some RAM tested). 3 = Blend (tests some of everything, lots of RAM tested). 1 = no fix, 2 = better than 1 but nowhere near right, 3 = OK sound. Historically and recently I've tried many things with no luck - Many sound debugging options, building without hres timers. Disabling cool n quiet in bios. Testing with different hdmi sinks/modes/sample rates/sizes. I only till now used LFS + alsa but now pulse also tested as - Yesterday I dug up an old HD and installed ubuntu 15.04 and installed/updated fglrx - it also has the issue (I was kind of hoping it wouldn't so regs could be compared). The issue does not exist if I boot into windows 7 (unless it's fooling me by always doing something behind the scenes!) So where to go from here? First thought - is there an obvious difference between the way the pre-si driver code does things and what code later h/w hits? Does the type of load needed give any clues? Do people have this h/w on setups without the issue? I don't know what proportion will test HDMI and then they may just look to eg. the kodi forums and be told it's a known issue rather than filing new bugs/adding "a me too". Anything else to test that I've missed? I don't mind spraying printfs/changing things, but don't really know where to start in the code. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 91371] Tonga HDMI Audio none on TV working on monitor - possible eld issue
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91371 Bug ID: 91371 Summary: Tonga HDMI Audio none on TV working on monitor - possible eld issue 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: adf.lists(a)gmail.com I have so far not managed to get any HDMI audio from my TV via R9 285. I can get HDMI sound when connected to a monitor (with cpu load) With other h/w this TV has recently been OK with a bit of messing around eg. extra run of xrandr + cpu load for R9 270x. RS880 and rv770 worked without the cpu load. Added complication since getting a new mobo I sometimes get i2c edid read fails on the TV - but then it's not always and the rv770 produced them and worked and the tonga always works for sound with the TV in windows. I noticed that for the TV the eld does not match what edid decode reports - it only shows one sample rate and shows "Fl/Fr C" when it's only 2 channel. TBH I don't know what eld said historically with different h/w. edid-decode and eld for TV attached. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 91202] output to DVI-I is blank
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91202 Bug ID: 91202 Summary: output to DVI-I is blank 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: bpaterni(a)gmail.com Created attachment 116902 --> https://bugs.freedesktop.org/attachment.cgi?id=116902&action=edit dmesg for e965b8ce4215ac2b22b23ffc8a8dfbae964b9496 I have a radeon r9 285 (tonga) and I'm trying to run dual DVI displays via the new AMDGPU driver. The problem I'm having though is that the display connected to the DVI-I output goes blank during drm initialization on boot, and thereafter never 'recovers'. If I plug either DVI-D or DVI-I in individually, however, and disconnect the other on a fresh boot, either outputs work just fine. Additionally, dual displays do work if I use any combination of DVI-D, HDMI, or DisplayPort; which leads me to believe that the problem has something to do with how amdgpu is handling output to DVI-I or a hardware problem. Hopefully it is not the latter. Please let me know if there is anything I can do to help debug this problem! I'm using Debian unstable, with the latest linux kernel compiled from git mainline (e965b8ce4215ac2b22b23ffc8a8dfbae964b9496) dmesg and Xorg log should be attached. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 100109] Graphics Lockup if monitor disconnected and then set into standby
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100109 Bug ID: 100109 Summary: Graphics Lockup if monitor disconnected and then set into standby Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: kierangrant(a)linux.com Created attachment 130119 --> https://bugs.freedesktop.org/attachment.cgi?id=130119&action=edit Various log files I got a Kernel Oops from with AMDGPU-PRO for Ubuntu 16.04.2 LTS x86-64 version 16.60 after unplugging and plugging in my HDMI display... Computer was left on overnight to do some long IO operation... before I left it, I turned monitor off... at the time my MATE display settings was to put monitor to sleep after 30 minutes... so I guess it tried that after 30 minutes... Next day... I got no graphics response... after trying various F-n combos... I eventually tried some SysRq keys to force text console... but stock Ubuntu SysRq limit was in effect *doh*... That is when as a last resort thought to unplug and re-plug in monitor... in hopes that would magically do something... it did something alright... I got Kernel OOPS at that moment... it was early morning for me :| Attached is a snippet of my syslog plus various ls* outputs... I have a MSI Radeon RX480 8GB I will see if I can manually reproduce the bug to get a Xorg.log file... I forgot that one and old one is now gone :/ -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 97548] DPM states not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97548 Bug ID: 97548 Summary: DPM states not working Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: jarkko_korpi(a)hotmail.com I am using 4.6-staging because I need the audio driver it provides. I have been trying to lower the voltages of the card by bios editing and there seems to be no issues with windows, but I dont seem to get higher DPM states in use at linux. Something is broken. dmesg is spammed with these amdgpu-pro, mint 18, rx480. Latest 4.6 kernel from git (agd5f/linux). [ 1214.592256] VM fault (0x14, vmid 6) at page 1071080, write from 'CB0' (0x43423000) (96) [ 1214.592262] amdgpu 0000:01:00.0: GPU fault detected: 146 0x059aa504 [ 1214.592262] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D2 [ 1214.592263] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0D0014 [ 1214.592264] VM fault (0x14, vmid 6) at page 1071058, write from 'CB7' (0x43423700) (208) [ 1214.592269] amdgpu 0000:01:00.0: GPU fault detected: 146 0x059a5504 [ 1214.592270] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D8 [ 1214.592271] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D020014 [ 1214.592271] VM fault (0x14, vmid 6) at page 1071064, write from 'CB2' (0x43423200) (32) [ 1214.592642] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f2ad014 [ 1214.592643] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057E9 [ 1214.592643] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C0D000C [ 1214.592644] VM fault (0x0c, vmid 6) at page 1071081, read from 'CB7' (0x43423700) (208) [ 1214.592650] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f2aa014 [ 1214.592650] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D8 [ 1214.592651] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C02000C [ 1214.592652] VM fault (0x0c, vmid 6) at page 1071064, read from 'CB2' (0x43423200) (32) [ 1214.592657] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f60e00c [ 1214.592658] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057EC [ 1214.592659] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0E0014 [ 1214.592659] VM fault (0x14, vmid 6) at page 1071084, write from 'CB6' (0x43423600) (224) [ 1214.592665] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f28a00c [ 1214.592666] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D0 [ 1214.592666] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0E0014 [ 1214.592667] VM fault (0x14, vmid 6) at page 1071056, write from 'CB6' (0x43423600) (224) [ 1214.592673] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0ec25014 [ 1214.592673] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D2 [ 1214.592674] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D060014 [ 1214.592675] VM fault (0x14, vmid 6) at page 1071058, write from 'CB0' (0x43423000) (96) [ 1214.661835] steam[6544]: segfault at 4184ddd7 ip 00000000f72ea771 sp 00000000ff9ce690 error 4 in libc-2.23.so[f727d000+1af000] [ 1353.103633] failed to send pre message 200 ret is 0 [ 1353.317672] failed to send message 200 ret is 0 [ 1353.536394] failed to send pre message 201 ret is 0 [ 1353.754228] failed to send message 201 ret is 0 [ 1961.904046] failed to send pre message 200 ret is 0 [ 1962.120865] failed to send message 200 ret is 0 [ 1962.342261] failed to send pre message 201 ret is 0 [ 1962.560233] failed to send message 201 ret is 0 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 97221] monitor miss detection, philips 242G5
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97221 Bug ID: 97221 Summary: monitor miss detection, philips 242G5 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: ken(a)kenjo.org Created attachment 125566 --> https://bugs.freedesktop.org/attachment.cgi?id=125566&action=edit dmesg This is a 144Hz display but that is not showing up in xrandr as an option for nay resolution. DisplayPort-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 50.00 59.94 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 97220] miss detect monitor. dell UP3214Q
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97220 Bug ID: 97220 Summary: miss detect monitor. dell UP3214Q Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: ken(a)kenjo.org Created attachment 125565 --> https://bugs.freedesktop.org/attachment.cgi?id=125565&action=edit dmesg Dell UP3214Q is a MST Monitor and proper detection is needed for it to operate in 60HZ mode. It is miss detected and only show up as supporting 30Hz max. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 96906] OpenCL program causes steady stream of GPU fault detected errors
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=96906 Bug ID: 96906 Summary: OpenCL program causes steady stream of GPU fault detected errors Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: jolan(a)jolan.org Hi, I have an OpenCL program which causes a steady stream of errors: kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x03f84801 kernel: VM fault (0x01, vmid 6) at page 135290494, read from 'TC7' (0x54433700) (132) kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C084001 kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E7E kernel: amdgpu 0000:05:00.0: GPU fault detected: 147 0x03f08401 kernel: VM fault (0x01, vmid 3) at page 135290494, read from 'TC2' (0x54433200) (200) kernel: amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x060C8001 kernel: amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E7E kernel: amdgpu 0000:04:00.0: GPU fault detected: 147 0x03f0c801 kernel: VM fault (0x01, vmid 6) at page 135290495, read from 'TC1' (0x54433100) (4) kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C004001 kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E7F AMDGPU-Pro: 16.30.3.306809 Kernel: 4.7.0-rc6-mainline GPU: RX480 -- 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 July 2017