dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 99143] r9 390: Hardware cursor invisible after hibernate/resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99143 Bug ID: 99143 Summary: r9 390: Hardware cursor invisible after hibernate/resume 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: h.judt(a)gmx.at I have merged https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.10-wip into 4.9, as this solves the failures to hibernate/resume on my machine with the r9 390. The only problem with hibernation left now is that the HW cursor vanishes after hibernating and resuming. Widgets still get focused, only the cursor is no longer visible. Switching to software cursor as a workaround solves this. lspci: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390] (rev 80) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] Using xorg-server-1.18.4, libdrm-git, mesa-git and xf86-video-amdgpu-git. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 98901] amdgpu doesn't reinitialize after reboot in Xen PV DomU
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98901 Bug ID: 98901 Summary: amdgpu doesn't reinitialize after reboot in Xen PV DomU 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: msgctl(a)centzontotochtin.org Created attachment 128264 --> https://bugs.freedesktop.org/attachment.cgi?id=128264&action=edit Logs from Xen Dom0 and affected DomU I'm not sure whether this is a Xen or amdgpu bug. amdgpu consistently does not reinitialize after paravirtualized Xen DomU reboots. It's a PCI passthrough setup - the physical machine does not reboot and it can't reset PCI Express devices. This setup is working fine until I need to reboot the affected DomU. DomU: Debian testing (29-11-2016) Linux version 4.7.0-1-amd64 Dom0: Debian GNU/Linux 8.6 (jessie) Linux 3.16.0-4-amd64 Graphics adapter: Radeon RX480 I attached an archive with all the relevant logs I could gather. Please contact me for further information/testing. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 98730] On kernel startup, all monitors will go blank and stay blank with newest amd-staging-4.7
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98730 Bug ID: 98730 Summary: On kernel startup, all monitors will go blank and stay blank with newest amd-staging-4.7 Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: guido-xorgbugs(a)unknownsite.de When booting with the newest kernel from the amd-staging-4.7 branch from https://cgit.freedesktop.org/~agd5f/linux/, all connected monitors will go blank and stay blank indefinitely. The power indicator on the monitors will start to blink as if there was no signal. This is with commit 680da8633ae17cdea8fddd1ede87253325c8ca25. With an older commit, d330e1e9c232895dbd0c183a647d41d54ecc0884, this branch still works. DAL is enabled in the config in both cases. The graphics card is a Sapphire Nitro Radeon R9 380X. There are three monitors connected in total, one to the DVI-I port, one to the DVI-D port and one to the DisplayPort. I am using this particular branch as a workaround for the bug described in https://bugs.freedesktop.org/show_bug.cgi?id=91202 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 98513] [4.9-rc3 w/ drm-next-4.10-wip][AMDGPU][CIK] Unable to suspend, hangs on hibernation
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98513 Bug ID: 98513 Summary: [4.9-rc3 w/ drm-next-4.10-wip][AMDGPU][CIK] Unable to suspend, hangs on hibernation Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: shawn.starr(a)rogers.com Something regressed for CIK on AMDGPU, I am unable to hibernate anymore, hangs laptop when it attempts to freeze(). -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 98461] Radeon and 5k resolution 5120x2880 = corrupted image
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98461 Bug ID: 98461 Summary: Radeon and 5k resolution 5120x2880 = corrupted image 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: blesk2(a)gmail.com Created attachment 127570 --> https://bugs.freedesktop.org/attachment.cgi?id=127570&action=edit Photo of display I try to set 2560x2880 resolution on DisplayPort-0 and the same resolution on DisplayPort-1, but screen is wobbly and distorted. xrandr --output DisplayPort-0 --mode 2560x2880 --right-of DisplayPort-1 --output DisplayPort-1 --mode 2560x2880 xrandr Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384 DisplayPort-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 60.00 + 60.00 2560x1440 59.95*+ 2560x2880 59.98 29.99 1920x1200 59.88 1920x1080 60.00 1600x1200 60.00 1680x1050 59.95 1280x1024 60.02 1280x800 59.81 1024x768 60.00 800x600 60.32 640x480 60.00 59.94 DisplayPort-1 connected (normal left inverted right x axis y axis) 848x480 59.74 + 2560x2880 59.98 29.99 Monitor: Dell UP2715K VGA: AMD FirePro W2100 It is related with Bug id 97244 (5k resolution but on Intel card). -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 98417] TTM broken on 4.9-rc2
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98417 Bug ID: 98417 Summary: TTM broken on 4.9-rc2 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: krejzi(a)email.com Created attachment 127520 --> https://bugs.freedesktop.org/attachment.cgi?id=127520&action=edit dmesg As the title says. Relevant dmesg output: [ 12.409144] ttm: no symbol version for memcpy [ 12.409146] ttm: Unknown symbol memcpy (err -22) [ 12.409167] ttm: no symbol version for clear_page [ 12.409167] ttm: Unknown symbol clear_page (err -22) [ 12.409178] ttm: no symbol version for copy_page [ 12.409179] ttm: Unknown symbol copy_page (err -22) [ 12.409204] ttm: no symbol version for phys_base [ 12.409205] ttm: Unknown symbol phys_base (err -22) [ 12.409216] ttm: no symbol version for memset [ 12.409216] ttm: Unknown symbol memset (err -22) [ 12.409219] ttm: no symbol version for ___preempt_schedule [ 12.409219] ttm: Unknown symbol ___preempt_schedule (err -22) Full dmesg output and kernel config are attached. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98333 Bug ID: 98333 Summary: 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL 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: dillondixon(a)gmail.com So this is regarding AMDGPU DAL as it currently exists in https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.7, which from my understanding contains the most up-to-date public-facing iteration of the DAL patch. So I have an HDMI 2.0 4K 60 Hz monitor (Vizio D40u-D1) as my main display connected to an XFX RX 480. I'm using a kernel compiled from the branch listed above. Now the issue I'm having is that I'm stuck at 30 Hz. The RX 480 is capable of driving this monitor at 60 Hz @ 4K, which works under Windows. Trying to switch to 60 Hz either results in no signal, or just 30 Hz again. I had the same issue in the past with the proprietary Linux Nvidia drivers on a 960 GTX I used to own, and after several months, the devs there were able to figure out what the issue is, describe it in a forum post, and get a fix in. See here: https://devtalk.nvidia.com/default/topic/939971/linux/4k-60hz-works-in-wind… So what I'm hoping is that a similar fix would work in DAL. I can provide logs on request (not sure to log right now). Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 98324] amd-staging-4.7: problems with unblanking displays when monitors are switched off
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98324 Bug ID: 98324 Summary: amd-staging-4.7: problems with unblanking displays when monitors are switched off Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: bugspam(a)moreofthesa.me.uk Created attachment 127405 --> https://bugs.freedesktop.org/attachment.cgi?id=127405&action=edit Kernel log extract, showing the unblanking failure. Setup: RX 470 with two monitors attached – one via DVI-and one via HDMI. (Both are AOC monitors.) * Ensure that outputs are blanked (via xset, time-out or similar). * Switch off the monitors. * Unblank the outputs. * Switch on the monitors. Invariably, in this situation, the DVI-connected monitor is unblanked and displaying what it should be, but the HDMI-connected monitor is receiving no signal (or at least nothing to display) and is therefore displaying nothing. The HDMI-connected monitor can be restored by using xrandr to change mode or by blanking and unblanking – so long as it's switched on while doing so. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 98276] Kernel Panic on shutdown caused by "drm/amdgpu: always apply pci shutdown callbacks"
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98276 Bug ID: 98276 Summary: Kernel Panic on shutdown caused by "drm/amdgpu: always apply pci shutdown callbacks" Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: johannes.hirte(a)datenkhaos.de Kernel 4.9-rc1 fails on shutdown/reboot with a panic. Bisect pointed me to 00ea8cba5ef7b783f11cb1a0b900b7c18d2ce0b6 is the first bad commit commit 00ea8cba5ef7b783f11cb1a0b900b7c18d2ce0b6 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Thu Sep 22 14:40:29 2016 -0400 drm/amdgpu: always apply pci shutdown callbacks (v2) We can't properly detect all hypervisors and we need this to properly tear down the hardware. v2: trivial warning fix Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> :040000 040000 868a00ff980f95dac82b908df0737342bf40cdc3 02bf2cf4e8797d37d454301afedf2f97735b60ca M drivers After removing this commit, everything works again. System is a Carrizo. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 98183] [amdgpu SI] "gpu fault detect" in Alien: Isolation
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98183 Bug ID: 98183 Summary: [amdgpu SI] "gpu fault detect" in Alien: Isolation Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: arek.rusi(a)gmail.com Created attachment 127168 --> https://bugs.freedesktop.org/attachment.cgi?id=127168&action=edit kernel log Hi, kernel - drm-next-4.9-wip + drm/amdgpu: disable CRTCs before teardown mesa,libdrm,amdgpu,llvm form git/svn This is not regression, this happened since dpm is workable. GPU/VM faults appears during loading game only, menu/gameplay(20min) looks normal. Probably this problem doesn't performance impact, frame rate is the same as for radeon. -- 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 July 2017