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: Thu, 28 Jun 2018 19:33:52 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0451568602==" 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 23A806EE67 for ; Thu, 28 Jun 2018 19:33:53 +0000 (UTC) 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 --===============0451568602== Content-Type: multipart/alternative; boundary="15302144330.5423aF1.18534" Content-Transfer-Encoding: 7bit --15302144330.5423aF1.18534 Date: Thu, 28 Jun 2018 19:33:53 +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 Bug ID: 107065 Summary: "BUG: unable to handle kernel paging request at 0000000000002000" at amdgpu_vm_cpu_set_ptes at S3 resume Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: jb5sgc1n.nya@20mm.eu When I resume from S3 using the 4.17.2-1-ARCH kernel, with amdgpu.vm_update_mode=3D3 (for reasons explained in https://bugs.freedesktop.org/show_bug.cgi?id=3D102322 ) first the amdgpu dr= iver and shortly thereafter the system crashes with the following kernel message= s: Jun 28 21:14:25 ryzen kernel: ACPI: Low-level resume complete Jun 28 21:14:25 ryzen kernel: PM: Restoring platform NVS memory Jun 28 21:14:25 ryzen kernel: Enabling non-boot CPUs ... ... Jun 28 21:14:25 ryzen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400040000). Jun 28 21:14:25 ryzen kernel: [drm] UVD and UVD ENC initialized successfull= y. Jun 28 21:14:25 ryzen kernel: [drm] VCE initialized successfully. Jun 28 21:14:25 ryzen kernel: OOM killer enabled. Jun 28 21:14:25 ryzen kernel: Restarting tasks ... done. Jun 28 21:14:25 ryzen kernel: PM: suspend exit Jun 28 21:14:25 ryzen kernel: BUG: unable to handle kernel paging request at 0000000000002000 Jun 28 21:14:25 ryzen kernel: PGD 0 P4D 0=20 Jun 28 21:14:25 ryzen kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI Jun 28 21:14:25 ryzen kernel: Modules linked in: arc4 md4 sha512_ssse3 sha512_generic nls_utf8 cifs ccm dns_resolver fscache> Jun 28 21:14:25 ryzen kernel: bluetooth snd_hwdep snd_pcm eeepc_wmi snd_ti= mer asus_wmi snd sparse_keymap mxm_wmi wmi_bmof i> Jun 28 21:14:25 ryzen kernel: dm_crypt dm_mod i2c_dev Jun 28 21:14:25 ryzen kernel: CPU: 3 PID: 882 Comm: amdgpu_cs:0 Tainted: G= =20=20=20=20=20 W O 4.17.2-1-ARCH #1 Jun 28 21:14:25 ryzen kernel: Hardware name: System manufacturer System Pro= duct Name/PRIME X370-PRO, BIOS 4011 04/19/2018 Jun 28 21:14:25 ryzen kernel: RIP: 0010:gmc_v8_0_set_pte_pde+0x1b/0x30 [amd= gpu] Jun 28 21:14:25 ryzen kernel: RSP: 0018:ffffb8b8c3fa7a70 EFLAGS: 00010202 Jun 28 21:14:25 ryzen kernel: RAX: 000000fffffff000 RBX: 0000000000000001 R= CX: 000000f400956001 Jun 28 21:14:25 ryzen kernel: RDX: 0000000000002000 RSI: 0000000000002000 R= DI: ffff9edab48a0000 Jun 28 21:14:25 ryzen kernel: RBP: 0000000000000000 R08: 0000000000000001 R= 09: 0000000000000000 Jun 28 21:14:25 ryzen kernel: R10: ffffffffc03e4c50 R11: ffff9edab30d0800 R= 12: 0000000000002000 Jun 28 21:14:25 ryzen kernel: R13: 0000000000000001 R14: ffffb8b8c3fa7ae8 R= 15: 000000f400956000 Jun 28 21:14:25 ryzen kernel: FS: 00007f622bb59700(0000) GS:ffff9edadecc0000(0000) knlGS:0000000000000000 Jun 28 21:14:25 ryzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005= 0033 Jun 28 21:14:25 ryzen kernel: CR2: 0000000000002000 CR3: 00000007e03f8000 C= R4: 00000000003406e0 Jun 28 21:14:25 ryzen kernel: Call Trace: Jun 28 21:14:25 ryzen kernel: amdgpu_vm_cpu_set_ptes+0x76/0xf0 [amdgpu] Jun 28 21:14:25 ryzen kernel: amdgpu_vm_update_directories+0x1ca/0x3c0 [amdgpu] Jun 28 21:14:25 ryzen kernel: ? amdgpu_vm_do_copy_ptes+0xc0/0xc0 [amdgpu] Jun 28 21:14:25 ryzen kernel: amdgpu_cs_ioctl+0x1169/0x1a70 [amdgpu] Jun 28 21:14:25 ryzen kernel: ? dequeue_entity+0x156/0x950 Jun 28 21:14:25 ryzen kernel: ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu] Jun 28 21:14:25 ryzen kernel: drm_ioctl_kernel+0x5b/0xb0 [drm] Jun 28 21:14:25 ryzen kernel: drm_ioctl+0x1b7/0x370 [drm] Jun 28 21:14:25 ryzen kernel: ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu] Jun 28 21:14:25 ryzen kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Jun 28 21:14:25 ryzen kernel: do_vfs_ioctl+0xa4/0x610 Jun 28 21:14:25 ryzen kernel: ksys_ioctl+0x60/0x90 Jun 28 21:14:25 ryzen kernel: __x64_sys_ioctl+0x16/0x20 Jun 28 21:14:25 ryzen kernel: do_syscall_64+0x5b/0x170 Jun 28 21:14:25 ryzen kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 28 21:14:25 ryzen kernel: RIP: 0033:0x7f623b586667 Jun 28 21:14:25 ryzen kernel: RSP: 002b:00007f622bb58a98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Jun 28 21:14:25 ryzen kernel: RAX: ffffffffffffffda RBX: 00007f622bb58b88 R= CX: 00007f623b586667 Jun 28 21:14:25 ryzen kernel: RDX: 00007f622bb58b00 RSI: 00000000c0186444 R= DI: 000000000000000b Jun 28 21:14:25 ryzen kernel: RBP: 00007f622bb58b00 R08: 00007f622bb58bb0 R= 09: 0000000000000010 Jun 28 21:14:25 ryzen kernel: R10: 00007f622bb58bb0 R11: 0000000000000246 R= 12: 00000000c0186444 Jun 28 21:14:25 ryzen kernel: R13: 000000000000000b R14: 000000000000000a R= 15: 0000000000000000 Jun 28 21:14:25 ryzen kernel: Code: 8b 80 d8 00 00 00 e9 85 ed 5c c2 0f 1f = 44 00 00 0f 1f 44 00 00 48 b8 00 f0 ff ff ff 00 0> Jun 28 21:14:25 ryzen kernel: RIP: gmc_v8_0_set_pte_pde+0x1b/0x30 [amdgpu] = RSP: ffffb8b8c3fa7a70 Jun 28 21:14:25 ryzen kernel: CR2: 0000000000002000 Jun 28 21:14:25 ryzen kernel: ---[ end trace 6fce4be2faa5be7e ]--- --=20 You are receiving this mail because: You are the assignee for the bug.= --15302144330.5423aF1.18534 Date: Thu, 28 Jun 2018 19:33:53 +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
Bug ID 107065
Summary "BUG: unable to handle kernel paging request at 00000000= 00002000" at amdgpu_vm_cpu_set_ptes at S3 resume
Product DRI
Version DRI git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity major
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter jb5sgc1n.nya@20mm.eu

When I resume from S3 using the 4.17.2-1-ARCH kernel, with
amdgpu.vm_update_mode=3D3 (for reasons explained in
https://bugs.freedesktop.org/show_bug.=
cgi?id=3D102322 ) first the amdgpu driver
and shortly thereafter the system crashes with the following kernel message=
s:

Jun 28 21:14:25 ryzen kernel: ACPI: Low-level resume complete
Jun 28 21:14:25 ryzen kernel: PM: Restoring platform NVS memory
Jun 28 21:14:25 ryzen kernel: Enabling non-boot CPUs ...
...
Jun 28 21:14:25 ryzen kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400040000).
Jun 28 21:14:25 ryzen kernel: [drm] UVD and UVD ENC initialized successfull=
y.
Jun 28 21:14:25 ryzen kernel: [drm] VCE initialized successfully.
Jun 28 21:14:25 ryzen kernel: OOM killer enabled.
Jun 28 21:14:25 ryzen kernel: Restarting tasks ... done.
Jun 28 21:14:25 ryzen kernel: PM: suspend exit
Jun 28 21:14:25 ryzen kernel: BUG: unable to handle kernel paging request at
0000000000002000
Jun 28 21:14:25 ryzen kernel: PGD 0 P4D 0=20
Jun 28 21:14:25 ryzen kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Jun 28 21:14:25 ryzen kernel: Modules linked in: arc4 md4 sha512_ssse3
sha512_generic nls_utf8 cifs ccm dns_resolver fscache>
Jun 28 21:14:25 ryzen kernel:  bluetooth snd_hwdep snd_pcm eeepc_wmi snd_ti=
mer
asus_wmi snd sparse_keymap mxm_wmi wmi_bmof i>
Jun 28 21:14:25 ryzen kernel:  dm_crypt dm_mod i2c_dev
Jun 28 21:14:25 ryzen kernel: CPU: 3 PID: 882 Comm: amdgpu_cs:0 Tainted: G=
=20=20=20=20=20
  W  O      4.17.2-1-ARCH #1
Jun 28 21:14:25 ryzen kernel: Hardware name: System manufacturer System Pro=
duct
Name/PRIME X370-PRO, BIOS 4011 04/19/2018
Jun 28 21:14:25 ryzen kernel: RIP: 0010:gmc_v8_0_set_pte_pde+0x1b/0x30 [amd=
gpu]
Jun 28 21:14:25 ryzen kernel: RSP: 0018:ffffb8b8c3fa7a70 EFLAGS: 00010202
Jun 28 21:14:25 ryzen kernel: RAX: 000000fffffff000 RBX: 0000000000000001 R=
CX:
000000f400956001
Jun 28 21:14:25 ryzen kernel: RDX: 0000000000002000 RSI: 0000000000002000 R=
DI:
ffff9edab48a0000
Jun 28 21:14:25 ryzen kernel: RBP: 0000000000000000 R08: 0000000000000001 R=
09:
0000000000000000
Jun 28 21:14:25 ryzen kernel: R10: ffffffffc03e4c50 R11: ffff9edab30d0800 R=
12:
0000000000002000
Jun 28 21:14:25 ryzen kernel: R13: 0000000000000001 R14: ffffb8b8c3fa7ae8 R=
15:
000000f400956000
Jun 28 21:14:25 ryzen kernel: FS:  00007f622bb59700(0000)
GS:ffff9edadecc0000(0000) knlGS:0000000000000000
Jun 28 21:14:25 ryzen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005=
0033
Jun 28 21:14:25 ryzen kernel: CR2: 0000000000002000 CR3: 00000007e03f8000 C=
R4:
00000000003406e0
Jun 28 21:14:25 ryzen kernel: Call Trace:
Jun 28 21:14:25 ryzen kernel:  amdgpu_vm_cpu_set_ptes+0x76/0xf0 [amdgpu]
Jun 28 21:14:25 ryzen kernel:  amdgpu_vm_update_directories+0x1ca/0x3c0
[amdgpu]
Jun 28 21:14:25 ryzen kernel:  ? amdgpu_vm_do_copy_ptes+0xc0/0xc0 [amdgpu]
Jun 28 21:14:25 ryzen kernel:  amdgpu_cs_ioctl+0x1169/0x1a70 [amdgpu]
Jun 28 21:14:25 ryzen kernel:  ? dequeue_entity+0x156/0x950
Jun 28 21:14:25 ryzen kernel:  ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu]
Jun 28 21:14:25 ryzen kernel:  drm_ioctl_kernel+0x5b/0xb0 [drm]
Jun 28 21:14:25 ryzen kernel:  drm_ioctl+0x1b7/0x370 [drm]
Jun 28 21:14:25 ryzen kernel:  ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu]
Jun 28 21:14:25 ryzen kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Jun 28 21:14:25 ryzen kernel:  do_vfs_ioctl+0xa4/0x610
Jun 28 21:14:25 ryzen kernel:  ksys_ioctl+0x60/0x90
Jun 28 21:14:25 ryzen kernel:  __x64_sys_ioctl+0x16/0x20
Jun 28 21:14:25 ryzen kernel:  do_syscall_64+0x5b/0x170
Jun 28 21:14:25 ryzen kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 28 21:14:25 ryzen kernel: RIP: 0033:0x7f623b586667
Jun 28 21:14:25 ryzen kernel: RSP: 002b:00007f622bb58a98 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
Jun 28 21:14:25 ryzen kernel: RAX: ffffffffffffffda RBX: 00007f622bb58b88 R=
CX:
00007f623b586667
Jun 28 21:14:25 ryzen kernel: RDX: 00007f622bb58b00 RSI: 00000000c0186444 R=
DI:
000000000000000b
Jun 28 21:14:25 ryzen kernel: RBP: 00007f622bb58b00 R08: 00007f622bb58bb0 R=
09:
0000000000000010
Jun 28 21:14:25 ryzen kernel: R10: 00007f622bb58bb0 R11: 0000000000000246 R=
12:
00000000c0186444
Jun 28 21:14:25 ryzen kernel: R13: 000000000000000b R14: 000000000000000a R=
15:
0000000000000000
Jun 28 21:14:25 ryzen kernel: Code: 8b 80 d8 00 00 00 e9 85 ed 5c c2 0f 1f =
44
00 00 0f 1f 44 00 00 48 b8 00 f0 ff ff ff 00 0>
Jun 28 21:14:25 ryzen kernel: RIP: gmc_v8_0_set_pte_pde+0x1b/0x30 [amdgpu] =
RSP:
ffffb8b8c3fa7a70
Jun 28 21:14:25 ryzen kernel: CR2: 0000000000002000
Jun 28 21:14:25 ryzen kernel: ---[ end trace 6fce4be2faa5be7e ]---


You are receiving this mail because:
  • You are the assignee for the bug.
= --15302144330.5423aF1.18534-- --===============0451568602== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0451568602==--