Comment # 6
on bug 107065
from Andrey Grodzovsky
(In reply to dwagner from comment #5) > Interesting: With amd-staging-drm-next, I see the same crash at > https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/amd/amdgpu/ > amdgpu_vm.c?h=amd-staging-drm-next#n921 with the same backtrace with > vm_update_mode=3 immediately upon starting X11 - not only after S3 resume. > Here with symbols translated to source lines: > > Jun 29 01:49:05 ryzen kernel: amdgpu_vm_cpu_set_ptes > (/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:921 (discriminator 2)) amdgpu > Jun 29 01:49:05 ryzen kernel: amdgpu_vm_update_directories > (/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:989 > /drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1096) amdgpu > Jun 29 01:49:05 ryzen kernel: ? amdgpu_vm_do_copy_ptes > (/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:913) amdgpu > Jun 29 01:49:05 ryzen kernel: amdgpu_gem_va_ioctl > (/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:542 > /drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:674) amdgpu > Jun 29 01:49:05 ryzen kernel: ? __alloc_pages_nodemask > (/mm/page_alloc.c:4355) > Jun 29 01:49:05 ryzen kernel: ? amdgpu_gem_metadata_ioctl > (/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:548) amdgpu > Jun 29 01:49:05 ryzen kernel: drm_ioctl_kernel+0xa7/0xf0 drm > Jun 29 01:49:05 ryzen kernel: drm_ioctl+0x2f1/0x3c0 drm > Jun 29 01:49:05 ryzen kernel: ? amdgpu_gem_metadata_ioctl > (/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:548) amdgpu > Jun 29 01:49:05 ryzen kernel: amdgpu_drm_ioctl > (/./include/linux/pm_runtime.h:108 > /drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:842) amdgpu > Jun 29 01:49:05 ryzen kernel: do_vfs_ioctl (/fs/ioctl.c:46 /fs/ioctl.c:500 > /fs/ioctl.c:684) > Jun 29 01:49:05 ryzen kernel: ? handle_mm_fault (/mm/memory.c:4133) > Jun 29 01:49:05 ryzen kernel: ksys_ioctl (/./include/linux/file.h:39 > /fs/ioctl.c:702) > Jun 29 01:49:05 ryzen kernel: __x64_sys_ioctl (/fs/ioctl.c:708 > /fs/ioctl.c:706 /fs/ioctl.c:706) > Jun 29 01:49:05 ryzen kernel: do_syscall_64 (/arch/x86/entry/common.c:290) > Jun 29 01:49:05 ryzen kernel: entry_SYSCALL_64_after_hwframe > (/./include/trace/events/initcall.h:10 /./include/trace/events/initcall.h:10) So with Arch Linux kernel it happens only during S3 but with amd-staging-drm-next it happens once you start X ?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
