dri-devel January 2019

dri-devel@lists.freedesktop.org

279 participants
2022 discussions

[Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
by bugzilla-daemon＠freedesktop.org 08 Jan '19

08 Jan '19

https://bugs.freedesktop.org/show_bug.cgi?id=108585 Bug ID: 108585 Summary: *ERROR* hw_init of IP block <gfx_v8_0> failed -22 Product: DRI Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: dan(a)danny.cz CC: bcrocker(a)redhat.com Created attachment 142253 --> https://bugs.freedesktop.org/attachment.cgi?id=142253&action=edit full dmesg output amdgpu driver fails to initialize Radeon WX4100 PRO on my Talos Power9 system with kernel 4.19 (GA). There is no such problem with 4.19-rc8 (and earlier). ... [ 2.421393] [drm] amdgpu kernel modesetting enabled. [ 2.421512] amdgpu 0000:01:00.0: enabling device (0540 -> 0542) [ 2.421732] [drm] initializing kernel modesetting (POLARIS11 0x1002:0x67E3 0x1002:0x0B0D 0x00). [ 2.421776] [drm] register mmio base: 0x00000000 [ 2.421781] [drm] register mmio size: 262144 [ 2.421787] [drm] PCI I/O BAR is not found. [ 2.421798] [drm] add ip block number 0 <vi_common> [ 2.421801] [drm] add ip block number 1 <gmc_v8_0> [ 2.421805] [drm] add ip block number 2 <tonga_ih> [ 2.421808] [drm] add ip block number 3 <powerplay> [ 2.421811] [drm] add ip block number 4 <dce_v11_0> [ 2.421814] [drm] add ip block number 5 <gfx_v8_0> [ 2.421818] [drm] add ip block number 6 <sdma_v3_0> [ 2.421821] [drm] add ip block number 7 <uvd_v6_0> [ 2.421824] [drm] add ip block number 8 <vce_v3_0> [ 2.421837] [drm] UVD is enabled in VM mode [ 2.421840] [drm] UVD ENC is enabled in VM mode [ 2.421845] [drm] VCE enabled in VM mode [ 2.609475] md/raid1:md127: active with 2 out of 2 mirrors [ 2.625800] md127: detected capacity change from 0 to 481708474368 [ 2.627770] md/raid1:md126: active with 2 out of 2 mirrors [ 2.643643] md126: detected capacity change from 0 to 1072693248 [ 2.769520] usb 1-4: new high-speed USB device number 4 using xhci_hcd [ 2.769550] ATOM BIOS: 113-D0150600-103 [ 2.769747] [drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 2.769846] pci 0000:01 : [PE# 00] pseudo-bypass sizes: tracker 32800 bitmap 8192 TCEs 65536 [ 2.769851] pci 0000:01 : [PE# 00] TCE tables configured for pseudo-bypass [ 2.769903] amdgpu 0000:01:00.0: BAR 2: releasing [mem 0x6000010000000-0x60000101fffff 64bit pref] [ 2.769907] amdgpu 0000:01:00.0: BAR 0: releasing [mem 0x6000000000000-0x600000fffffff 64bit pref] [ 2.769939] pci 0000:00:00.0: BAR 15: releasing [mem 0x6000000000000-0x6003fbff0ffff 64bit pref] [ 2.769956] pci 0000:00:00.0: BAR 15: assigned [mem 0x6000000000000-0x600017fffffff 64bit pref] [ 2.769961] amdgpu 0000:01:00.0: BAR 0: assigned [mem 0x6000000000000-0x60000ffffffff 64bit pref] [ 2.769972] amdgpu 0000:01:00.0: BAR 2: assigned [mem 0x6000100000000-0x60001001fffff 64bit pref] [ 2.770004] pci 0000:00:00.0: PCI bridge to [bus 01] [ 2.770009] pci 0000:00:00.0: bridge window [mem 0x600c000000000-0x600c07fefffff] [ 2.770015] pci 0000:00:00.0: bridge window [mem 0x6000000000000-0x6003fbff0ffff 64bit pref] [ 2.770066] amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used) [ 2.770069] amdgpu 0000:01:00.0: GART: 256M 0x0000000000000000 - 0x000000000FFFFFFF [ 2.770075] [drm] Detected VRAM RAM=4096M, BAR=4096M [ 2.770077] [drm] RAM width 128bits GDDR5 [ 2.770162] [TTM] Zone kernel: Available graphics memory: 32717248 kiB [ 2.770165] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 2.770166] [TTM] Initializing pool allocator [ 2.771771] [drm] amdgpu: 4096M of VRAM memory ready [ 2.771774] [drm] amdgpu: 4096M of GTT memory ready. [ 2.771790] [drm] GART: num cpu pages 4096, num gpu pages 65536 [ 2.771839] [drm] PCIE GART of 256M enabled (table at 0x000000F4008D0000). [ 2.771911] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.771913] [drm] Driver supports precise vblank timestamp query. [ 2.772311] [drm] AMDGPU Display Connectors [ 2.772313] [drm] Connector 0: [ 2.772315] [drm] DP-1 [ 2.772316] [drm] HPD5 [ 2.772318] [drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b [ 2.772320] [drm] Encoders: [ 2.772322] [drm] DFP1: INTERNAL_UNIPHY1 [ 2.772323] [drm] Connector 1: [ 2.772325] [drm] DP-2 [ 2.772326] [drm] HPD4 [ 2.772328] [drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f [ 2.772330] [drm] Encoders: [ 2.772332] [drm] DFP2: INTERNAL_UNIPHY1 [ 2.772333] [drm] Connector 2: [ 2.772335] [drm] DP-3 [ 2.772336] [drm] HPD3 [ 2.772338] [drm] DDC: 0x4870 0x4870 0x4871 0x4871 0x4872 0x4872 0x4873 0x4873 [ 2.772340] [drm] Encoders: [ 2.772341] [drm] DFP3: INTERNAL_UNIPHY [ 2.772343] [drm] Connector 3: [ 2.772345] [drm] DP-4 [ 2.772346] [drm] HPD2 [ 2.772348] [drm] DDC: 0x4874 0x4874 0x4875 0x4875 0x4876 0x4876 0x4877 0x4877 [ 2.772350] [drm] Encoders: [ 2.772351] [drm] DFP4: INTERNAL_UNIPHY [ 2.772477] [drm] Chained IB support enabled! [ 2.773607] [drm] Found UVD firmware Version: 1.130 Family ID: 16 [ 2.775588] [drm] Found VCE firmware Version: 53.26 Binary ID: 3 [ 2.780989] amdgpu: [powerplay] dpm has been enabled [ 2.990665] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD) [ 2.990695] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 [ 2.990698] amdgpu 0000:01:00.0: amdgpu_device_ip_init failed [ 2.990701] amdgpu 0000:01:00.0: Fatal error during GPU init [ 2.990703] [drm] amdgpu: finishing device. [ 3.833155] ------------[ cut here ]------------ [ 3.833157] Memory manager not clean during takedown. [ 3.833188] WARNING: CPU: 0 PID: 338 at drivers/gpu/drm/drm_mm.c:950 drm_mm_takedown+0x3c/0x60 [drm] [ 3.833191] Modules linked in: raid1 amdgpu(+) mfd_core chash i2c_algo_bit gpu_sched drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm crc32c_vpmsum tg3 aacraid drm_panel_orientation_quirks i2c_core [ 3.833204] CPU: 0 PID: 338 Comm: kworker/0:2 Not tainted 4.19.0-1.fc30.op.1.ppc64le #1 [ 3.833210] Workqueue: events work_for_cpu_fn [ 3.833213] NIP: c00800000cdfea14 LR: c00800000cdfea10 CTR: c0000000006ff6e0 [ 3.833215] REGS: c0000007f85d74d0 TRAP: 0700 Not tainted (4.19.0-1.fc30.op.1.ppc64le) [ 3.833217] MSR: 9000000002029033 <SF,HV,VEC,EE,ME,IR,DR,RI,LE> CR: 44002222 XER: 20040000 [ 3.833224] CFAR: c000000000119b04 IRQMASK: 0 GPR00: c00800000cdfea10 c0000007f85d7750 c00800000ce6f200 0000000000000029 GPR04: 0000000000000001 0000000000000399 ffffffffffffffff 0000000000000000 GPR08: 0000000000000007 0000000000000007 0000000000000001 0769077207750764 GPR12: 0000000000002000 c000000001820000 c000000000148e68 c0002006d7c997c0 GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR20: 0000000000000000 0000000000000000 fffffffffffffef7 c0000007e02b3060 GPR24: c0000007e02b3080 c0000007e02b3088 c0000007e02b3078 0000000000000000 GPR28: 0000000000000000 c0000007e02b2980 c0000007e02b29a0 c0000007f9f38300 [ 3.833258] NIP [c00800000cdfea14] drm_mm_takedown+0x3c/0x60 [drm] [ 3.833265] LR [c00800000cdfea10] drm_mm_takedown+0x38/0x60 [drm] [ 3.833267] Call Trace: [ 3.833275] [c0000007f85d7750] [c00800000cdfea10] drm_mm_takedown+0x38/0x60 [drm] (unreliable) [ 3.833307] [c0000007f85d77b0] [c00800000dba9058] amdgpu_vram_mgr_fini+0x40/0xb0 [amdgpu] [ 3.833313] [c0000007f85d77e0] [c00800000cf15904] ttm_bo_clean_mm+0x10c/0x1a0 [ttm] [ 3.833341] [c0000007f85d7860] [c00800000db7a35c] amdgpu_ttm_fini+0x94/0x180 [amdgpu] [ 3.833370] [c0000007f85d78e0] [c00800000db7d1f8] amdgpu_bo_fini+0x20/0x40 [amdgpu] [ 3.833404] [c0000007f85d7900] [c00800000dc0ce50] gmc_v8_0_sw_fini+0x58/0x98 [amdgpu] [ 3.833440] [c0000007f85d7930] [c00800000dd55718] amdgpu_device_fini+0x3c4/0x628 [amdgpu] [ 3.833469] [c0000007f85d79e0] [c00800000db67b04] amdgpu_driver_unload_kms+0x6c/0x100 [amdgpu] [ 3.833496] [c0000007f85d7a10] [c00800000db67d84] amdgpu_driver_load_kms+0x1ec/0x280 [amdgpu] [ 3.833504] [c0000007f85d7a90] [c00800000cdfa830] drm_dev_register+0x1a8/0x270 [drm] [ 3.833533] [c0000007f85d7b30] [c00800000db60708] amdgpu_pci_probe+0x160/0x290 [amdgpu] [ 3.833537] [c0000007f85d7bc0] [c0000000006d7ddc] local_pci_probe+0x6c/0x140 [ 3.833541] [c0000007f85d7c50] [c00000000013ad48] work_for_cpu_fn+0x38/0x60 [ 3.833543] [c0000007f85d7c80] [c00000000013f880] process_one_work+0x250/0x500 [ 3.833546] [c0000007f85d7d20] [c00000000013fda0] worker_thread+0x270/0x5b0 [ 3.833550] [c0000007f85d7dc0] [c00000000014900c] kthread+0x1ac/0x1c0 [ 3.833553] [c0000007f85d7e30] [c00000000000bdd4] ret_from_kernel_thread+0x5c/0x68 [ 3.833556] Instruction dump: [ 3.833558] 60000000 e9230038 38630038 7fa34800 4d9e0020 7c0802a6 f8010010 f821ffa1 [ 3.833563] 3c620000 e8638540 4803297d e8410018 <0fe00000> 38210060 e8010010 7c0803a6 [ 3.833569] ---[ end trace 6009d10b516b7f29 ]--- [ 3.833576] [TTM] Finalizing pool allocator [ 3.833612] [TTM] Zone kernel: Used memory at exit: 6 kiB [ 3.833617] [TTM] Zone dma32: Used memory at exit: 6 kiB [ 3.833620] [drm] amdgpu: ttm finalized [ 3.833902] amdgpu: probe of 0000:01:00.0 failed with error -22 ... Both 4.19-rc8 and 4.19 kernels use the same firmware from linux-firmware-20180815-86.gitf1b95fe5.fc28 package. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 202061] New: Nouveau Trace
by bugzilla-daemon＠bugzilla.kernel.org 08 Jan '19

08 Jan '19

https://bugzilla.kernel.org/show_bug.cgi?id=202061 Bug ID: 202061 Summary: Nouveau Trace Product: Drivers Version: 2.5 Kernel Version: 4.20 Hardware: Other OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: scafroglia57(a)gmail.com Regression: No ------------[ cut here ]------------ [ 2.286601] nouveau 0000:01:00.0: timeout [ 2.286645] WARNING: CPU: 3 PID: 259 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x1a4/0x250 [nouveau] [ 2.286645] Modules linked in: nouveau(+) i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops mxm_wmi r8169 drm nvme_core ahci i2c_i801 libahci video wmi [ 2.286651] CPU: 3 PID: 259 Comm: systemd-udevd Not tainted 4.20.0-xanmod1 #1.181225 [ 2.286652] Hardware name: Micro-Star International Co., Ltd. MS-7B48/Z370-A PRO (MS-7B48), BIOS 2.70 08/03/2018 [ 2.286679] RIP: 0010:acr_ls_sec2_post_run+0x1a4/0x250 [nouveau] [ 2.286679] Code: d0 e9 c0 fe ff ff 49 8b 7f 10 48 8b 5f 50 48 85 db 74 1e e8 7e d3 38 d0 48 89 da 48 c7 c7 b3 e4 43 c0 48 89 c6 e8 36 63 da cf <0f> 0b e9 0a ff ff ff 48 8b 5f 10 eb dc 8b 45 20 48 c7 c6 68 56 43 [ 2.286680] RSP: 0018:ffffa36401eb3650 EFLAGS: 00010282 [ 2.286681] RAX: 0000000000000000 RBX: ffff8fb79c2295c0 RCX: ffffffff91465a68 [ 2.286681] RDX: 0000000000000001 RSI: 0000000000000096 RDI: 0000000000000246 [ 2.286682] RBP: ffff8fb79c525b80 R08: 0000000000000001 R09: 00000000000002bf [ 2.286682] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000040 [ 2.286683] R13: ffff8fb78f760b40 R14: 0000000088541920 R15: ffff8fb78e997c00 [ 2.286684] FS: 00007f6a1dde3680(0000) GS:ffff8fb79eac0000(0000) knlGS:0000000000000000 [ 2.286684] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.286685] CR2: 00007f6a1dc62000 CR3: 000000044eb0e005 CR4: 00000000003606e0 [ 2.286686] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 2.286686] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 2.286687] Call Trace: [ 2.286714] acr_r352_bootstrap+0x19b/0x290 [nouveau] [ 2.286739] acr_r352_reset+0x35/0x220 [nouveau] [ 2.286767] gf100_gr_init_ctxctl+0x6d/0xa10 [nouveau] [ 2.286789] nvkm_engine_init+0xaa/0x1e0 [nouveau] [ 2.286811] nvkm_subdev_init+0xb2/0x200 [nouveau] [ 2.286831] nvkm_engine_ref.part.0+0x43/0x60 [nouveau] [ 2.286852] nvkm_ioctl_new+0x125/0x200 [nouveau] [ 2.286879] ? nvkm_fifo_chan_child_del+0x90/0x90 [nouveau] [ 2.286905] ? gf100_gr_dtor+0xd0/0xd0 [nouveau] [ 2.286926] nvkm_ioctl+0xd8/0x170 [nouveau] [ 2.286947] nvif_object_init+0xbf/0x110 [nouveau] [ 2.286974] nvc0_fbcon_accel_init+0x59/0x910 [nouveau] [ 2.286999] nouveau_fbcon_create+0x545/0x550 [nouveau] [ 2.287005] __drm_fb_helper_initial_config_and_unlock+0x1cd/0x410 [drm_kms_helper] [ 2.287029] nouveau_fbcon_init+0x15a/0x1c0 [nouveau] [ 2.287054] nouveau_drm_device_init+0x43b/0x7f0 [nouveau] [ 2.287057] ? pci_bus_read_config_word+0x49/0x70 [ 2.287081] nouveau_drm_probe+0x274/0x2d0 [nouveau] [ 2.287083] local_pci_probe+0x41/0x90 [ 2.287084] pci_device_probe+0x188/0x1a0 [ 2.287087] really_probe+0xf8/0x3b0 [ 2.287088] driver_probe_device+0xb3/0xf0 [ 2.287089] __driver_attach+0xdd/0x110 [ 2.287091] ? driver_probe_device+0xf0/0xf0 [ 2.287092] bus_for_each_dev+0x76/0xc0 [ 2.287093] bus_add_driver+0x152/0x230 [ 2.287094] ? 0xffffffffc04a0000 [ 2.287095] driver_register+0x6b/0xb0 [ 2.287096] ? 0xffffffffc04a0000 [ 2.287098] do_one_initcall+0x46/0x1f5 [ 2.287099] ? free_pcp_prepare+0x4a/0xd0 [ 2.287101] ? kmem_cache_alloc_trace+0x2f/0x1d0 [ 2.287103] do_init_module+0x5a/0x210 [ 2.287104] load_module+0x2116/0x23a0 [ 2.287107] ? ima_post_read_file+0xf4/0x100 [ 2.287109] ? __do_sys_finit_module+0xa8/0x110 [ 2.287110] __do_sys_finit_module+0xa8/0x110 [ 2.287112] do_syscall_64+0x65/0x190 [ 2.287114] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2.287115] RIP: 0033:0x7f6a1d8ed839 [ 2.287116] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1f f6 2c 00 f7 d8 64 89 01 48 [ 2.287117] RSP: 002b:00007ffd8224b0e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 2.287117] RAX: ffffffffffffffda RBX: 000055f07e842a70 RCX: 00007f6a1d8ed839 [ 2.287118] RDX: 0000000000000000 RSI: 00007f6a1d5cc145 RDI: 0000000000000013 [ 2.287118] RBP: 00007f6a1d5cc145 R08: 0000000000000000 R09: 00007ffd8224b200 [ 2.287119] R10: 0000000000000013 R11: 0000000000000246 R12: 0000000000000000 [ 2.287119] R13: 000055f07e7f8470 R14: 0000000000020000 R15: 000055f07e842a70 [ 2.287120] ---[ end trace dabc1c2442916b9b ]--- -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[PATCH] drm/virtio: Remove incorrect kfree()
by Ezequiel Garcia 08 Jan '19

08 Jan '19

The virtio_gpu_output is a member of struct virtio_gpu_device and is not a dynamically-allocated chunk, so it's wrong to kfree() it. Removing it fixes a memory corruption BUG() that can be triggered when the virtio-gpu driver is removed. Signed-off-by: Ezequiel Garcia <ezequiel(a)collabora.com> --- drivers/gpu/drm/virtio/virtgpu_display.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c b/drivers/gpu/drm/virtio/virtgpu_display.c index e1c223e18d86..d539bc28dc97 100644 --- a/drivers/gpu/drm/virtio/virtgpu_display.c +++ b/drivers/gpu/drm/virtio/virtgpu_display.c @@ -243,12 +243,8 @@ static enum drm_connector_status virtio_gpu_conn_detect( static void virtio_gpu_conn_destroy(struct drm_connector *connector) { - struct virtio_gpu_output *virtio_gpu_output = - drm_connector_to_virtio_gpu_output(connector); - drm_connector_unregister(connector); drm_connector_cleanup(connector); - kfree(virtio_gpu_output); } static const struct drm_connector_funcs virtio_gpu_connector_funcs = { -- 2.20.0

2 2

[Bug 201867] New: Nouveau + discrete GPU (GP104M = GTX 1070 M) Driver Crashes, System freezes, dual screen not working
by bugzilla-daemon＠bugzilla.kernel.org 08 Jan '19

08 Jan '19

https://bugzilla.kernel.org/show_bug.cgi?id=201867 Bug ID: 201867 Summary: Nouveau + discrete GPU (GP104M = GTX 1070 M) Driver Crashes, System freezes, dual screen not working Product: Drivers Version: 2.5 Kernel Version: 4.19.4-arch1-1-ARCH #1 SMP PREEMPT 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 Reporter: david.kremer.dk(a)gmail.com Regression: No Created attachment 279831 --> https://bugzilla.kernel.org/attachment.cgi?id=279831&action=edit Driver Traceback The problem is proteiform. It is actually well described in https://bugzilla.kernel.org/show_bug.cgi?id=156341 so this could be a duplicate, however, since the driver supposed to actually drive the nvidia GPU is nouveau, I feel obliged to fill a new bug report to address the issue. So basically, there is two issues: 1. when loading the nouveau driver in a tty, you can't launch Xorg afterward, the xinit program waits for a server to be available but that never come. 2. When loading the nouveau driver after the X session has started, the fan finally switches off, but there is first a traceback in dmesg and everything that is reported in bug_id=156341 happens: subsequent calls to lspci/lshw/... are freezing the system definetely without possibility to recover except by doing a hard reboot. So there's definitely something messy about this familiy of Nvidia GPU integrated as a discrete GC on this new laptop generation. Can't give much more info See attachment for the traceback. lspci output: 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) 01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] (rev ff) CPU=Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz -- You are receiving this mail because: You are watching the assignee of the bug.

1 3

[PATCH] drm/todo: Better defio support in the generic fbdev emulation
by Daniel Vetter 08 Jan '19

08 Jan '19

The current one essentially means you need CMA or a vmalloc backed object, which makes fbdev emulation a special case. Since implementing this will be quite a bit of work, capture the idea in a TODO. Cc: Noralf Trønnes <noralf(a)tronnes.org> Signed-off-by: Daniel Vetter <daniel.vetter(a)intel.com> --- Documentation/gpu/todo.rst | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst index 41da7b06195c..0a85dad876ae 100644 --- a/Documentation/gpu/todo.rst +++ b/Documentation/gpu/todo.rst @@ -209,6 +209,36 @@ Would be great to refactor this all into a set of small common helpers. Contact: Daniel Vetter +Generic fbdev defio support +--------------------------- + +The defio support code in the fbdev core has some very specific requirements, +which means drivers need to have a special framebuffer for fbdev. Which prevents +us from using the generic fbdev emulation code everywhere. The main issue is +that it uses some fields in struct page itself, which breaks shmem gem objects +(and other things). + +Possible solution would be to write our own defio mmap code in the drm fbdev +emulation. It would need to fully wrap the existing mmap ops, forwarding +everything after it has done the write-protect/mkwrite trickery: + +- In the drm_fbdev_fb_mmap helper, if we need defio, change the + default page prots to write-protected with something like this:: + + vma->vm_page_prot = pgprot_wrprotect(vma->vm_page_prot); + +- Set the mkwrite and fsync callbacks with similar implementions to the core + fbdev defio stuff. These should all work on plain ptes, they don't actually + require a struct page. uff. These should all work on plain ptes, they don't + actually require a struct page. + +- Track the dirty pages in a separate structure (bitfield with one bit per page + should work) to avoid clobbering struct page. + +Might be good to also have some igt testcases for this. + +Contact: Daniel Vetter, Noralf Tronnes + Put a reservation_object into drm_gem_object -------------------------------------------- -- 2.20.0.rc1

3 2

[GIT PULL] tilcdc changes for 4.22
by Jyri Sarha 08 Jan '19

08 Jan '19

Hi Dave, Please pull this drm/tilcdc patch for Linux v4.22. Best regards and thanks, Jyri The following changes since commit 8fe28cb58bcb235034b64cbbb7550a8a43fd88be: Linux 4.20 (2018-12-23 15:55:59 -0800) are available in the Git repository at: https://github.com/jsarha/linux tags/tilcdc-4.22 for you to fetch changes up to 432973fd3a20102840d5f7e61af9f1a03c217a4c: drm/tilcdc: Register cpufreq notifier after we have initialized crtc (2019-01-04 18:01:58 +0200) ---------------------------------------------------------------- tilcdc pull request for Linux v4.22 ---------------------------------------------------------------- Jyri Sarha (1): drm/tilcdc: Register cpufreq notifier after we have initialized crtc drivers/gpu/drm/tilcdc/tilcdc_drv.c | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

1 0

[v2 00/14] Add HDR Metadata Parsing and handling in DRM layer
by Uma Shankar 08 Jan '19

08 Jan '19

This patch series enables HDR support in drm. It basically defines HDR metadata structures, property to pass content (after blending) metadata from user space compositors to driver. Dynamic Range and Mastering infoframe creation and sending. ToDo: 1. We need to get the color framework in place for all planes which support HDR content in hardware. This is already in progres and patches are out for review in mailing list. 2. UserSpace/Compositors: Blending policies and metadata blob creation and passing to driver. Work is already in progress by Intel's middleware teams on wayland and we should be getting the initial version pretty soon for review. Please review and share your feedbacks/suggestions. Note: The intention for these patches is to get a design feedback on the uapi changes, generic property design and infoframe handling. This cannot get merged as of now without the userspace support in place. A POC has already been developed by Ville based on wayland. Please refer below link to see the component interactions and usage: https://lists.freedesktop.org/archives/wayland-devel/2017-December/036403.h… v2: Updated Ville's POC changes to the patch series.Incorporated cleanups and fixes from Ville. Rebase on latest drm-tip. Note: It took a while to float this version as there was no userspace consumer for it and dependency on full userspace stack. However, things are falling in place now. Media driver and VAAPI changes for HDR are already out, with compositors changes also expected to land soon. Uma Shankar (10): drm: Add HDR source metadata property drm: Add CEA extended tag blocks and HDR bitfield macros drm: Parse HDR metadata info from EDID drm: Parse Colorimetry data block from EDID drm/i915: Attach HDR metadata property to connector drm: Add HDR capability field to plane structure drm: Implement HDR source metadata set and get property handling drm: Enable HDR infoframe support drm/i915: Write HDR infoframe and send to panel drm/i915:Enabled Modeset when HDR Infoframe changes Ville Syrjälä (4): drm/i915: [DO NOT MERGE] hack for glk board outputs drm/i915: Add HLG EOTF drm/i915: Enable infoframes on GLK+ for HDR drivers/video: Constantify function argument for HDMI infoframe log drivers/gpu/drm/drm_atomic.c | 2 + drivers/gpu/drm/drm_atomic_uapi.c | 13 ++++ drivers/gpu/drm/drm_connector.c | 6 ++ drivers/gpu/drm/drm_edid.c | 143 ++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/i915_reg.h | 4 + drivers/gpu/drm/i915/intel_atomic.c | 15 +++- drivers/gpu/drm/i915/intel_bios.c | 7 ++ drivers/gpu/drm/i915/intel_hdmi.c | 43 ++++++++++- drivers/video/hdmi.c | 129 ++++++++++++++++++++++++++++++++ include/drm/drm_connector.h | 12 +++ include/drm/drm_edid.h | 4 + include/drm/drm_mode_config.h | 6 ++ include/drm/drm_plane.h | 3 + include/linux/hdmi.h | 33 +++++++++ include/uapi/drm/drm_mode.h | 16 ++++ 15 files changed, 433 insertions(+), 3 deletions(-) -- 1.9.1

3 39

[PATCH v1 0/2] Fix SDL 1.2 on emulated fbdev devices (broken in kernels >=4.19)
by Ivan Mironov 08 Jan '19

08 Jan '19

Hi, Originally this issue was brought up on linux.org.ru forum by user saahriktu, he is on Cc. He discovered that commit db05c48197759 ("drm: fb-helper: Reject all pixel format changing requests") breaks support of SDL1 programs, like various old games and emulators of old game consoles. First patch contains fix for that commit. I tried to reproduce the same issue in a VM under qemu, and found yet another part of kernel code which prevents SDL1 apps from running normally. Second patch in this series fixes this problem. Also, it seems that at least in some cases both problems could be circumvented by adding appropriate modes into /etc/fb.modes. But without examining the kernel code it is not clear which values are correct. I am not sure that such circumvention covers all possible cases, and it is definitely far from any user-frienliness. First patch in this series fixes a clear regression. Second patch is optional, please read commit message carefully before applying it. Changes in v1: - Added "Cc: stable" to the patch which fixes known regression. - Added more information and detailed reproduction steps in commit messages. Changes in v0: - RFC patch series introduced. Ivan Mironov (2): drm/fb-helper: Bring back workaround for bugs of SDL 1.2 drm/fb-helper: Ignore the value of fb_var_screeninfo.pixclock drivers/gpu/drm/drm_fb_helper.c | 153 +++++++++++++++++++++----------- 1 file changed, 99 insertions(+), 54 deletions(-) -- 2.20.1

4 11

[Bug 109140] [KBL-G][GL] KHR-GL43.compute_shader.max test failed
by bugzilla-daemon＠freedesktop.org 08 Jan '19

08 Jan '19

https://bugs.freedesktop.org/show_bug.cgi?id=109140 Bug ID: 109140 Summary: [KBL-G][GL] KHR-GL43.compute_shader.max test failed Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: hai.lan(a)intel.com When Use Kaby Lake-g(AMD Vega M GPU) to do the OpenGL CTS test, the case " KHR-GL43.compute_shader.max" will fail. KHR-GL44.compute_shader.max and KHR-GL45.compute_shader.max also failed Following is the environtment Platform KabyLake-G CPU Intel (R) Core (TM) i7-8809G CPU @3.10GHz GPU AMD(Radeon RX Vega M GH Graphics); Memory 16G OS Ubutu18.04 Kernel 4.19.0 Mesa: mesa 18.3.0 (https://mesa.freedesktop.org/archive/mesa-18.3.0.tar.gz) VK-GL-CTS version https://github.com/KhronosGroup/VK-GL-CTS commit 54e546a1a0a6fa412ea4c3e3081bbc9518928a6e How to reproduce run command: $ ./glcts -n KHR-GL43.compute_shader.max Writing test log into TestResults.qpa dEQP Core git-54e546a1a0a6fa412ea4c3e3081bbc9518928a6e (0x54e546a1) starting.. target implementation = 'Default' Test case 'KHR-GL43.compute_shader.max'.. Fail (Fail) DONE! Test run totals: Passed: 0/1 (0.0%) Failed: 1/1 (100.0%) Not supported: 0/1 (0.0%) Warnings: 0/1 (0.0%) -- You are receiving this mail because: You are the assignee for the bug.

1 3

linux-next: build warning after merge of the drm-misc tree
by Stephen Rothwell 07 Jan '19

07 Jan '19

Hi all, After merging the drm-misc tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: drivers/gpu/drm/msm/msm_gem.c: In function 'describe_fence': drivers/gpu/drm/msm/msm_gem.c:761:36: warning: format '%u' expects argument of type 'unsigned int', but argument 6 has type 'u64' {aka 'long long unsigned int'} [-Wformat=] seq_printf(m, "\t%9s: %s %s seq %u\n", type, ~^ %llu drivers/gpu/drm/msm/msm_gem.c:764:5: fence->seqno); ~~~~~~~~~~~~ Introduced by commit b312d8ca3a7c ("dma-buf: make fence sequence numbers 64 bit v2") -- Cheers, Stephen Rothwell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2019