dri-devel October 2018

dri-devel@lists.freedesktop.org

277 participants
1898 discussions

[Bug 199475] New: AMDGPU Failed to blank
by bugzilla-daemon＠bugzilla.kernel.org 20 Jun '20

20 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=199475 Bug ID: 199475 Summary: AMDGPU Failed to blank Product: Drivers Version: 2.5 Kernel Version: 4.15.18 Hardware: Other OS: Linux Tree: Mainline Status: NEW Severity: low Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: andreassx0(a)gmail.… [View More]

1 9

[Bug 71891] New: 3.13 fails to boot with the radeon module
by bugzilla-daemon＠bugzilla.kernel.org 08 Jun '20

08 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=71891 Bug ID: 71891 Summary: 3.13 fails to boot with the radeon module Product: Drivers Version: 2.5 Kernel Version: 3.13.6-1-ARCH Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org … [View More]Reporter: sh.siddhartha(a)gmail.com Regression: No $ lspci -k | grep -A3 VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] Subsystem: Dell Device 0447 Kernel driver in use: fglrx_pci Kernel modules: radeon, fglrx Dell Inspiron N5010 (BIOS) Legacy catalyst works properly. Using the open source radeon driver either boots to tty login with above errors, or boots to a locked up black screen. drm syslog: [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver [drm] initializing kernel modesetting (RV730 0x1002:0x9480 0x1028:0x0447). [drm] register mmio base: 0xFBE20000 [drm] register mmio size: 65536 [drm] Detected VRAM RAM=1024M, BAR=256M [drm] RAM width 128bits DDR [drm] radeon: 1024M of VRAM memory ready [drm] radeon: 1024M of GTT memory ready. [drm] GART: num cpu pages 262144, num gpu pages 262144 [drm] Loading RV730 Microcode [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] radeon: irq initialized. [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!! [drm:rv770_startup] *ERROR* radeon: failed initializing UVD (-1). [drm] Enabling audio 0 support [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] radeon atom DIG backlight initialized [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA-1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] Connector 1: [drm] HDMI-A-1 [drm] HPD1 [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 2: [drm] LVDS-1 [drm] DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 0x7f74 [drm] Encoders: [drm] LCD1: INTERNAL_UNIPHY2 [drm] Internal thermal controller with fan control [drm] radeon: dpm initialized [drm] fb mappable at 0xC045E000 [drm] vram apper at 0xC0000000 [drm] size 4325376 [drm] fb depth is 24 [drm] pitch is 5632 fbcon: radeondrmfb (fb0) is primary device [drm:rv770_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [drm] Initialized radeon 2.36.0 20080528 for 0000:01:00.0 on minor 0 -- You are receiving this mail because: You are watching the assignee of the bug. [View Less]

1 51

[PATCH] drm/debugfs: accept trailing whitespace in "force" attribute
by Michael Tretter 18 May '20

18 May '20

Using plain echo to set the "force" connector attribute fails with -EINVAL, because echo appends a newline to the output. Strip trailing whitespace in the input before checking the value to accept "off\n" or "off ". Signed-off-by: Michael Tretter <m.tretter(a)pengutronix.de> --- drivers/gpu/drm/drm_debugfs.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/drm_debugfs.c b/drivers/gpu/drm/drm_debugfs.c index c1807d5754b2..10dd89d3f28e 100644 --- a/drivers/gpu/… [View More]

3 6

[Bug 201505] New: Resume from suspend does not power up the display
by bugzilla-daemon＠bugzilla.kernel.org 11 May '20

11 May '20

https://bugzilla.kernel.org/show_bug.cgi?id=201505 Bug ID: 201505 Summary: Resume from suspend does not power up the display Product: Drivers Version: 2.5 Kernel Version: 4.19 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org … [View More]

1 6

[PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()
by Peter Jones 07 Apr '20

07 Apr '20

This was sort of annoying me: random:~$ dmesg | tail -1 [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. random:~$ dmesg | grep -c "Reducing the compressed" 47 This patch makes it DRM_INFO_ONCE() just like the similar message farther down in that function is pr_info_once(). Signed-off-by: Peter Jones <pjones(a)redhat.com> --- drivers/gpu/drm/i915/… [View More]

3 2

[PATCH] RFC: drm/atomic-helpers: remove legacy_cursor_update hacks
by Daniel Vetter 06 Mar '20

06 Mar '20

The stuff never really worked, and leads to lots of fun because it out-of-order frees atomic states. Which upsets KASAN, among other things. For async updates we now have a more solid solution with the ->atomic_async_check and ->atomic_async_commit hooks. Support for that for msm and vc4 landed. nouveau and i915 have their own commit routines, doing something similar. For everyone else it's probably better to remove the use-after-free bug, and encourage folks to use the async support … [View More]

1 1

[Bug 196247] New: AMD FirePro W5130M (Dell 3510 notebook) - radeon driver - ring 0 stalled
by bugzilla-daemon＠bugzilla.kernel.org 28 Feb '20

28 Feb '20

https://bugzilla.kernel.org/show_bug.cgi?id=196247 Bug ID: 196247 Summary: AMD FirePro W5130M (Dell 3510 notebook) - radeon driver - ring 0 stalled Product: Drivers Version: 2.5 Kernel Version: 4.10. Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-… [View More]

1 10

[Bug 58981] New: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS
by bugzilla-daemon＠bugzilla.kernel.org 28 Jan '20

28 Jan '20

https://bugzilla.kernel.org/show_bug.cgi?id=58981 Summary: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.35,3.2.45,3.10-rc2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-… [View More]

1 6

[RFC PATCH v1 0/5] Add pardata bus + tinydrm driver
by Sam Ravnborg 20 Jan '20

20 Jan '20

This is an RFC - to get some responses on the overall design. The code builds but has not yet been tested on any HW. Before investing more time into this I would like some feedback if this is the right way forward or a different design should be pursued. The problem to solve is that I have a propriatary ARM based board with a display that is connected using a parallel bus. The display is capable of showing graphics so it is more advanced than what is found in auxdisplay/ I know there are … [View More]others using a display connected usign a parallel data bus, so this is not a unique problem for my board alone. But I do not expect many users as any modern design likely uses SPI or similar. The old (proprietary) approach was to implement a char driver and then let some 3rd party lib use the char driver to write to the display. The goal is to move to a more modern world where I expect to have a simple Qt based program running that can be used for a few simple things. (I do not expect any high performance and do not need it). Implementation: A pardata bus is implemented. It uses a platform_driver to hook into the DT. When probed the pardatabus driver creates pardata devices for all child nodes in the tree. Within tinydrm the pardata support is used to implement a driver for the display I have (Winstar wg160160). A library module is used to implement the more basic things allowing us to have a more simple driver, and thus making it simpler to add new drivers. The implmentation uses array support in gpiolib to try to have some performance on screen updates. TODO: - Test on HW - Add locking so there can be more than one user on the bus - Improve pardata.rst documentation - Add support for a sparkfun parallel data display (To verify that the library is generic) - I may add a class if I see the need - Likewise I may add sysfs attributes if there is a need for it Any comments appreciated! Sam Sam Ravnborg (5): dt-bindings: add parallel data bus (pardata) pardata: new bus for parallel data access tinydrm: add support for parallel data displays dt-bindings: add winstar,wg160160 display bindings tinydrm: add winstar wg160160 driver .../bindings/display/winstar,wg160160.txt | 53 +++ .../bindings/pardata/parallel-data-bus.txt | 60 +++ Documentation/driver-api/index.rst | 1 + Documentation/driver-api/pardata.rst | 60 +++ MAINTAINERS | 14 + drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/gpu/drm/tinydrm/Kconfig | 13 + drivers/gpu/drm/tinydrm/Makefile | 2 + drivers/gpu/drm/tinydrm/pardata-dbi.c | 417 +++++++++++++++++++++ drivers/gpu/drm/tinydrm/wg160160.c | 298 +++++++++++++++ drivers/pardata/Kconfig | 17 + drivers/pardata/Makefile | 5 + drivers/pardata/pardata.c | 282 ++++++++++++++ include/drm/tinydrm/pardata-dbi.h | 257 +++++++++++++ include/linux/pardata.h | 138 +++++++ 16 files changed, 1620 insertions(+) [View Less]

5 18

[Bug 194731] New: drm general protection fault in drm_atomic_init
by bugzilla-daemon＠bugzilla.kernel.org 09 Jan '20

09 Jan '20

https://bugzilla.kernel.org/show_bug.cgi?id=194731 Bug ID: 194731 Summary: drm general protection fault in drm_atomic_init Product: Drivers Version: 2.5 Kernel Version: 4.10.0 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org … [View More]Reporter: janpieter.sollie(a)dommel.be Regression: No I modified the drm_atomic.c a bit to be more verbose. the drm_init calls a general protection fault when allocating my second GPU(does it work this way?) of the amdgpu module. afterwards, the system is unable to allocate more kernel memory. init does not even manage to reboot, I can not do sudo without segfault dmesg: [ 77.946291] [drm] Cannot find any crtc or sizes - going 1024x768 [ 77.946575] [drm] fb mappable at 0xC0CCB000 [ 77.946576] [drm] vram apper at 0xC0000000 [ 77.946577] [drm] size 786432 [ 77.946578] [drm] fb depth is 24 [ 77.946578] [drm] pitch is 1024 [ 77.950389] kcalloc called [ 77.950390] kcalloc2 called [ 77.950433] kcalloc called [ 77.950444] general protection fault: 0000 [#1] SMP [ 77.950445] Modules linked in: amdkfd amdgpu(O+) amdttm(O) amdkcl(O) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_nat iptable_nat nf_nat_ipv4 nf_nat l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppoe pppox ppp_generic slhc deflate cmac af_key w83627ehf hwmon_vid k10temp fam15h_power i2c_piix4 pcspkr [ 77.950462] CPU: 16 PID: 5094 Comm: kworker/16:2 Tainted: G O 4.10.0-rc8 #12 [ 77.950463] Hardware name: Supermicro H8DG6/H8DGi/H8DG6/H8DGi, BIOS 2.0a 01/09/2012 [ 77.950470] Workqueue: events work_for_cpu_fn [ 77.950471] task: ffff88183c027000 task.stack: ffffc90020cfc000 [ 77.950476] RIP: 0010:__kmalloc+0x6f/0x100 [ 77.950477] RSP: 0018:ffffc90020cff6b0 EFLAGS: 00010286 [ 77.950478] RAX: 0000000000000000 RBX: ffff8818362628ff RCX: 0000000000000897 [ 77.950479] RDX: 0000000000000896 RSI: 0000000000000000 RDI: 0000000000019b70 [ 77.950479] RBP: ffffc90020cff6d0 R08: ffff88183fc19b70 R09: ffffffff81417df1 [ 77.950480] R10: 0000000000000300 R11: 0000000000000000 R12: ff88183626296000 [ 77.950481] R13: ffff88083f803a00 R14: 00000000014080c0 R15: ffff88183602b238 [ 77.950483] FS: 0000000000000000(0000) GS:ffff88183fc00000(0000) knlGS:0000000000000000 [ 77.950484] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 77.950485] CR2: 00005590d5ce93d8 CR3: 0000000001c11000 CR4: 00000000000406e0 [ 77.950485] Call Trace: [ 77.950492] drm_atomic_state_init+0x81/0xf0 [ 77.950494] drm_atomic_state_alloc+0x53/0x80 [ 77.950497] drm_fb_helper_pan_display+0xf4/0x2a0 [ 77.950501] fb_pan_display+0xd6/0x170 [ 77.950502] bit_update_start+0x24/0x60 [ 77.950504] fbcon_switch+0x3e2/0x670 [ 77.950507] redraw_screen+0x15d/0x220 [ 77.950510] ? tty_do_resize+0x4d/0xa0 [ 77.950512] vc_do_resize+0x4c3/0x4f0 [ 77.950513] vc_resize+0x1a/0x20 [ 77.950515] fbcon_init+0x40b/0x660 [ 77.950516] visual_init+0xce/0x130 [ 77.950517] do_bind_con_driver+0x1c1/0x3a0 [ 77.950519] do_take_over_console+0x113/0x180 [ 77.950520] do_fbcon_takeover+0x51/0xb0 [ 77.950522] fbcon_event_notify+0x75a/0x880 [ 77.950525] notifier_call_chain+0x44/0x70 [ 77.950526] __blocking_notifier_call_chain+0x4e/0x80 [ 77.950528] blocking_notifier_call_chain+0x11/0x20 [ 77.950529] fb_notifier_call_chain+0x16/0x20 [ 77.950531] register_framebuffer+0x200/0x340 [ 77.950533] drm_fb_helper_initial_config+0x201/0x390 piece of code that prints the "kcalloc(2) called": drm_atomic_state_init(struct drm_device *dev, struct drm_atomic_state *state) { kref_init(&(state->ref)); /* TODO legacy paths should maybe do a better job about * setting this appropriately? */ state->allow_modeset = true; state->crtcs = kcalloc(dev->mode_config.num_crtc, sizeof(struct __drm_crtcs_state), GFP_KERNEL); printk("kcalloc called \n"); if (!(state->crtcs)) goto fail; state->planes = kcalloc(dev->mode_config.num_total_plane, sizeof(struct __drm_planes_state), GFP_KERNEL); printk("kcalloc2 called \n"); if (!(state->planes)) goto fail; state->dev = dev; DRM_DEBUG_ATOMIC("Allocated atomic state %p\n", state); return 0; fail: printk("fail called \n"); drm_atomic_state_default_release(state); return -ENOMEM; } EXPORT_SYMBOL(drm_atomic_state_init); -- You are receiving this mail because: You are watching the assignee of the bug. [View Less]

1 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2018