[Bug 106851] WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() + drm:radeon_pm_late_init [radeon]] *ERROR*
https://bugzilla.kernel.org/show_bug.cgi?id=106851 lbl changed: What|Removed |Added Kernel Version|4.1.12-LTS |4.1.12, 4.2.5 -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 107001] New: Radeon HDMI audio lost after resuming from suspend
https://bugzilla.kernel.org/show_bug.cgi?id=107001 Bug ID: 107001 Summary: Radeon HDMI audio lost after resuming from suspend Product: Drivers Version: 2.5 Kernel Version: 4.2.0 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri at kernel-bugs.osdl.org Reporter: timo.valtoaho at gmail.com Regression: No Created attachment 191781 --> https://bugzilla.kernel.org/attachment.cgi?id=191781&action=edit output of scripts/ver_linux After switching to 4.2 series, I noticed that audio through HDMI was gone after first suspend/resume cycle (systemctl suspend). I can get audio back with some simple operations, like executing xrand, lanching gnome-control-center or swithcing to a virtual terminal (ctrl+alt+F1). All of these operations will restore audio. I have tested this out, and it was 4.2-rc2 that introduced this issue, and is still present in 4.3-rc7. Also, it doesn't matter whether radeon driver is a module or compiled in with required firmware. System is Debian Jessie (8.2), Gnome Output of scripts/ver_linux: Attached files: output of scripts/ver_linux output of lspci -vvv -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 107001] Radeon HDMI audio lost after resuming from suspend
https://bugzilla.kernel.org/show_bug.cgi?id=107001 --- Comment #1 from Timo Valtoaho --- Created attachment 191791 --> https://bugzilla.kernel.org/attachment.cgi?id=191791&action=edit putput of lspci -vvv -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 80419] XCOM: Enemy Unknown Causes lockup
https://bugs.freedesktop.org/show_bug.cgi?id=80419 --- Comment #59 from David Beswick --- Just to update, I've captured three different traces but none have been able to reproduce the problem on replay. I've also tried the following: * Looping a trace replay over 24 hours continuously -- no repro * Running with a -O0 Mesa build -- hang remains * Going directly to fallback in all cases during si_dma_copy (wild guess based on code comments) -- hang remains I don't think traces will be a fruitful method of debugging, unless someone can suggest something I'm doing wrong. I'm continuing to look at this. If anyone has a hypothesis and would like to send a patch then I could build and test with it. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151101/9cb72999/attachment.html>
[Bug 80419] XCOM: Enemy Unknown Causes lockup
https://bugs.freedesktop.org/show_bug.cgi?id=80419 --- Comment #60 from David Beswick --- Forgot to add that I also tried replaying traces via Steam, in case the Steam overlay somehow had something to do with it. It doesn't seem to help as I can't reproduce the problem via a trace that way either. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151101/38556b70/attachment.html>
[PATCH 09/19] drm: sun4i: Add DT bindings documentation
On Fri, Oct 30, 2015 at 12:37 PM, Thierry Reding wrote: > On Fri, Oct 30, 2015 at 11:40:03AM -0500, Rob Herring wrote: >> On Fri, Oct 30, 2015 at 9:20 AM, Maxime Ripard > [...] >> > +Optional properties: >> > + - allwinner,tv-encoder: phandle to the TV Encoder in our pipeline >> > + - allwinner,panel: phandle to the panel used in our RGB interface >> >> Use of-graph please. > > Why? Panels are a really simple resource and a simple phandle is fully > capable of describing the relationship. So we can have some consistency in bindings and common parsing code. It is simple when it is just a panel, but when it can be tv-encoder or other board level downstream bridge devices it doesn't stay so simple. Also, we already have a simple way to do panels which is as a child node. Let's not have a third way. Rob
[Bug 92765] Linux 4.1.12+, 4.2.5+ -> drm:radeon_pm_late_init [radeon]] *ERROR* + WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() +
] Oct 29 05:26:43 hosty kernel: [] chrdev_open+0xae/0x1f0 Oct 29 05:26:43 hosty kernel: [] do_dentry_open+0x227/0x330 Oct 29 05:26:43 hosty kernel: [] ? cdev_put+0x30/0x30 Oct 29 05:26:43 hosty kernel: [] vfs_open+0x56/0x60 Oct 29 05:26:43 hosty kernel: [] do_last.isra.11+0x344/0xf60 Oct 29 05:26:43 hosty kernel: [] ? path_init+0x17e/0x460 Oct 29 05:26:43 hosty kernel: [] path_openat+0x91/0x690 Oct 29 05:26:43 hosty kernel: [] do_filp_open+0x49/0xd0 Oct 29 05:26:43 hosty kernel: [] ? find_next_zero_bit+0x1a/0x30 Oct 29 05:26:43 hosty kernel: [] ? __alloc_fd+0xa7/0x130 Oct 29 05:26:43 hosty kernel: [] do_sys_open+0x14d/0x250 Oct 29 05:26:43 hosty kernel: [] SyS_open+0x1e/0x20 Oct 29 05:26:43 hosty kernel: [] system_call_fastpath+0x12/0x71 Oct 29 05:26:43 hosty kernel: ---[ end trace 1148860c62f9432d ]--- Oct 29 05:26:43 hosty kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for dpm state Oct 29 05:26:43 hosty kernel: [ cut here ] This is when I start the X server/ power off / reboot / resume from suspend : Oct 29 05:25:40 hosty kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for dpm state Oct 29 05:25:40 hosty kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for dpm state Oct 29 05:25:40 hosty kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for power profile Oct 29 05:25:40 hosty kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for power method Found something related: https://lkml.org/lkml/2015/10/26/780 Right now I'm running the -ck patch, but it behaves the same on the generic one Hw: DGPU 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] (rev ff) OS: ArchLinux It didn't happen on Linux 4.1.11 and 4.2.4. I think this is the commit that messed it up: == commit 4e4887f08f2ece9e7f1975af4c3dc797b1ad557b Author: Alex Deucher Date: Wed Sep 30 16:45:52 2015 -0400 drm/radeon: add pm sysfs files late commit 51a4726b04e880fdd9b4e0e58b13f70b0a68a7f5 upstream. They were added relatively early in the driver init process which meant that in some cases the driver was not finished initializing before external tools tried to use them which could result in a crash depending on the timing. Signed-off-by: Alex Deucher Signed-off-by: Greg Kroah-Hartman == -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151101/9601532e/attachment-0001.html>
[PATCH -next] drm/vc4: Add dependency on HAVE_DMA_ATTRS, and select DRM_GEM_CMA_HELPER
Avoid the following build errors, seen with m68k:allmodconfig and other
architectures which do not support HAVE_DMA_ATTRS.
ERROR: "drm_gem_cma_create" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_prime_mmap" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_prime_get_sg_table" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_vm_ops" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_mmap" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_prime_vunmap" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_prime_import_sg_table" [drivers/gpu/drm/vc4/vc4.ko]
undefined!
ERROR: "drm_gem_cma_free_object" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_prime_vmap" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_dumb_map_offset" [drivers/gpu/drm/vc4/vc4.ko] undefined!
ERROR: "drm_gem_cma_create" [drivers/gpu/drm/drm_kms_helper.ko] undefined!
ERROR: "drm_gem_cma_describe" [drivers/gpu/drm/drm_kms_helper.ko] undefined!
ERROR: "drm_gem_cma_free_object" [drivers/gpu/drm/drm_kms_helper.ko] undefined!
Cc: Eric Anholt
Fixes: c8b75bca92cb ("drm/vc4: Add KMS support for Raspberry Pi.")
Signed-off-by: Guenter Roeck
---
drivers/gpu/drm/vc4/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vc4/Kconfig b/drivers/gpu/drm/vc4/Kconfig
index e502802d74b6..2d7d115ddf3f 100644
--- a/drivers/gpu/drm/vc4/Kconfig
+++ b/drivers/gpu/drm/vc4/Kconfig
@@ -1,9 +1,10 @@
config DRM_VC4
tristate "Broadcom VC4 Graphics"
depends on ARCH_BCM2835 || COMPILE_TEST
- depends on DRM
+ depends on DRM && HAVE_DMA_ATTRS
select DRM_KMS_HELPER
select DRM_KMS_CMA_HELPER
+ select DRM_GEM_CMA_HELPER
help
Choose this option if you have a system that has a Broadcom
VC4 GPU, such as the Raspberry Pi or other BCM2708/BCM2835.
--
2.1.4
[PATCH] drm: Remove unused fbdev_list members
I noticed that intel_fbdev->our_mode is unused. Introduced by
79e539453b34 ("DRM: i915: add mode setting support").
Then I noticed that intel_fbdev->fbdev_list is unused as well.
Introduced by 386516744ba4 ("drm/fb: fix fbdev object model +
cleanup properly.") in i915, nouveau and radeon.
Subsequently cargo culted to amdgpu, ast, cirrus, qxl, udl,
virtio and mgag200.
Already removed from the latter with cc59487a05b1 ("drm/mgag200:
'fbdev_list' in 'struct mga_fbdev' is not used").
Remove it from the others.
Signed-off-by: Lukas Wunner
---
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c | 1 -
drivers/gpu/drm/ast/ast_drv.h | 1 -
drivers/gpu/drm/cirrus/cirrus_drv.h | 1 -
drivers/gpu/drm/i915/intel_drv.h| 2 --
drivers/gpu/drm/nouveau/nouveau_fbcon.h | 1 -
drivers/gpu/drm/qxl/qxl_fb.c| 1 -
drivers/gpu/drm/radeon/radeon_fb.c | 1 -
drivers/gpu/drm/udl/udl_fb.c| 1 -
drivers/gpu/drm/virtio/virtgpu_fb.c | 1 -
9 files changed, 10 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c
index 96290d9..ab781b4 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c
@@ -45,7 +45,6 @@
struct amdgpu_fbdev {
struct drm_fb_helper helper;
struct amdgpu_framebuffer rfb;
- struct list_head fbdev_list;
struct amdgpu_device *adev;
};
diff --git a/drivers/gpu/drm/ast/ast_drv.h b/drivers/gpu/drm/ast/ast_drv.h
index 86205a2..69e2a62 100644
--- a/drivers/gpu/drm/ast/ast_drv.h
+++ b/drivers/gpu/drm/ast/ast_drv.h
@@ -256,7 +256,6 @@ struct ast_framebuffer {
struct ast_fbdev {
struct drm_fb_helper helper;
struct ast_framebuffer afb;
- struct list_head fbdev_list;
void *sysram;
int size;
struct ttm_bo_kmap_obj mapping;
diff --git a/drivers/gpu/drm/cirrus/cirrus_drv.h
b/drivers/gpu/drm/cirrus/cirrus_drv.h
index 7050615..d772f7a 100644
--- a/drivers/gpu/drm/cirrus/cirrus_drv.h
+++ b/drivers/gpu/drm/cirrus/cirrus_drv.h
@@ -153,7 +153,6 @@ struct cirrus_device {
struct cirrus_fbdev {
struct drm_fb_helper helper;
struct cirrus_framebuffer gfb;
- struct list_head fbdev_list;
void *sysram;
int size;
int x1, y1, x2, y2; /* dirty rect */
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index 0598932..d792665 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -123,8 +123,6 @@ struct intel_framebuffer {
struct intel_fbdev {
struct drm_fb_helper helper;
struct intel_framebuffer *fb;
- struct list_head fbdev_list;
- struct drm_display_mode *our_mode;
int preferred_bpp;
};
diff --git a/drivers/gpu/drm/nouveau/nouveau_fbcon.h
b/drivers/gpu/drm/nouveau/nouveau_fbcon.h
index 1e2e9e2..ca77ad0 100644
--- a/drivers/gpu/drm/nouveau/nouveau_fbcon.h
+++ b/drivers/gpu/drm/nouveau/nouveau_fbcon.h
@@ -34,7 +34,6 @@
struct nouveau_fbdev {
struct drm_fb_helper helper;
struct nouveau_framebuffer nouveau_fb;
- struct list_head fbdev_list;
struct drm_device *dev;
unsigned int saved_flags;
struct nvif_object surf2d;
diff --git a/drivers/gpu/drm/qxl/qxl_fb.c b/drivers/gpu/drm/qxl/qxl_fb.c
index c4a5526..a97d167 100644
--- a/drivers/gpu/drm/qxl/qxl_fb.c
+++ b/drivers/gpu/drm/qxl/qxl_fb.c
@@ -40,7 +40,6 @@
struct qxl_fbdev {
struct drm_fb_helper helper;
struct qxl_framebuffer qfb;
- struct list_headfbdev_list;
struct qxl_device *qdev;
spinlock_t delayed_ops_lock;
diff --git a/drivers/gpu/drm/radeon/radeon_fb.c
b/drivers/gpu/drm/radeon/radeon_fb.c
index 26da2f4..adc44bb 100644
--- a/drivers/gpu/drm/radeon/radeon_fb.c
+++ b/drivers/gpu/drm/radeon/radeon_fb.c
@@ -44,7 +44,6 @@
struct radeon_fbdev {
struct drm_fb_helper helper;
struct radeon_framebuffer rfb;
- struct list_head fbdev_list;
struct radeon_device *rdev;
};
diff --git a/drivers/gpu/drm/udl/udl_fb.c b/drivers/gpu/drm/udl/udl_fb.c
index 62c7b1d..b9df46e 100644
--- a/drivers/gpu/drm/udl/udl_fb.c
+++ b/drivers/gpu/drm/udl/udl_fb.c
@@ -33,7 +33,6 @@ module_param(fb_defio, int, S_IWUSR | S_IRUSR | S_IWGRP |
S_IRGRP);
struct udl_fbdev {
struct drm_fb_helper helper;
struct udl_framebuffer ufb;
- struct list_head fbdev_list;
int fb_count;
};
diff --git a/drivers/gpu/drm/virtio/virtgpu_fb.c
b/drivers/gpu/drm/virtio/virtgpu_fb.c
index 6a81e08..2242a80 100644
--- a/drivers/gpu/drm/virtio/virtgpu_fb.c
+++ b/drivers/gpu/drm/virtio/virtgpu_fb.c
@@ -32,7 +32,6 @@
struct virtio_gpu_fbdev {
struct drm_fb_helper helper;
struct virtio_gpu_framebuffer vgfb;
- struct list_head fbdev_list;
struct virtio_gpu_device *vgdev;
struct delayed_workwork;
};
--
2.1.0
[Bug 106851] WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() + drm:radeon_pm_late_init [radeon]] *ERROR*
https://bugzilla.kernel.org/show_bug.cgi?id=106851 --- Comment #5 from lbl --- Update: it also happens on kernel 4.2.5 -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106271] Switch between AMD hybrid graphics (HD 8650G / HD 8970M) makes hardware reset.
https://bugzilla.kernel.org/show_bug.cgi?id=106271 --- Comment #10 from Aneroid --- Created attachment 191771 --> https://bugzilla.kernel.org/attachment.cgi?id=191771&action=edit Kernel crash log Very strange things happend. Kernel crash on every reboot now. It looks like kernel switch on pitcairin card, but can't boot from it. I remove any kernel options. -- You are receiving this mail because: You are watching the assignee of the bug.
