dri-devel August 2019

dri-devel@lists.freedesktop.org

318 participants
2338 discussions

[CI] dma-fence: Propagate errors to dma-fence-array container
by Chris Wilson 11 Aug '19

11 Aug '19

When one of the array of fences is signaled, propagate its errors to the parent fence-array (keeping the first error to be raised). v2: Opencode cmpxchg_local to avoid compiler freakout. v3: Be careful not to flag an error if we race against signal-on-any. v4: Same applies to installing the signal cb. v5: Use cmpxchg to only set the error once before using a nifty idea by Christian to avoid changing the status after emitting the signal. Signed-off-by: Chris Wilson <chris(a)chris-wilson.co.uk> Cc: Sumit Semwal <sumit.semwal(a)linaro.org> Cc: Gustavo Padovan <gustavo(a)padovan.org> Cc: Christian König <christian.koenig(a)amd.com> Reviewed-by: Christian König <christian.koenig(a)amd.com> --- drivers/dma-buf/dma-fence-array.c | 32 ++++++++++++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/drivers/dma-buf/dma-fence-array.c b/drivers/dma-buf/dma-fence-array.c index 12c6f64c0bc2..d3fbd950be94 100644 --- a/drivers/dma-buf/dma-fence-array.c +++ b/drivers/dma-buf/dma-fence-array.c @@ -13,6 +13,8 @@ #include <linux/slab.h> #include <linux/dma-fence-array.h> +#define PENDING_ERROR 1 + static const char *dma_fence_array_get_driver_name(struct dma_fence *fence) { return "dma_fence_array"; @@ -23,10 +25,29 @@ static const char *dma_fence_array_get_timeline_name(struct dma_fence *fence) return "unbound"; } +static void dma_fence_array_set_pending_error(struct dma_fence_array *array, + int error) +{ + /* + * Propagate the first error reported by any of our fences, but only + * before we ourselves are signaled. + */ + if (error) + cmpxchg(&array->base.error, PENDING_ERROR, error); +} + +static void dma_fence_array_clear_pending_error(struct dma_fence_array *array) +{ + /* Clear the error flag if not actually set. */ + cmpxchg(&array->base.error, PENDING_ERROR, 0); +} + static void irq_dma_fence_array_work(struct irq_work *wrk) { struct dma_fence_array *array = container_of(wrk, typeof(*array), work); + dma_fence_array_clear_pending_error(array); + dma_fence_signal(&array->base); dma_fence_put(&array->base); } @@ -38,6 +59,8 @@ static void dma_fence_array_cb_func(struct dma_fence *f, container_of(cb, struct dma_fence_array_cb, cb); struct dma_fence_array *array = array_cb->array; + dma_fence_array_set_pending_error(array, f->error); + if (atomic_dec_and_test(&array->num_pending)) irq_work_queue(&array->work); else @@ -63,9 +86,14 @@ static bool dma_fence_array_enable_signaling(struct dma_fence *fence) dma_fence_get(&array->base); if (dma_fence_add_callback(array->fences[i], &cb[i].cb, dma_fence_array_cb_func)) { + int error = array->fences[i]->error; + + dma_fence_array_set_pending_error(array, error); dma_fence_put(&array->base); - if (atomic_dec_and_test(&array->num_pending)) + if (atomic_dec_and_test(&array->num_pending)) { + dma_fence_array_clear_pending_error(array); return false; + } } } @@ -142,6 +170,8 @@ struct dma_fence_array *dma_fence_array_create(int num_fences, atomic_set(&array->num_pending, signal_on_any ? 1 : num_fences); array->fences = fences; + array->base.error = PENDING_ERROR; + return array; } EXPORT_SYMBOL(dma_fence_array_create); -- 2.23.0.rc1

1 0

[CI] dma-fence: Propagate errors to dma-fence-array container
by Chris Wilson 11 Aug '19

11 Aug '19

1 0

[PATCH 1/2] drm: gm12u320: Do not take a mutex from a wait_event condition
by Hans de Goede 11 Aug '19

11 Aug '19

I made the condition of the wait_event_timeout call in gm12u320_fb_update_work a helper which takes a mutex to make sure that any writes to fb_update.run or fb_update.fb from other CPU cores are seen before the check is done. This is not necessary as the wait_event helpers contain the necessary barriers for this themselves. More over it is harmfull since by the time the check is done the task is no longer in the TASK_RUNNING state and calling mutex_lock while not in task-running is not allowed, leading to this warning when the kernel is build with some extra locking checks enabled: [11947.450011] do not call blocking ops when !TASK_RUNNING; state=2 set at [<00000000e4306de6>] prepare_to_wait_event+0x61/0x190 This commit fixes this by dropping the helper and simply directly checking the condition (without unnecessary locking) in the wait_event_timeout call. Signed-off-by: Hans de Goede <hdegoede(a)redhat.com> --- drivers/gpu/drm/tiny/gm12u320.c | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/drivers/gpu/drm/tiny/gm12u320.c b/drivers/gpu/drm/tiny/gm12u320.c index 4c47aa4de09b..4d66765b1125 100644 --- a/drivers/gpu/drm/tiny/gm12u320.c +++ b/drivers/gpu/drm/tiny/gm12u320.c @@ -342,17 +342,6 @@ static void gm12u320_copy_fb_to_blocks(struct gm12u320_device *gm12u320) mutex_unlock(&gm12u320->fb_update.lock); } -static int gm12u320_fb_update_ready(struct gm12u320_device *gm12u320) -{ - int ret; - - mutex_lock(&gm12u320->fb_update.lock); - ret = !gm12u320->fb_update.run || gm12u320->fb_update.fb != NULL; - mutex_unlock(&gm12u320->fb_update.lock); - - return ret; -} - static void gm12u320_fb_update_work(struct work_struct *work) { struct gm12u320_device *gm12u320 = @@ -426,7 +415,8 @@ static void gm12u320_fb_update_work(struct work_struct *work) * switches back to showing its logo. */ wait_event_timeout(gm12u320->fb_update.waitq, - gm12u320_fb_update_ready(gm12u320), + !gm12u320->fb_update.run || + gm12u320->fb_update.fb != NULL, IDLE_TIMEOUT); } return; -- 2.22.0

2 2

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming
by bugzilla-daemon＠freedesktop.org 11 Aug '19

11 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #82 from Mauro Gaspari <ilvipero(a)gmx.com> --- (In reply to Pierre-Eric Pelloux-Prayer from comment #81) > Can anyone provide a apitrace/renderdoc capture that can reliably reproduce > the crash/freeze? Hello, Sadly my freezes are hard to reproduce. Sometimes I can play for a day with no freeze, sometimes it freezes in 10 minutes, one hour, and so on. I had another freeze today: OS: openSUSE Tumbleweed x86_64 Kernel: 5.2.5-1-default Resolution: 3440x1440 DE: Xfce WM: Xfwm4 CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz GPU: AMD ATI Radeon VII Memory: 3791MiB / 64387MiB OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.3 Game: EVE Online: Wine+DXVK. (Crossover 18.5.0) vsync off frame limiter off Problem description: Afer rougly 1 hour of gameplay, desktop Frozen for a few seconds but managed to recover. Game did not recover and I killed the process. DMESG: [20612.721860] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=12880412, emitted seq=12880414 [20612.721921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process exefile.exe pid 1980 thread exefile.ex:cs0 pid 2057 [20612.721925] amdgpu 0000:0a:00.0: GPU reset begin! [20613.526448] amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) [20613.526502] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed [20613.547524] amdgpu 0000:0a:00.0: GPU mode1 reset [20614.055810] [drm] psp mode1 reset succeed [20614.128815] amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume [20614.128943] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000). [20614.129304] [drm] PSP is resuming... [20614.192202] [drm] reserve 0x400000 from 0x8000c00000 for PSP TMR SIZE [20614.649220] [drm] UVD and UVD ENC initialized successfully. [20614.748872] [drm] VCE initialized successfully. [20615.271942] [drm] Fence fallback timer expired on ring gfx [20615.783826] [drm] Fence fallback timer expired on ring comp_1.0.0 [20616.616023] [drm] Fence fallback timer expired on ring uvd_1 [20617.127844] [drm] Fence fallback timer expired on ring uvd_enc_1.0 [20617.639836] [drm] Fence fallback timer expired on ring uvd_enc_1.1 [20617.739606] [drm] recover vram bo from shadow start [20617.742231] [drm] recover vram bo from shadow done [20617.742233] [drm] Skip scheduling IBs! [20617.742234] [drm] Skip scheduling IBs! [20617.742259] amdgpu 0000:0a:00.0: GPU reset(2) succeeded! [20617.742289] [drm] Skip scheduling IBs! [20617.742309] [drm] Skip scheduling IBs! [20617.742314] [drm] Skip scheduling IBs! [20617.742316] [drm] Skip scheduling IBs! [20617.742318] [drm] Skip scheduling IBs! [20617.742320] [drm] Skip scheduling IBs! [20617.743840] [drm] Skip scheduling IBs! [20617.744006] [drm] Skip scheduling IBs! [20617.744180] [drm] Skip scheduling IBs! [20617.744450] [drm] Skip scheduling IBs! System Logs: 2019-08-11T17:13:10.377029+08:00 MGDT-ROG kernel: [20612.721860] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=12880412, emitted seq=12880414 2019-08-11T17:13:10.377046+08:00 MGDT-ROG kernel: [20612.721921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process exefile.exe pid 1980 thread exefile.ex:cs0 pid 2057 2019-08-11T17:13:10.377047+08:00 MGDT-ROG kernel: [20612.721925] amdgpu 0000:0a:00.0: GPU reset begin! 2019-08-11T17:13:11.182763+08:00 MGDT-ROG kernel: [20613.526448] amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) 2019-08-11T17:13:11.182776+08:00 MGDT-ROG kernel: [20613.526502] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed 2019-08-11T17:13:11.202766+08:00 MGDT-ROG kernel: [20613.547524] amdgpu 0000:0a:00.0: GPU mode1 reset 2019-08-11T17:13:11.714757+08:00 MGDT-ROG kernel: [20614.055810] [drm] psp mode1 reset succeed 2019-08-11T17:13:11.786740+08:00 MGDT-ROG kernel: [20614.128815] amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume 2019-08-11T17:13:11.786749+08:00 MGDT-ROG kernel: [20614.128943] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000). 2019-08-11T17:13:11.786751+08:00 MGDT-ROG kernel: [20614.129304] [drm] PSP is resuming... 2019-08-11T17:13:11.850739+08:00 MGDT-ROG kernel: [20614.192202] [drm] reserve 0x400000 from 0x8000c00000 for PSP TMR SIZE 2019-08-11T17:13:12.306756+08:00 MGDT-ROG kernel: [20614.649220] [drm] UVD and UVD ENC initialized successfully. 2019-08-11T17:13:12.406756+08:00 MGDT-ROG kernel: [20614.748872] [drm] VCE initialized successfully. 2019-08-11T17:13:12.926899+08:00 MGDT-ROG kernel: [20615.271942] [drm] Fence fallback timer expired on ring gfx 2019-08-11T17:13:13.438783+08:00 MGDT-ROG kernel: [20615.783826] [drm] Fence fallback timer expired on ring comp_1.0.0 2019-08-11T17:13:14.274773+08:00 MGDT-ROG kernel: [20616.616023] [drm] Fence fallback timer expired on ring uvd_1 2019-08-11T17:13:14.671435+08:00 MGDT-ROG tracker-store[4801]: OK 2019-08-11T17:13:14.672970+08:00 MGDT-ROG systemd[2481]: tracker-store.service: Succeeded. 2019-08-11T17:13:14.782896+08:00 MGDT-ROG kernel: [20617.127844] [drm] Fence fallback timer expired on ring uvd_enc_1.0 2019-08-11T17:13:15.294768+08:00 MGDT-ROG kernel: [20617.639836] [drm] Fence fallback timer expired on ring uvd_enc_1.1 2019-08-11T17:13:15.394759+08:00 MGDT-ROG kernel: [20617.739606] [drm] recover vram bo from shadow start 2019-08-11T17:13:15.397215+08:00 MGDT-ROG kernel: [20617.742231] [drm] recover vram bo from shadow done 2019-08-11T17:13:15.397227+08:00 MGDT-ROG kernel: [20617.742233] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397228+08:00 MGDT-ROG kernel: [20617.742234] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397231+08:00 MGDT-ROG kernel: [20617.742259] amdgpu 0000:0a:00.0: GPU reset(2) succeeded! 2019-08-11T17:13:15.397233+08:00 MGDT-ROG kernel: [20617.742289] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397235+08:00 MGDT-ROG kernel: [20617.742309] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397242+08:00 MGDT-ROG kernel: [20617.742314] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397262+08:00 MGDT-ROG kernel: [20617.742316] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397265+08:00 MGDT-ROG kernel: [20617.742318] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397268+08:00 MGDT-ROG kernel: [20617.742320] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402744+08:00 MGDT-ROG kernel: [20617.743840] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402753+08:00 MGDT-ROG kernel: [20617.744006] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402755+08:00 MGDT-ROG kernel: [20617.744180] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402757+08:00 MGDT-ROG kernel: [20617.744450] [drm] Skip scheduling IBs! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 201285] New: Kernel oops in amdgpu with Ryzen5 2400G
by bugzilla-daemon＠bugzilla.kernel.org 10 Aug '19

10 Aug '19

https://bugzilla.kernel.org/show_bug.cgi?id=201285 Bug ID: 201285 Summary: Kernel oops in amdgpu with Ryzen5 2400G Product: Drivers Version: 2.5 Kernel Version: 4.19-rc5 Hardware: Intel OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: phil(a)kantaka.co.uk Regression: No I'm seeing this oops on every boot, consistently ever since this hardware started consistently coming up at all. Hardware is; Gigabyte AB350N-Gaming WIFI/AB350N-Gaming WIFI-CF, BIOS F23. 8Gb RAM Ryzen 5 2400G Vega. Kernel 4.19-rc5 (but this oops has been there ever since the hardware started working consistently somewhere in the early 4.19-rc releases.) Display is Dell U2518D 25" 2560x1440 connected via Displayport. [ 3.096828] amdgpu: [powerplay] dpm has been enabled [ 3.096900] [drm] DM_PPLIB: values for Invalid clock [ 3.096900] [drm] DM_PPLIB: 0 in kHz [ 3.096901] [drm] DM_PPLIB: 0 in kHz [ 3.096901] [drm] DM_PPLIB: 0 in kHz [ 3.096901] [drm] DM_PPLIB: 1333000 in kHz [ 3.096977] WARNING: CPU: 0 PID: 316 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1372 dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu] [ 3.096977] Modules linked in: usbhid(+) hid arc4 binfmt_misc nls_ascii nls_cp437 vfat fat edac_mce_amd kvm_amd ccp rng_core iwlmvm kvm irqbypass btusb mac80211 crct10dif_pclmul amdkfd btrtl crc32_pclmul btbcm btintel ghash_clmulni_intel pcbc iwlwifi snd_hda_codec_realtek bluetooth efi_pstore snd_hda_codec_generic amdgpu(+) snd_hda_codec_hdmi jitterentropy_rng chash snd_hda_intel gpu_sched ttm snd_hda_codec drbg wmi_bmof snd_hda_core ansi_cprng aesni_intel drm_kms_helper aes_x86_64 evdev snd_hwdep ecdh_generic cfg80211 crypto_simd drm cryptd rfkill glue_helper pcspkr efivars k10temp sg i2c_algo_bit snd_pcm snd_timer snd soundcore sp5100_tco wmi pcc_cpufreq video button acpi_cpufreq efivarfs ip_tables x_tables autofs4 ext4 crc32c_generic crc16 mbcache jbd2 fscrypto sd_mod ahci xhci_pci libahci r8169 [ 3.097005] xhci_hcd crc32c_intel libata i2c_piix4 libphy usbcore scsi_mod gpio_amdpt gpio_generic [ 3.097010] CPU: 0 PID: 316 Comm: systemd-udevd Not tainted 4.19.0-rc5 #16 [ 3.097011] Hardware name: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI/AB350N-Gaming WIFI-CF, BIOS F23 08/08/2018 [ 3.097059] RIP: 0010:dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu] [ 3.097060] Code: d8 ca d8 f1 d9 5a 50 8b 44 fc 14 49 8b 94 24 78 01 00 00 48 89 04 24 df 2c 24 d8 f1 db 42 78 de c9 de ca de f9 d9 5a 4c eb 02 <0f> 0b 48 89 da be 04 00 00 00 48 89 ef e8 83 55 fe ff 84 c0 0f 84 [ 3.097061] RSP: 0018:ffffa7588144f7b8 EFLAGS: 00010246 [ 3.097062] RAX: 0000000000000001 RBX: ffffa7588144f818 RCX: 0000000000000000 [ 3.097062] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff8f70d7a166a0 [ 3.097063] RBP: ffff8f70d1af5000 R08: 00000000000004d3 R09: 0000000000000004 [ 3.097063] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8f70d18f1000 [ 3.097064] R13: ffff8f70cf471920 R14: ffff8f70d18f1000 R15: 0000000000000000 [ 3.097065] FS: 00007f38d41ef8c0(0000) GS:ffff8f70d7a00000(0000) knlGS:0000000000000000 [ 3.097066] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.097066] CR2: 00007fd9234ecfe0 CR3: 000000021450a000 CR4: 00000000003406f0 [ 3.097067] Call Trace: [ 3.097073] ? _cond_resched+0x15/0x30 [ 3.097138] dcn10_create_resource_pool+0x781/0x9d0 [amdgpu] [ 3.097191] ? dal_aux_engine_dce110_create+0x39/0x70 [amdgpu] [ 3.097236] dc_create_resource_pool+0x42/0x180 [amdgpu] [ 3.097237] ? _cond_resched+0x15/0x30 [ 3.097240] ? __kmalloc+0x177/0x210 [ 3.097290] ? dal_gpio_service_create+0x8f/0x110 [amdgpu] [ 3.097348] dc_create+0x20f/0x620 [amdgpu] [ 3.097416] dm_hw_init+0xc8/0x130 [amdgpu] [ 3.097483] amdgpu_device_init.cold.28+0x10ea/0x1295 [amdgpu] [ 3.097573] amdgpu_driver_load_kms+0x86/0x2c0 [amdgpu] [ 3.097584] drm_dev_register+0x109/0x140 [drm] [ 3.097649] amdgpu_pci_probe+0x13c/0x1c0 [amdgpu] [ 3.097652] local_pci_probe+0x41/0x90 [ 3.097655] pci_device_probe+0x189/0x1a0 [ 3.097657] really_probe+0x235/0x3a0 [ 3.097659] driver_probe_device+0xb3/0xf0 [ 3.097660] __driver_attach+0xdd/0x110 [ 3.097662] ? driver_probe_device+0xf0/0xf0 [ 3.097663] bus_for_each_dev+0x76/0xc0 [ 3.097665] ? klist_add_tail+0x3b/0x70 [ 3.097666] bus_add_driver+0x152/0x230 [ 3.097668] ? 0xffffffffc0e3b000 [ 3.097669] driver_register+0x6b/0xb0 [ 3.097670] ? 0xffffffffc0e3b000 [ 3.097672] do_one_initcall+0x46/0x1c3 [ 3.097674] ? _cond_resched+0x15/0x30 [ 3.097677] ? kmem_cache_alloc_trace+0x155/0x1d0 [ 3.097691] do_init_module+0x5a/0x210 [ 3.097705] load_module+0x20b1/0x22c0 [ 3.097708] ? __do_sys_finit_module+0xa8/0x110 [ 3.097709] __do_sys_finit_module+0xa8/0x110 [ 3.097711] do_syscall_64+0x55/0xe0 [ 3.097713] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3.097714] RIP: 0033:0x7f38d4e51a79 [ 3.097716] 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 df 43 0c 00 f7 d8 64 89 01 48 [ 3.097717] RSP: 002b:00007ffdc62527b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 3.097719] RAX: ffffffffffffffda RBX: 0000562eaf698600 RCX: 00007f38d4e51a79 [ 3.097719] RDX: 0000000000000000 RSI: 00007f38d4b590ed RDI: 0000000000000014 [ 3.097720] RBP: 00007f38d4b590ed R08: 0000000000000000 R09: 0000000000000000 [ 3.097720] R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000 [ 3.097721] R13: 0000562eaf6d1450 R14: 0000000000020000 R15: 0000562eaf698600 [ 3.097722] ---[ end trace 0b370350fb262101 ]--- [ 3.097883] [drm] DM_PPLIB: values for Invalid clock [ 3.097884] [drm] DM_PPLIB: 300000 in kHz [ 3.097884] [drm] DM_PPLIB: 600000 in kHz [ 3.097884] [drm] DM_PPLIB: 626000 in kHz [ 3.097885] [drm] DM_PPLIB: 654000 in kHz [ 3.098234] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3 [ 3.098284] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 3.106418] [drm] Display Core initialized with v3.1.59! [ 3.134934] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.134935] [drm] Driver supports precise vblank timestamp query. Happy to test any patches etc. Kernel is compiled with: CONFIG_DRM_AMDGPU=m CONFIG_DRM_AMDGPU_SI=y CONFIG_DRM_AMDGPU_CIK=y CONFIG_DRM_AMDGPU_USERPTR=y # CONFIG_DRM_AMDGPU_GART_DEBUGFS is not set CONFIG_DRM_AMD_ACP=y CONFIG_DRM_AMD_DC=y CONFIG_DRM_AMD_DC_DCN1_0=y -- You are receiving this mail because: You are watching the assignee of the bug.

1 9

[Bug 111370] Cannot get OpenCL visible with Radeon VII installation
by bugzilla-daemon＠freedesktop.org 10 Aug '19

10 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=111370 Bas Nieuwenhuizen <bas(a)basnieuwenhuizen.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev(a)lists.freedesktop. |dri-devel(a)lists.freedesktop |org |.org Component|Drivers/Vulkan/radeon |DRM/AMDgpu-pro Product|Mesa |DRI QA Contact|mesa-dev(a)lists.freedesktop. | |org | --- Comment #2 from Bas Nieuwenhuizen <bas(a)basnieuwenhuizen.nl> --- AFAIU right site, but definitely wrong component -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 109524] "Invalid glsl version in shading_language_version()" when trying to run directX games using wine
by bugzilla-daemon＠freedesktop.org 10 Aug '19

10 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=109524 Bug ID: 109524 Summary: "Invalid glsl version in shading_language_version()" when trying to run directX games using wine Product: Mesa Version: 18.2 Hardware: x86 (IA32) OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R100 Assignee: dri-devel(a)lists.freedesktop.org Reporter: laszlo.erdoes(a)freenet.de QA Contact: dri-devel(a)lists.freedesktop.org When I try running any software in wine that uses direct3D, I get the following message and an app crash: Mesa 18.2.8 implementation error: Invalid GLSL version in shading_language_version() Please report at https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa wine: Unhandled page fault on read access to 0x00000000 at address 0xb7bf1440 (thread 0009), starting debugger... I'm using an R100 GPU. The problem wasn't present in some earlier versions of Mesa, I believe it still worked in some 17.x version. -- You are receiving this mail because: You are the assignee for the bug.

1 15

Re: The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here)
by Mikhail Gavrilov 10 Aug '19

10 Aug '19

On Fri, 9 Aug 2019 at 23:55, Mikhail Gavrilov <mikhail.v.gavrilov(a)gmail.com> wrote: > Finally initial problem "gnome-shell: page allocation failure: > order:4, mode:0x40cc0(GFP_KERNEL|__GFP_COMP), > nodemask=(null),cpuset=/,mems_allowed=0" did not happens anymore with > latest version of the patch (I tested more than 23 hours) > > But I hit a new problem: > > [73808.088801] ------------[ cut here ]------------ > [73808.088806] DEBUG_LOCKS_WARN_ON(ww_ctx->contending_lock) > [73808.088813] WARNING: CPU: 8 PID: 1348877 at > kernel/locking/mutex.c:757 __ww_mutex_lock.constprop.0+0xb0f/0x10c0 [pruned] > So I needed to report it separately (in another thread) or we continue here? Today after reboot issue "DEBUG LOCKS WARN_ON(ww_ctx->contending_lock)" happened again. -- Best Regards, Mike Gavrilov.

1 0

[Bug 111231] VM_L2_PROTECTION_FAULT
by bugzilla-daemon＠freedesktop.org 10 Aug '19

10 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=111231 Bug ID: 111231 Summary: VM_L2_PROTECTION_FAULT Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: ds2.bugs.freedesktop(a)gmail.com When playing minetest on an AMD ryzen 2200G with vega integrated graphics, occasionally the system will appear to suffer a graphics lock-up during game load when the loading bar appears. When this occours, dmesg spits out a VM_L2_PROTECTION_FAULT and then repeated errors about fence timeouts: [ 5699.136659] amdgpu 0000:0b:00.0: [gfxhub] no-retry page fault (src_id:0 ring:155 vmid:5 pasid:32770, for process minetest pid 7127 thread minetest:cs0 pid 7133) [ 5699.136662] amdgpu 0000:0b:00.0: in page starting at address 0x000080014034d000 from 27 [ 5699.136664] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00501136 [ 5704.343299] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out. [ 5709.259775] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=443165, emitted seq=443167 [ 5709.259860] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process minetest pid 7127 thread minetest:cs0 pid 7133 [ 5709.259862] [drm] GPU recovery disabled. [ 5709.463238] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out. [ 5719.286451] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=443165, emitted seq=443167 [ 5719.286537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process minetest pid 7127 thread minetest:cs0 pid 7133 [ 5719.286539] [drm] GPU recovery disabled. [ 5729.312836] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=443165, emitted seq=443167 [ 5729.312921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process minetest pid 7127 thread minetest:cs0 pid 7133 [ 5729.312923] [drm] GPU recovery disabled. [ 5739.339485] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=443165, emitted seq=443167 [ 5739.339570] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process minetest pid 7127 thread minetest:cs0 pid 7133 [ 5739.339572] [drm] GPU recovery disabled. [ 5749.366552] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=443165, emitted seq=443167 [ 5749.366637] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process minetest pid 7127 thread minetest:cs0 pid 7133 [ 5749.366640] [drm] GPU recovery disabled. Notably, when playing minetest normally, this doesn't always happen, but when it does the screen gets a light covering of graphical corruption "confetti" (photos to follow - had to be taken on a phone, sorry). Currently running a mesa debug build compiled from git at commit b0626c1f306 after seeing if https://bugs.freedesktop.org/show_bug.cgi?id=105251 had anything to do with it - I think this is related but not entirely a duplicate, as a fix mentioned there did stop the test program there from having an effect but did not stop this problem. In the course of trying to reproduce this problem in a more repeatable manner, I decided to take an apitrace (will attach in following messages). Interestingly, the brief trace I took did not crash my system during recording of it, but now replaying it will fairly regularly cause the same kind of lockup, more frequently than the game itself will. I ran apitrace replay in verbose mode to see whereabouts it stopped to see if this gave an approximate indications of where things starting going pear shaped. The point at which output ends is well short of the entire apitrace dump, as expected from what I saw - and additionally the stderr appears to contain an exception of some kind. See the apitrace.out.txt and apitrace.err.txt attachments (to follow separately). I haven't yet got a dmesg output during minetest running itself, but I have got some runs (spanning from boot to either hard or soft reboot - sometimes xorg was killable, othertimes not) from replaying the offending api trace. These will also be attached in follow-up messages. These appear to have a lot more GPU faults before the messages about timeouts appear. -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 111368] the bug is visible at the site
by bugzilla-daemon＠freedesktop.org 10 Aug '19

10 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=111368 Bug ID: 111368 Summary: the bug is visible at the site Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: minor Priority: medium Component: General Assignee: dri-devel(a)lists.freedesktop.org Reporter: saurabhdubey0601(a)gmail.com Created attachment 145017 --> https://bugs.freedesktop.org/attachment.cgi?id=145017&action=edit the bug is highlighted -- You are receiving this mail because: You are the assignee for the bug.

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2019