From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" at amdgpu_vm_cpu_set_ptes at S3 resume Date: Fri, 29 Jun 2018 16:16:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0190229029==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 63B096F0F8 for ; Fri, 29 Jun 2018 16:16:37 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0190229029== Content-Type: multipart/alternative; boundary="15302889971.fAFC5.31843" Content-Transfer-Encoding: 7bit --15302889971.fAFC5.31843 Date: Fri, 29 Jun 2018 16:16:37 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107065 --- Comment #6 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=3Damd-staging-drm-next#n921 with the same backtrace with > vm_update_mode=3D3 immediately upon starting X11 - not only after S3 resu= me. > Here with symbols translated to source lines: >=20 > 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)=20 > 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)=20 > Jun 29 01:49:05 ryzen kernel: ? handle_mm_fault (/mm/memory.c:4133)=20 > Jun 29 01:49:05 ryzen kernel: ksys_ioctl (/./include/linux/file.h:39 > /fs/ioctl.c:702)=20 > Jun 29 01:49:05 ryzen kernel: __x64_sys_ioctl (/fs/ioctl.c:708 > /fs/ioctl.c:706 /fs/ioctl.c:706)=20 > Jun 29 01:49:05 ryzen kernel: do_syscall_64 (/arch/x86/entry/common.c:290= )=20 > 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 ? --=20 You are receiving this mail because: You are the assignee for the bug.= --15302889971.fAFC5.31843 Date: Fri, 29 Jun 2018 16:16:37 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 6 on bug 10706= 5 from Andrey Grodzovsky 
(In reply to dwagner from comment #5)
> Interesting: With amd-staging-drm-next, I see th=
e same crash at
> https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu=
/drm/amd/amdgpu/
> amdgpu_vm.c?h=3Damd-staging-drm-next#n921 with the same backtrace with
> vm_update_mode=3D3 immediately upon starting X11 - not only after S3 r=
esume.
> Here with symbols translated to source lines:
>=20
> 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)=20
> 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)=20
> Jun 29 01:49:05 ryzen kernel: ? handle_mm_fault (/mm/memory.c:4133)=20
> Jun 29 01:49:05 ryzen kernel: ksys_ioctl (/./include/linux/file.h:39
> /fs/ioctl.c:702)=20
> Jun 29 01:49:05 ryzen kernel: __x64_sys_ioctl (/fs/ioctl.c:708
> /fs/ioctl.c:706 /fs/ioctl.c:706)=20
> Jun 29 01:49:05 ryzen kernel: do_syscall_64 (/arch/x86/entry/common.c:=
290)=20
> Jun 29 01:49:05 ryzen kernel: entry_SYSCALL_64_after_hwframe
> (/./include/trace/events/initcall.h:10 /./include/trace/events/initcal=
l.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.
= --15302889971.fAFC5.31843-- --===============0190229029== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0190229029==--