[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #41 from Jan Kokemüller (jan.kokemuel...@gmail.com) --- > Looks correct. Care to send out a proper git patch? Thank you for having a look at the patch! I've sent it to the amd-gfx list. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #40 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Jan Kokemüller from comment #39) > Created attachment 295225 [details] > Call DC_FP_START() / DC_FP_END() in dcn21_validate_bandwidth > > Could it be that DC_FP_START()/DC_FP_END() aka > kernel_fpu_begin()/kernel_fpu_end() are not called in the > *_validate_bandwidth code path on AMD Renoir systems? To my untrained eye it > looks like it is missing, while it _is_ there for dcn20. > > I've been running the attached patch for 2 days now with some KVM VMs open > and the system seems stable. Previously, I had similar crashes/backtraces > @krakopo described. > > I'm happy to help testing any patches. I'm running a Thinkpad T14 with a AMD > Ryzen 7 PRO 4750U (Renoir). Looks correct. Care to send out a proper git patch? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Jan Kokemüller (jan.kokemuel...@gmail.com) changed: What|Removed |Added CC||jan.kokemuel...@gmail.com --- Comment #39 from Jan Kokemüller (jan.kokemuel...@gmail.com) --- Created attachment 295225 --> https://bugzilla.kernel.org/attachment.cgi?id=295225=edit Call DC_FP_START() / DC_FP_END() in dcn21_validate_bandwidth Could it be that DC_FP_START()/DC_FP_END() aka kernel_fpu_begin()/kernel_fpu_end() are not called in the *_validate_bandwidth code path on AMD Renoir systems? To my untrained eye it looks like it is missing, while it _is_ there for dcn20. I've been running the attached patch for 2 days now with some KVM VMs open and the system seems stable. Previously, I had similar crashes/backtraces @krakopo described. I'm happy to help testing any patches. I'm running a Thinkpad T14 with a AMD Ryzen 7 PRO 4750U (Renoir). -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #38 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- @krakopo I must say I don't have any idea what could be happening on your machine. It could be explained if the kernel thread was being pre-empted, but pre-emption is disabled by kernel_fpu_begin(). It may help to ask in bug 207979 also, it has some of the long time x86 maintainers on CC. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #37 from krak...@protonmail.com --- I do see ldmxcsr in the disassembly: 81038870 : 81038870: e8 9b 07 03 00 callq 81069010 <__fentry__> 81038875: 48 83 ec 10 sub$0x10,%rsp 81038879: bf 01 00 00 00 mov$0x1,%edi 8103887e: 65 48 8b 04 25 28 00mov%gs:0x28,%rax 81038885: 00 00 81038887: 48 89 44 24 08 mov%rax,0x8(%rsp) 8103888c: 31 c0 xor%eax,%eax 8103888e: c7 44 24 04 00 00 00movl $0x0,0x4(%rsp) 81038895: 00 81038896: e8 35 ae 08 00 callq 810c36d0 8103889b: e8 80 fd ff ff callq 81038620 810388a0: 65 8a 05 b1 f2 fd 7emov%gs:0x7efdf2b1(%rip),%al # 17b58 810388a7: 65 c6 05 a9 f2 fd 7emovb $0x1,%gs:0x7efdf2a9(%rip)# 17b58 810388ae: 01 810388af: 65 48 8b 3c 25 c0 7bmov%gs:0x17bc0,%rdi 810388b6: 01 00 810388b8: f6 47 26 20 testb $0x20,0x26(%rdi) 810388bc: 74 3c je 810388fa 810388be: 48 c7 c7 57 43 40 82mov$0x82404357,%rdi 810388c5: e8 46 41 9c 00 callq 819fca10 <__this_cpu_preempt_check> 810388ca: c7 44 24 04 80 1f 00movl $0x1f80,0x4(%rsp) 810388d1: 00 810388d2: 65 48 c7 05 82 f2 fdmovq $0x0,%gs:0x7efdf282(%rip)# 17b60 810388d9: 7e 00 00 00 00 810388de: 0f ae 54 24 04 ldmxcsr 0x4(%rsp) 810388e3: db e3 fninit 810388e5: 48 8b 44 24 08 mov0x8(%rsp),%rax 810388ea: 65 48 2b 04 25 28 00sub%gs:0x28,%rax 810388f1: 00 00 810388f3: 75 20 jne81038915 810388f5: 48 83 c4 10 add$0x10,%rsp 810388f9: c3 retq 810388fa: 48 8b 07mov(%rdi),%rax 810388fd: f6 c4 40test $0x40,%ah 81038900: 75 bc jne810388be 81038902: f0 80 4f 01 40 lock orb $0x40,0x1(%rdi) 81038907: 48 81 c7 00 1b 00 00add$0x1b00,%rdi 8103890e: e8 5d fd ff ff callq 81038670 81038913: eb a9 jmp810388be 81038915: e8 36 3c 9c 00 callq 819fc550 <__stack_chk_fail> 8103891a: 66 0f 1f 44 00 00 nopw 0x0(%rax,%rax,1) And yes I do have the "sse" flag in /proc/cpuinfo. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #36 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- @krakopo The 0020 MXCSR value is also exactly like it was for me before the bug fix. So something is definitely clearing MXCSR after it should be set to 0x1F80 by kernel_fpu_begin(). Can you disassemble kernel_fpu_begin() to verify that the ldmxcsr instruction is present close to its end? Also, check that /proc/cpuinfo flags has "sse" in it - not sure though how that could possibly be missing. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #35 from krak...@protonmail.com --- @Petteri I'm running DragonFly BSD 5.8.1 in my KVM virtual machine. Here is the dmesg output with the debug info patch applied: Aug 19 23:18:03 archpad kernel: MXCSR: 0020 XMM3: 4010 Aug 19 23:18:03 archpad kernel: simd exception: [#1] PREEMPT SMP NOPTI Aug 19 23:18:03 archpad kernel: CPU: 5 PID: 518 Comm: Xorg Not tainted 5.8.1-arch1206987 #1 Aug 19 23:18:03 archpad kernel: Hardware name: LENOVO 81W4/LNVNB161216, BIOS DZCN19WW 04/13/2020 Aug 19 23:18:03 archpad kernel: RIP: 0010:dcn_bw_ceil2+0x35/0x60 [amdgpu] Aug 19 23:18:03 archpad kernel: Code: cd 7b 3e 0f 28 d0 66 0f ef db 66 0f ef e4 f3 0f 5e d1 f3 0f 5a e0 f3 0f 2c c2 66 0f ef d2 f3 0f 2a d0 f3 0f 59 d1 f3 0f 5a da 0f 58 1d 5b 19 2e 00 66 0f 2f dc 72 01 c3 f3 0f 58 ca 0f 28 c1 Aug 19 23:18:03 archpad kernel: RSP: 0018:9e24c10775f8 EFLAGS: 00010202 Aug 19 23:18:03 archpad kernel: RAX: 0004 RBX: RCX: 0780 Aug 19 23:18:03 archpad kernel: RDX: 93d6d0683080 RSI: 93d6d0689560 RDI: 4440 Aug 19 23:18:03 archpad kernel: RBP: 93d6d06831c0 R08: 93d6d06833b4 R09: Aug 19 23:18:03 archpad kernel: R10: R11: R12: 93d6d0683360 Aug 19 23:18:03 archpad kernel: R13: 0001 R14: 93d6d0682188 R15: 93d6d0682028 Aug 19 23:18:03 archpad kernel: FS: 7f78d940() GS:93d70774() knlGS: Aug 19 23:18:03 archpad kernel: CS: 0010 DS: ES: CR0: 80050033 Aug 19 23:18:03 archpad kernel: CR2: 000800ea8030 CR3: 0002021ca000 CR4: 00340ee0 Aug 19 23:18:03 archpad kernel: Call Trace: Aug 19 23:18:03 archpad kernel: dml21_ModeSupportAndSystemConfigurationFull+0x437/0x5cf0 [amdgpu] Aug 19 23:18:03 archpad kernel: ? cpufreq_this_cpu_can_update+0xe/0x50 Aug 19 23:18:03 archpad kernel: ? sugov_update_single+0x58/0x210 Aug 19 23:18:03 archpad kernel: ? sugov_get_util+0xf0/0xf0 Aug 19 23:18:03 archpad kernel: ? update_blocked_averages+0x539/0x620 Aug 19 23:18:03 archpad kernel: ? update_group_capacity+0x25/0x1c0 Aug 19 23:18:03 archpad kernel: ? cpumask_next_and+0x19/0x20 Aug 19 23:18:03 archpad kernel: ? update_sd_lb_stats.constprop.0+0x799/0x8f0 Aug 19 23:18:03 archpad kernel: ? cpufreq_this_cpu_can_update+0xe/0x50 Aug 19 23:18:03 archpad kernel: ? sugov_update_single+0x143/0x210 Aug 19 23:18:03 archpad kernel: ? sugov_get_util+0xf0/0xf0 Aug 19 23:18:03 archpad kernel: ? update_load_avg+0x63a/0x660 Aug 19 23:18:03 archpad kernel: ? update_curr+0x73/0x1f0 Aug 19 23:18:03 archpad kernel: ? enqueue_entity+0x14e/0x750 Aug 19 23:18:03 archpad kernel: ? resched_curr+0x20/0xc0 Aug 19 23:18:03 archpad kernel: ? check_preempt_wakeup+0x13b/0x250 Aug 19 23:18:03 archpad kernel: ? check_preempt_curr+0x67/0x90 Aug 19 23:18:03 archpad kernel: ? _raw_spin_unlock+0x16/0x30 Aug 19 23:18:03 archpad kernel: dml_get_voltage_level+0x116/0x1e0 [amdgpu] Aug 19 23:18:03 archpad kernel: dcn20_fast_validate_bw+0x359/0x680 [amdgpu] Aug 19 23:18:03 archpad kernel: ? resource_build_scaling_params+0xc44/0x11a0 [amdgpu] Aug 19 23:18:03 archpad kernel: dcn21_validate_bandwidth+0xcd/0x2a0 [amdgpu] Aug 19 23:18:03 archpad kernel: dc_validate_global_state+0x2f2/0x390 [amdgpu] Aug 19 23:18:03 archpad kernel: amdgpu_dm_atomic_check+0xefb/0x1010 [amdgpu] Aug 19 23:18:03 archpad kernel: ? free_one_page+0x57/0xd0 Aug 19 23:18:03 archpad kernel: drm_atomic_check_only+0x57c/0x7f0 [drm] Aug 19 23:18:03 archpad kernel: ? __drm_atomic_helper_crtc_duplicate_state+0x85/0xd0 [drm_kms_helper] Aug 19 23:18:03 archpad kernel: drm_atomic_commit+0x13/0x50 [drm] Aug 19 23:18:03 archpad kernel: drm_atomic_helper_legacy_gamma_set+0x123/0x180 [drm_kms_helper] Aug 19 23:18:03 archpad kernel: drm_mode_gamma_set_ioctl+0x19a/0x230 [drm] Aug 19 23:18:03 archpad kernel: ? drm_color_lut_check+0xa0/0xa0 [drm] Aug 19 23:18:03 archpad kernel: drm_ioctl_kernel+0xb2/0x100 [drm] Aug 19 23:18:03 archpad kernel: drm_ioctl+0x208/0x360 [drm] Aug 19 23:18:03 archpad kernel: ? drm_color_lut_check+0xa0/0xa0 [drm] Aug 19 23:18:03 archpad kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Aug 19 23:18:03 archpad kernel: ksys_ioctl+0x82/0xc0 Aug 19 23:18:03 archpad kernel: __x64_sys_ioctl+0x16/0x20 Aug 19 23:18:03 archpad kernel: do_syscall_64+0x44/0x70 Aug 19 23:18:03 archpad kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 19 23:18:03 archpad kernel: RIP: 0033:0x7f22234b08eb Aug 19 23:18:03 archpad kernel: Code: 0f 1e fa 48 8b 05 a5 95 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 95 0c 00 f7 d8 64 89 01 48 Aug 19 23:18:03 archpad kernel: RSP: 002b:7ffee6662f48 EFLAGS: 0246 ORIG_RAX: 0010 Aug 19 23:18:03 archpad kernel: RAX: ffda RBX: 7ffee6662f80 RCX:
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #34 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- @krakopo Can you apply the debug info patch from here? https://bugzilla.kernel.org/attachment.cgi?id=289421=diff What kernel are you running inside the KVM virtual machine? I wonder if the virtual machine has the MXCSR problem, perhaps it could be leaking to the host somehow. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987
krak...@protonmail.com changed:
What|Removed |Added
CC||krak...@protonmail.com
--- Comment #33 from krak...@protonmail.com ---
I'm seeing this on an AMD Ryzen 4500U laptop running 5.8.1 (Arch Linux
5.8.1-arch1-1). I can repro fairly consistently when running a 64-bit KVM
virtual machine.
The kernel I'm running has the commit which should resolve this:
7ad816762f9b ("x86/fpu: Reset MXCSR to default in kernel_fpu_begin()")
Confirmed patch is in my kernel:
https://git.archlinux.org/linux.git/tree/arch/x86/kernel/fpu/core.c?h=v5.8.1-arch1#n106
Here is what I see in dmesg:
Aug 18 20:25:49 archpad kernel: simd exception: [#1] PREEMPT SMP NOPTI
Aug 18 20:25:49 archpad kernel: CPU: 0 PID: 509 Comm: Xorg Not tainted
5.8.1-arch1-1 #1
Aug 18 20:25:49 archpad kernel: Hardware name: LENOVO 81W4/LNVNB161216, BIOS
DZCN19WW 04/13/2020
Aug 18 20:25:49 archpad kernel: RIP: 0010:dcn_bw_ceil2+0x35/0x60 [amdgpu]
Aug 18 20:25:49 archpad kernel: Code: cd 7b 3e 0f 28 d0 66 0f ef db 66 0f ef e4
f3 0f 5e d1 f3 0f 5a e0 f3 0f 2c c2 66 0f ef d2 f3 0f 2a d0 f3 0f 59 d1 f3 0f
5a da 0f 58 1d 5b 19 2e 00 66 0f 2f dc 72 01 c3 f3 0f 58 ca 0f 28 c1
Aug 18 20:25:49 archpad kernel: RSP: 0018:b8fac07035f8 EFLAGS: 00010202
Aug 18 20:25:49 archpad kernel: RAX: 0004 RBX:
RCX: 0780
Aug 18 20:25:49 archpad kernel: RDX: 97ebd0a63080 RSI: 97ebd0a69560
RDI: 4440
Aug 18 20:25:49 archpad kernel: RBP: 97ebd0a631c0 R08: 97ebd0a633b4
R09:
Aug 18 20:25:49 archpad kernel: R10: R11:
R12: 97ebd0a63360
Aug 18 20:25:49 archpad kernel: R13: 0001 R14: 97ebd0a62188
R15: 97ebd0a62028
Aug 18 20:25:49 archpad kernel: FS: 7f8787a65940()
GS:97ec4740() knlGS:
Aug 18 20:25:49 archpad kernel: CS: 0010 DS: ES: CR0:
80050033
Aug 18 20:25:49 archpad kernel: CR2: 00080088 CR3: 0001f904
CR4: 00340ef0
Aug 18 20:25:49 archpad kernel: Call Trace:
Aug 18 20:25:49 archpad kernel:
dml21_ModeSupportAndSystemConfigurationFull+0x437/0x5cf0 [amdgpu]
Aug 18 20:25:49 archpad kernel: ? sysvec_apic_timer_interrupt+0x46/0xe0
Aug 18 20:25:49 archpad kernel: ? asm_sysvec_apic_timer_interrupt+0x12/0x20
Aug 18 20:25:49 archpad kernel: ? sched_clock+0x5/0x10
Aug 18 20:25:49 archpad kernel: ? sched_clock_local+0x12/0x80
Aug 18 20:25:49 archpad kernel: ? amdgpu_sa_bo_new+0xbc/0x550 [amdgpu]
Aug 18 20:25:49 archpad kernel: ? sched_clock_cpu+0xae/0xd0
Aug 18 20:25:49 archpad kernel: ? kmem_cache_alloc_trace+0x17c/0x220
Aug 18 20:25:49 archpad kernel: ? amdgpu_sa_bo_new+0xbc/0x550 [amdgpu]
Aug 18 20:25:49 archpad kernel: ? _raw_spin_unlock+0x16/0x30
Aug 18 20:25:49 archpad kernel: ? preempt_count_add+0x49/0xa0
Aug 18 20:25:49 archpad kernel: ? kernel_init_free_pages+0x6d/0x90
Aug 18 20:25:49 archpad kernel: ? prep_new_page+0xa2/0xb0
Aug 18 20:25:49 archpad kernel: ? get_page_from_freelist+0xfa8/0x1220
Aug 18 20:25:49 archpad kernel: ? __mod_zone_page_state+0x66/0xa0
Aug 18 20:25:49 archpad kernel: ? hubbub2_get_dcc_compression_cap+0xa8/0x270
[amdgpu]
Aug 18 20:25:49 archpad kernel: ? fill_plane_buffer_attributes+0x26f/0x420
[amdgpu]
Aug 18 20:25:49 archpad kernel: dml_get_voltage_level+0x116/0x1e0 [amdgpu]
Aug 18 20:25:49 archpad kernel: dcn20_fast_validate_bw+0x359/0x680 [amdgpu]
Aug 18 20:25:49 archpad kernel: ? resource_build_scaling_params+0xc44/0x11a0
[amdgpu]
Aug 18 20:25:49 archpad kernel: dcn21_validate_bandwidth+0xcd/0x2a0 [amdgpu]
Aug 18 20:25:49 archpad kernel: dc_validate_global_state+0x2f2/0x390 [amdgpu]
Aug 18 20:25:49 archpad kernel: amdgpu_dm_atomic_check+0xefb/0x1010 [amdgpu]
Aug 18 20:25:49 archpad kernel: drm_atomic_check_only+0x57c/0x7f0 [drm]
Aug 18 20:25:49 archpad kernel: ?
__drm_atomic_helper_crtc_duplicate_state+0x85/0xd0 [drm_kms_helper]
Aug 18 20:25:49 archpad kernel: drm_atomic_commit+0x13/0x50 [drm]
Aug 18 20:25:49 archpad kernel: drm_atomic_helper_legacy_gamma_set+0x123/0x180
[drm_kms_helper]
Aug 18 20:25:49 archpad kernel: drm_mode_gamma_set_ioctl+0x19a/0x230 [drm]
Aug 18 20:25:49 archpad kernel: ? drm_color_lut_check+0xa0/0xa0 [drm]
Aug 18 20:25:49 archpad kernel: drm_ioctl_kernel+0xb2/0x100 [drm]
Aug 18 20:25:49 archpad kernel: drm_ioctl+0x208/0x360 [drm]
Aug 18 20:25:49 archpad kernel: ? drm_color_lut_check+0xa0/0xa0 [drm]
Aug 18 20:25:49 archpad kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Aug 18 20:25:49 archpad kernel: ksys_ioctl+0x82/0xc0
Aug 18 20:25:49 archpad kernel: __x64_sys_ioctl+0x16/0x20
Aug 18 20:25:49 archpad kernel: do_syscall_64+0x44/0x70
Aug 18 20:25:49 archpad kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 18 20:25:49 archpad kernel: RIP: 0033:0x7f87887888eb
Aug 18
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #32 from Cyrax (ev...@hotmail.com) --- Fix is in stable 5.7.10 kernel. *** This bug has been marked as a duplicate of bug 207979 *** -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #31 from Alex Deucher (alexdeuc...@gmail.com) --- Duplicate of bug 207979. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #30 from Cyrax (ev...@hotmail.com) --- The patch in https://bugzilla.kernel.org/show_bug.cgi?id=207979 works beatifully. 19 days heavy usage without system crash on patched 5.7.6 kernel. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.7.0 |5.7.6 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Alexander Kernozhitsky (sh200...@mail.ru) changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #29 from Alexander Kernozhitsky (sh200...@mail.ru) --- I encountered this bug today. When running specific graphical applications, the machine hangs, and the kernel logs say about simd exception. It started to occur after the upgrade to 5.7.6 kernel. I tried to apply the patch mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=207979, and the patch resolves the issue for me. Using AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #28 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- @yaomtc Your bug seems to be some separate issue, as the log does not have the "simd exception" or "mode_support_and_system_configuration" entries in it. It looks more similar to this bug here: https://gitlab.freedesktop.org/drm/amd/-/issues/1149 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #27 from yao...@protonmail.com --- Created attachment 289535 --> https://bugzilla.kernel.org/attachment.cgi?id=289535=edit systemd journal from crash Update: got a whole system crash again when I was starting up SteamVR. So I guess the issue wasn't resolved for me. It could have reduced the likelihood maybe, or it was luck? Not sure what else to attach here, but I copied journal entries from the time of the crash (which happens at 21:09:31 near the end). Let me know if there's something else I should attach the next time this happens, if more data would be helpful. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #26 from Cyrax (ev...@hotmail.com) --- (In reply to Petteri Aimonen from comment #25) > Looks like there are two kinds of crash bugs here. Many of the amdgpu > crashes have been fixed in 5.7.0, but the specific one that gives "simd > exception" in dmesg is not. > > @Cyrax There is an experimental patch in > https://bugzilla.kernel.org/show_bug.cgi?id=207979 if you want to try. > > Out of interest, are you possibly running a 32-bit operating system under > virtualization on 64-bit host? That's what triggers the bug for me. I'm running one 32-bit LXC container (Arch Linux. https://archlinux32.org/>) and three 64-bit LXC containers (Arch Linux). Additionally I'm running three VirtualBox guests which are Windows, Arch Linux and old version LEDE (OpenWRT) router OS (All are running 64-bit OS). -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #25 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- Looks like there are two kinds of crash bugs here. Many of the amdgpu crashes have been fixed in 5.7.0, but the specific one that gives "simd exception" in dmesg is not. @Cyrax There is an experimental patch in https://bugzilla.kernel.org/show_bug.cgi?id=207979 if you want to try. Out of interest, are you possibly running a 32-bit operating system under virtualization on 64-bit host? That's what triggers the bug for me. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #24 from Cyrax (ev...@hotmail.com) --- (In reply to Petteri Aimonen from comment #16) > I hit the same issue, using Ubuntu 20.04. It happened when switching window > to Firefox. For me it only crashed Xorg, ssh to the machine still worked ok. > Killing Xorg didn't work and `shutdown -r now` hung up somewhere. > > Here is a bug report on the Ubuntu package: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881134 > > Here is call trace decoded with the debug symbols: > [clip] Yeah, it happens when switching windows and/or to different workspace. And yes it will crash Xorg only, other things will continue work as usual and issuing reboot command via SSH won't - well - reboot it. Only REISUB brings machine back to usable state. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #23 from Cyrax (ev...@hotmail.com) --- Created attachment 289483 --> https://bugzilla.kernel.org/attachment.cgi?id=289483=edit used decode_stacktrace.sh to previous dmesg log -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.7.0-rc3 |5.7.0 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #22 from Cyrax (ev...@hotmail.com) --- Created attachment 289481 --> https://bugzilla.kernel.org/attachment.cgi?id=289481=edit config file used to build kernel 5.7.0 with KASAN etc -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #21 from Cyrax (ev...@hotmail.com) --- Created attachment 289479 --> https://bugzilla.kernel.org/attachment.cgi?id=289479=edit dmesg output kernel 5.7.0 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 yao...@protonmail.com changed: What|Removed |Added CC||yao...@protonmail.com --- Comment #20 from yao...@protonmail.com --- So far so good Alex. Using the RX 5700 XT as well. Previously, running SteamVR could pretty quickly crash my system (even before launching a game), and since I rebuilt linux-mainline from AUR, haven't had SteamVR crash my system yet. Fingers crossed that this continues. Though Half-Life: Alyx is causing a system crash, which can even happen on Windows with Vulkan apparently! Wow. At least that's not an AMD or Linux specific issue. https://github.com/ValveSoftware/SteamVR-for-Linux/issues/356 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #19 from Alex Deucher (alexdeuc...@gmail.com) --- Do these patches help? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=59dfb0c64d3853d20dc84f4561f28d4f5a2ddc7d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa82e35cacfdff7278b7eeffd9575e9c386289e -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #18 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- As best as I can tell, the crash seems to be caused by some floating point exception (such as underflow/overflow) in this function call in dcn_calc_auto.c line 176: dcn_bw_ceil2(v->byte_per_pixel_in_dety[k], 1.0) In dcn_bw_ceil2() the exception occurs in this instruction: addsd 0x0(%rip),%xmm3 which is performing the addition flr + 0.1. At this point %xmm3 is ((int)(v->byte_per_pixel_in_dety[k] / 1.0)) * 1.0 The variable byte_per_pixel_in_dety is only assigned constant values 1.0, 2.0, 4.0, 8.0 so I don't see any reason for addsd to cause a simd exception. I'm not sure if the exception is precise or if it could be delayed from some prior instruction, but AFAIK it should be precise because in usermode the exception handler would attempt a recovery. Having XMM3 or MXCSR values would help, but they don't seem to get included in the dmesg output and I'm not sure if they are available in a crash dump either. Google search turned up https://beowulf.beowulf.narkive.com/tAHxVcs0/simd-exception-kernel-panic-on-skylake-ep-triggered-by-openfoam where the exception was delayed for some reason. Analyzing the dmesgs attached to this bug report, we have following crash locations: Cyrax2020-03-26 21:36: divss xmm0,DWORD PTR [r14+0x17f8] Cyrax2020-04-04 07:40: divss xmm0,DWORD PTR [r14+0x17f8] Cyrax2020-04-18 13:19: divss xmm0,DWORD PTR [r14+0x17f8] farmboy0 2020-04-19 11:43: not a simd exception Cyrax2020-04-23 05:15: divss xmm0,DWORD PTR [r14+0x17f8] Cyrax2020-04-27 19:20: divss xmm0,DWORD PTR [r14+0x17f8] Cyrax2020-05-02 14:18: divss xmm0,DWORD PTR [r14+0x17f8] PetteriA 2020-05-28 16:05: addsd xmm3,QWORD PTR [rip+0x1de967] So the crash locations appear fairly consistent for Cyrax's machine, but no two machines have the same location. For other users affected by this problem, it could be helpful if you install kernel debugging symbols and use decode_stacktrace.sh to convert the raw stack trace to code locations. Also reported on freedesktop amd bugtracker: https://gitlab.freedesktop.org/drm/amd/-/issues/1154 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #17 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- Created attachment 289381 --> https://bugzilla.kernel.org/attachment.cgi?id=289381=edit dmesg from kernel 5.4.0-31 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) changed: What|Removed |Added CC||j...@kernelbug.mail.kapsi.fi --- Comment #16 from Petteri Aimonen (j...@kernelbug.mail.kapsi.fi) --- I hit the same issue, using Ubuntu 20.04. It happened when switching window to Firefox. For me it only crashed Xorg, ssh to the machine still worked ok. Killing Xorg didn't work and `shutdown -r now` hung up somewhere. Here is a bug report on the Ubuntu package: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881134 Here is call trace decoded with the debug symbols: -- [455834.385061] Call Trace: [455834.385120] mode_support_and_system_configuration (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calc_auto.c:176) amdgpu [455834.385174] ? calculate_inits_and_adj_vp (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:950 (discriminator 12)) amdgpu [455834.385230] dcn_validate_bandwidth (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1034) amdgpu [455834.385283] dc_validate_global_state (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:2093) amdgpu [455834.385338] amdgpu_dm_atomic_check (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7413) amdgpu [455834.385351] drm_atomic_check_only (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1179) drm [455834.385361] drm_atomic_commit (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1220) drm [455834.385370] drm_mode_obj_set_property_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:496 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:533) drm [455834.385379] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385386] drm_ioctl_kernel (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:793) drm [455834.385394] drm_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:119 /build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:152 /build/linux-FFoizL/linux-5.4.0/include/linux/uaccess.h:151 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:888) drm [455834.385402] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385406] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385440] amdgpu_drm_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1293) amdgpu [455834.385443] do_vfs_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:47 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:510 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:697) [455834.385444] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385446] ? _copy_from_user (/build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:46 /build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:71 /build/linux-FFoizL/linux-5.4.0/lib/usercopy.c:14) [455834.385448] ksys_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/file.h:43 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:715) [455834.385449] __x64_sys_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:719) [455834.385451] do_syscall_64 (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/common.c:290) [455834.385455] entry_SYSCALL_64_after_hwframe (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/entry_64.S:184) [455834.385456] RIP: 0033:0x7faf3181837b -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #15 from Cyrax (ev...@hotmail.com) --- Created attachment 289241 --> https://bugzilla.kernel.org/attachment.cgi?id=289241=edit dump of struct dcn_bw_internal_vars -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #14 from Cyrax (ev...@hotmail.com) --- Created attachment 289239 --> https://bugzilla.kernel.org/attachment.cgi?id=289239=edit backtrace created by executing bt -f command in crash utility -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #13 from Cyrax (ev...@hotmail.com) --- Created attachment 289237 --> https://bugzilla.kernel.org/attachment.cgi?id=289237=edit kernel log dumped from crash dump by using crash utility -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #12 from Cyrax (ev...@hotmail.com) --- Created attachment 288873 --> https://bugzilla.kernel.org/attachment.cgi?id=288873=edit dmesg from 5.6.8 Additionally dmesg output shows this line : note: kworker/0:3[2251663] exited with preempt_count 1 It seems that this bug occurs when the monitor is turned off and then on repeatedly with short delay between. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.6.7 |5.7.0-rc3 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #11 from Cyrax (ev...@hotmail.com) --- Created attachment 288781 --> https://bugzilla.kernel.org/attachment.cgi?id=288781=edit dmesg output from Linux 5.7-rc3 This is starting to be real problem, I can't do anything remotely productive. Crash will happen in just 12 hours (give or take) when system is rebooted from previous one. I'm running four LXC containers which I have setup to run GUI programs in hosts system by following this help : https://wiki.archlinux.org/index.php/Linux_Containers#Xorg_program_considerations_(optional) Also I have running VirtualBox but its VM's aren't accessing 3D functions from host at all. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.6.5 |5.6.7 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #10 from Cyrax (ev...@hotmail.com) --- Created attachment 288719 --> https://bugzilla.kernel.org/attachment.cgi?id=288719=edit gdb disassembler dump around mode_support_and_system_configuration And it happened again. Looks like that something goes wrong after while when computer monitor is turned on. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #9 from Cyrax (ev...@hotmail.com) --- Created attachment 288679 --> https://bugzilla.kernel.org/attachment.cgi?id=288679=edit dmesg output And again. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.6.4 |5.6.5 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #8 from farmb...@googlemail.com --- Created attachment 288615 --> https://bugzilla.kernel.org/attachment.cgi?id=288615=edit smesg output -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 farmb...@googlemail.com changed: What|Removed |Added CC||farmb...@googlemail.com --- Comment #7 from farmb...@googlemail.com --- I am having the same problem sometimes during start/exit of SteamVR. I have observed with the 5.6 kernels. My card is a Navi RX 5700XT. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #6 from Cyrax (ev...@hotmail.com) --- Created attachment 288595 --> https://bugzilla.kernel.org/attachment.cgi?id=288595=edit dmesg output And another one. It seems that switching between virtual consoles causes this bug to happen -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.5.13 |5.6.4 -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #5 from Cyrax (ev...@hotmail.com) --- Oh and kernel is in 5.5.13 version. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Cyrax (ev...@hotmail.com) changed: What|Removed |Added Kernel Version|5.5.11 |5.5.13 Regression|No |Yes -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #4 from Cyrax (ev...@hotmail.com) --- Created attachment 288203 --> https://bugzilla.kernel.org/attachment.cgi?id=288203=edit dmesg output 2 This crash happened again. In that time I have used VLC, played a game (GZDoom) and tried to listen youtube playlist by using a combination of youtube-dl, ffmpeg and mpv. I also updated motherboards BIOS/firmware to latest one. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #3 from Cyrax (ev...@hotmail.com) --- GCC is "gcc (Arch Linux 9.3.0-1) 9.3.0" -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 --- Comment #2 from Cyrax (ev...@hotmail.com) --- Created attachment 288079 --> https://bugzilla.kernel.org/attachment.cgi?id=288079=edit dmesg output -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
https://bugzilla.kernel.org/show_bug.cgi?id=206987 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #1 from Alex Deucher (alexdeuc...@gmail.com) --- Please attach your full dmesg output. What version of gcc are you using? -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
