[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #1 from tempel.jul...@gmail.com --- Created attachment 143963 --> https://bugs.freedesktop.org/attachment.cgi?id=143963&action=edit dmesg log -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110417 Bug ID: 110417 Summary: regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS:

[Bug 110418] Unresolved compilation problems

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110418 Bug ID: 110418 Summary: Unresolved compilation problems Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Pri

[Bug 203301] New: amdgpu invalid connector error

2019-04-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203301 Bug ID: 203301 Summary: amdgpu invalid connector error Product: Drivers Version: 2.5 Kernel Version: 5.1.0-rc4+ actual git master Hardware: All OS: Linux Tree

[Bug 110420] Exception in thread "main" java.lang.Error: Unresolved compilation problems

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110420 Bug ID: 110420 Summary: Exception in thread "main" java.lang.Error: Unresolved compilation problems Product: DRI Version: XOrg git Hardware: Other OS: All

[Bug 110421] Exception in thread "main" java.lang.Error: Unresolved compilation problems

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110421 Bug ID: 110421 Summary: Exception in thread "main" java.lang.Error: Unresolved compilation problems Product: DRI Version: XOrg git Hardware: Other OS: All

[Bug 110416] Newly installed Kubuntu 18.04 brokes after try to install amdgpu for RX 550

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110416 Alex Deucher changed: What|Removed |Added Component|DRM/AMDgpu |DRM/AMDgpu-pro --- Comment #1 from Alex

[Bug 110422] AMD_DEBUG=forcedma will crash OpenGL aps with SIGFAULT on VegaM 8706G

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110422 Bug ID: 110422 Summary: AMD_DEBUG=forcedma will crash OpenGL aps with SIGFAULT on VegaM 8706G Product: Mesa Version: git Hardware: Other OS: All

[Bug 108309] Raven Ridge 2700U system lock-up on multiple games

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108309 --- Comment #9 from Cameron Banfield --- I can also confirm this issue. 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev d0) Lenovo ThinkPad A485 AMD Ry

[Bug 110423] Forced EDID is ignored

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110423 Bug ID: 110423 Summary: Forced EDID is ignored Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

[Bug 110423] Forced EDID is ignored

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110423 --- Comment #1 from Heiko Lechner --- I forgot: using amdgpu.dc=0 seems to respect the forced edid, the tv works fine but then I have no sound, so this is not really a workaround. -- You are receiving this mail because: You are the assignee fo

[PATCH 0/2] drm/exynos: clean up logs

2019-04-14 Thread Inki Dae
Just clean up logs from exynos drm driver. Inki Dae (2): drm/fimd: use DRM_ERROR instead of DRM_INFO in error case drm/exynos: remove unnecessary messages drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 2 -- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 8 +++- 2 files changed, 3 inse

[PATCH 1/2] drm/fimd: use DRM_ERROR instead of DRM_INFO in error case

2019-04-14 Thread Inki Dae
This patch makes error messages to be printed out using DRM_ERROR instead of DRM_INFO. Signed-off-by: Inki Dae --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos

[PATCH 2/2] drm/exynos: remove unnecessary messages

2019-04-14 Thread Inki Dae
This patch removes unnecessary messages from fimd_clear_channels and decon_clear_channels functions which print out just function name. Signed-off-by: Inki Dae --- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 2 -- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 -- 2 files changed, 4 delet

[Bug 110360] AMD system hits AMD-Vi: Completion-Wait loop timed out on Acer Squirtle_SR laptop

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110360 --- Comment #7 from jian-h...@endlessm.com --- Any thing else I can help more? Test or need more information, log? :) -- You are receiving this mail because: You are the assignee for the bug.___ dri-

Re: [PATCH 1/2] drm/fimd: use DRM_ERROR instead of DRM_INFO in error case

2019-04-14 Thread Sam Ravnborg
Hi Inki On Mon, Apr 15, 2019 at 09:47:19AM +0900, Inki Dae wrote: > This patch makes error messages to be printed out using DRM_ERROR > instead of DRM_INFO. > > Signed-off-by: Inki Dae > --- > drivers/gpu/drm/exynos/exynos_drm_fimd.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-)

Re: [PATCH 1/2] drm/fimd: use DRM_ERROR instead of DRM_INFO in error case

2019-04-14 Thread Inki Dae
Hi Sam, 19. 4. 15. 오후 12:17에 Sam Ravnborg 이(가) 쓴 글: > Hi Inki > > On Mon, Apr 15, 2019 at 09:47:19AM +0900, Inki Dae wrote: >> This patch makes error messages to be printed out using DRM_ERROR >> instead of DRM_INFO. >> >> Signed-off-by: Inki Dae >> --- >> drivers/gpu/drm/exynos/exynos_drm_fimd

[Bug 110360] AMD system hits AMD-Vi: Completion-Wait loop timed out on Acer Squirtle_SR laptop

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110360 --- Comment #8 from Alex Deucher --- https://patchwork.kernel.org/patch/10889269/ -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.f

[Bug 110360] AMD system hits AMD-Vi: Completion-Wait loop timed out on Acer Squirtle_SR laptop

2019-04-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110360 --- Comment #9 from Alex Deucher --- (In reply to Alex Deucher from comment #8) > https://patchwork.kernel.org/patch/10889269/ I think it's actually a problem with runtime pm and some pci state. I may ask you to help debug that when I get a ch

[pull] amdgpu, ttm drm-fixes-5.1

2019-04-14 Thread Alex Deucher
Hi Dave, Daniel, More fixes for 5.1: - GPUVM fixes for vega/RV and shadow buffers - TTM fixes for hugepages - TTM fix for refcount imbalance in error path - DC AUX fix for some active DP-DVI dongles - DC fix for multihead VT switch regression The following changes since commit d47703d43ecaa9189d7

Re: [PATCH 1/3] drm/ttm: Reset num_zones on ttm_mem_global cleanup

2019-04-14 Thread Koenig, Christian
Am 15.04.19 um 01:37 schrieb Brian Yip: > num_zones in the ttm_mem_global structure was never reset after calling > ttm_mem_global_release(). Consequently, when multiple GPU drivers > are loaded, and the first one fails to load its firmware, the second > driver will attempt to load its own firmware

Re: [PATCH 5/9] drm/ttm: TTM fault handler helpers

2019-04-14 Thread Christian König
Am 12.04.19 um 18:04 schrieb Thomas Hellstrom: With the vmwgfx dirty tracking, the default TTM fault handler is not completely sufficient (vmwgfx need to modify the vma->vm_flags member, and also needs to restrict the number of prefaults). We also want to replicate the new ttm_bo_vm_reserve() fu

Re: [PATCH 3/4] drm/amdgpu: Avoid HW reset if guilty job already signaled.

2019-04-14 Thread Koenig, Christian
Am 12.04.19 um 17:53 schrieb Grodzovsky, Andrey: > On 4/12/19 3:39 AM, Christian König wrote: >> Am 11.04.19 um 18:03 schrieb Andrey Grodzovsky: >>> Also reject TDRs if another one already running. >>> >>> v2: >>> Stop all schedulers across device and entire XGMI hive before >>> force signaling HW