dri-devel March 2016

dri-devel@lists.freedesktop.org

206 participants
1222 discussions

[Bug 94689] Two monitor DisplayPort MST DaisyChain (Second/Last Monitor In Chain Black Screen)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94689 Bug ID: 94689 Summary: Two monitor DisplayPort MST DaisyChain (Second/Last Monitor In Chain Black Screen) Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: mike.ennen(a)gmail.com As per our chat in #radeon (I am brcolow). Here is the dmesg with dri.debug=6: https://gist.github.com/brcolow/e27a5e46b175dd0966af Here is /sys/kernel/debug/dri/0/radeon_mst_info contents: mst: ffff88061cedfb40, 0 port: 1: ddps: 1 ldps: 0, sdp: 1/1, ffff8800bb193000, conn: ffff880622b27000 port: 8: ddps: 1 ldps: 0, sdp: 1/1, ffff8800bb192800, conn: ffff880622049000 port: 0: ddps: 1 ldps: 0, sdp: 0/0, ffff8800bb192000, conn: (null) vcpi: 7 3 vcpi 0: 8 1 22 vcpi 1: 1 2 22 vcpi 2:unsed vcpi 3:unsed vcpi 4:unsed vcpi 5:unsed payload 0: 2, 1, 22 payload 1: 2, 23, 22 payload 2: 0, 45, 0 payload 3: 0, 45, 0 payload 4: 0, 45, 0 payload 5: 0, 45, 0 dpcd: 12 14 c4 01 01 01 01 81 02 00 06 00 00 00 00 faux/mst: 00 01 mst ctrl: 07 branch oui: 00e04c devid: Dp1.2 revision: hw: 0.0 sw: 0.0 payload table: 07 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 attrib 0: 4 22 attrib 1: 2 22 The two monitors that are being daisy-chained are Dell UltraSharp U2715H's. GPU is Radeon R9 290. I have tried doing: xrandr --output DisplayPort-0-1 --rate X where X = 59.9, 60, 49.9, 50, 39.9, 40 etc but it doesn't seem to change anything (and this is the extent of my debugging abilities). -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 94502] R9-270 has no video output when underclocked
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94502 Bug ID: 94502 Summary: R9-270 has no video output when underclocked Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: maweki(a)gmail.com I have a Radeon R9-270 and I am running Fedora 23 with the default OpenSource drivers supplied with the repository. Yesterday I did an Update from Kernel 4.3.3-300 to 4.4.3-300 and I started seeing some issues. When I do nothing for about 12 seconds the screens (dual head) turn blank. Moving the mouse makes the screen go back on again. Sometimes the login-screen of the gnome-shell or chrome are frozen but the system as a whole seems fine. During normal operations /sys/kernel/debug/dri/0/radeon_pm_info is the following: power level 0 sclk: 30000 mclk: 120000 vddc: 950 vddci: 1000 pcie gen: 2 When the screen is still for a bit (exactly when it turns blank) the output is power level 0 sclk: 30000 mclk: 15000 vddc: 900 vddci: 850 pcie gen: 2 So apparently, when the video card is clocked down, the output is deactivated. My current "workaround" is running videos on the side - not an ideal solution. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 94484] Kernel BUG with latest radeon driver
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94484 Bug ID: 94484 Summary: Kernel BUG with latest radeon driver Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: tyler.brock(a)gmail.com Created attachment 122213 --> https://bugs.freedesktop.org/attachment.cgi?id=122213&action=edit journalctl output when radeon driver crashes Hey everyone, I'm running Linux 4.4.5 and Radeon driver xf86-video-ati 1:7.6.1 on wayland. I had no problems about a week ago but since using this version I frequently go to wake up my display by hitting a key on keyboard or moving the mouse and find that my computer has completely crashed (requiring a hard reboot). I've included the relevant output from journalctl. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 93895] GPU lockup on AMD A4-3400 APU when starting X server on opensource drivers. (works fine with fglrx)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93895 Bug ID: 93895 Summary: GPU lockup on AMD A4-3400 APU when starting X server on opensource drivers. (works fine with fglrx) Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: azari4096(a)gmail.com I've had this lockup on this machine for the past few years, across several different kernel versions, different distributions, etc. Booting with KMS works fine, but the second a graphical environment starts (whether X or wayland-based), it locks up. Booting Ubuntu with user-space mode-setting works, and then I can install FGLRX from there and everything works fine. After speaking with airlied on IRC, they suggested it could be a workaround that AMD has put into FGLRX that never made it into the opensource drivers, and that AMD might have to look into it. CPU/GPU : A4-3400 Motherboard : GA-A75M-D2H ( http://www.gigabyte.com/products/product-page.aspx?pid=3930#ov ) journalctl log of the lockup: ------------------------------------------------------------ Jan 27 18:28:32 miku dbus-daemon[374]: Successfully activated service 'org.freedesktop.systemd1' Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more than 10000msec Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0) Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: Saved 55 dwords of commands on ring 0. Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU softreset: 0x00000009 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS = 0xB1403828 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0 = 0x28000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1 = 0x00000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS = 0x20000840 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008678_CP_STALLED_STAT2 = 0x40000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT = 0x00008000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT = 0x80228643 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_SOFT_RESET=0x00007F6B Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_SOFT_RESET=0x00000100 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS = 0x00003828 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0 = 0x00000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1 = 0x00000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS = 0x20000040 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU reset succeeded, trying to resume Jan 27 18:28:42 miku kernel: [drm] Found smc ucode version: 0x00011100 Jan 27 18:28:42 miku kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000). Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: WB enabled Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800c613fc00 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800c613fc0c Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90002432118 Jan 27 18:28:42 miku kernel: [drm] ring test on 0 succeeded in 1 usecs Jan 27 18:28:42 miku kernel: [drm] ring test on 3 succeeded in 3 usecs Jan 27 18:28:42 miku kernel: [drm] ring test on 5 succeeded in 1 usecs Jan 27 18:28:42 miku kernel: [drm] UVD initialized successfully. Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more than 10370msec Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000000002 last fence id 0x0000000000000004 on ring 0) Jan 27 18:28:52 miku kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). Jan 27 18:28:52 miku kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35). Jan 27 18:29:22 miku systemd[1]: Started Getty on tty2. ------------------------------------------------------------ -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 93879] kernel 4.4.0 causes application lockup and unusable interfaces with radeon hardware
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93879 Bug ID: 93879 Summary: kernel 4.4.0 causes application lockup and unusable interfaces with radeon hardware Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: jimmy(a)boombatower.com Created attachment 121320 --> https://bugs.freedesktop.org/attachment.cgi?id=121320&action=edit sh -c "cat /proc/version; ./scripts/ver_linux; cat /proc/cpuinfo; cat /proc/modules; cat /proc/ioports; cat /proc/iomem; lspci -vvv; cat /proc/scsi/scsi" > env_info While running Plasma 5 on 4.4.0 the following occurs periodically: - chromium locks up - plasma desktop locks up - unable to enter password on plasma lock screen A trigger for locking chromium up seems to be to resize the window by dragging to screen edges (top to fullscreen, left to tack up left half of screen, etc). Otherwise, it also seems to somewhat randomly freeze over time. Reverting to 4.3.x resolves the issues. Environment ----------- Distro: openSUSE Tumbleweed (20160121) (x86_64) Kernel version: 4.4.0-1.2 (works on <= 4.3.3-6) OpenGL renderer string: Gallium 0.4 on AMD TAHITI (DRM 2.43.0, LLVM 3.7.0) OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.1.0 Xorg version: 7.6_1.18.0-5.2 xf86-video-ati version: 7.6.1-1.2 DRI3 enabled Hardware: Radeon HD 7970 ghz output from kernel bug reporting guide attached -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 93826] 144Hz graphic glitches and bad resolution
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93826 Bug ID: 93826 Summary: 144Hz graphic glitches and bad resolution 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: dherault(a)hotmail.com Created attachment 121218 --> https://bugs.freedesktop.org/attachment.cgi?id=121218&action=edit 290X Bad 144Hz OS : Arch linux GPU : Sapphire R9 290X Other GPU to test : Sapphire 7950. Screen : Asus MG279Q 1440p 144Hz. DRI provides false frequency refresh the screen with R9 290X. No issues with 7950. With 7950 Xrandr is set @143.86Hz. 144 Hz on screen OSD : http://reho.st/self/81f168d18def02417d2bd22867bc728658ec63e4.jpg With 290X Xrandr is also set @143.86Hz. 139 Hz on screen OSD : http://reho.st/self/b98c1c955cb7d42c3af6f82ea71bbc94be8aee6a.jpg With 290X a lot of glitches with false 144Hz. The erroneous résolution cause glitches. - Lines on the left (from grub to kde...) http://reho.st/view/self/ddfb4104cbbb09b7654b5fa610806d2477850128.jpg http://reho.st/thumb/self/d3be18d9d93500f7395edbf58407f066500e980a.jpg - Blur on all screen - Text glitches http://reho.st/thumb/self/b8fcd4246964f02c400e131bb54e0e8d2aa5101d.jpg Thanks Damien -- You are receiving this mail because: You are the assignee for the bug.

1 85

[Bug 93819] R9 390: [drm:radeon_vce_ring_test] *ERROR* ring 6 test failed after resume from hibernate
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93819 Bug ID: 93819 Summary: R9 390: [drm:radeon_vce_ring_test] *ERROR* ring 6 test failed after resume from hibernate 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: h.judt(a)gmx.at Created attachment 121201 --> https://bugs.freedesktop.org/attachment.cgi?id=121201&action=edit dmesg1 It does not happen always, but usually after a few hibernate/resume cycles (2 or 3, sometimes earlier). The following messages can be found in dmesg (see attachment for full output). [ 1001.941216] [drm] ring test on 0 succeeded in 0 usecs [ 1001.941331] [drm] ring test on 1 succeeded in 0 usecs [ 1001.941370] [drm] ring test on 2 succeeded in 0 usecs [ 1001.941565] [drm] ring test on 3 succeeded in 0 usecs [ 1001.941571] [drm] ring test on 4 succeeded in 0 usecs [ 1001.967662] [drm] ring test on 5 succeeded in 0 usecs [ 1001.967696] [drm] UVD initialized successfully. [ 1002.249117] [drm:radeon_vce_ring_test] *ERROR* radeon: ring 6 test failed] [ 1002.249139] [drm] ib test on ring 0 succeeded in 0 usecs [ 1002.749193] [drm] ib test on ring 1 succeeded in 0 usecs [ 1002.749221] [drm] ib test on ring 2 succeeded in 0 usecs [ 1002.749304] [drm] ib test on ring 3 succeeded in 0 usecs [ 1002.749354] [drm] ib test on ring 4 succeeded in 0 usecs [ 1003.269160] [drm] ib test on ring 5 succeeded [ 1013.788806] radeon 0000:01:00.0: ring 7 stalled for more than 10000msec [ 1013.788809] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000008 last fence id 0x000000000000000a on ring 7) [ 1013.788868] [drm:radeon_vce_ib_test] *ERROR* radeon: fence wait failed (-35). [ 1013.788874] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 7 (-35). After that, if the machine hibernates and resumes once again, additional errors will be printed and the X session becomes unusable (only the cursor blinking on the terminal). I will attach the dmesg of this too, though it might be less interesting. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 93809] playing Just Cause causes system crash
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93809 Bug ID: 93809 Summary: playing Just Cause causes system crash Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: aaalmosss(a)gmail.com It happens randomly, usually when lots of things are happening, like during settlement takeovers. The screen freezes, sound stops, and only the magic sysrq keys are working. GPU is Radeon R9 270x, Linux 4.3.3, libdrm 2.4.66, Mesa 11.1.1, wine 1.7.55. I also tried gallium nine, and that made it more unstable, it crashes even when just riding around. BTW nine doesn't help with the horrible performance (5-15 fps), but it introduces several graphical glitches. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 93753] Sometimes wrong clk frequency of Display after dpms mode changes.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93753 Bug ID: 93753 Summary: Sometimes wrong clk frequency of Display after dpms mode changes. Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: t.graziadei(a)bachmann.info Created attachment 121103 --> https://bugs.freedesktop.org/attachment.cgi?id=121103&action=edit Screenshot of failure Sometimes after the deactivation of the screensaver or also on bootup the screen shows flickering noise and a duplicated screen image. (Attached there is the used test image and a screenshot of the failure image). We tested on various kernel versions, latest kernel tested was 4.4.0. We run a customized debian image. Further investigations showed, that in the failure scenario the measured clk frequency was only 25MHz but it should be 35MHz. We also tried to deactivate dpms completly (radeon.dpm=0 in kernel parameters) and also turned the dpms off in the screensaver, but we still sometimes encounter the problem after a reboot. Attached you will find a dmesg output with drm.debug=0xf activated. We use a Radeon PALM on a AMD G-T40E 2x1GHz -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 93713] System hangs (beomes totaly unresponsive) when trying to use hybrid graphics with ATI 7730M videocard
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93713 Bug ID: 93713 Summary: System hangs (beomes totaly unresponsive) when trying to use hybrid graphics with ATI 7730M videocard 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: g0000ga(a)gmail.com When trying to use my discrete video card whole system freezes after couple of seconds and doesn't react on anything. I've tried to have a delayed killall -9 running in the background like "sleep 60 && killall -9 glmark2 &" but it seems to be never run or having no effect. Only hard reset helps. Have Intel HD4000 + muxless Radeon 7730M [g0ga@work ~]✘ xrandr --setprovideroffloadsink radeon Intel [g0ga@work ~]✘ DRI_PRIME=1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE (DRM 2.43.0, LLVM 3.7.0) doesn't matter what to run, everything is going to die. kernel 4.3.3 + xorg 1.18.0, archlinux distribution, most recent at time of writing this post. Please let me know how to provide more data for you being able to debug this. Thanks, Victor -- You are receiving this mail because: You are the assignee for the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2016