dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 22:50:19 +0000	[thread overview]
Message-ID: <bug-107065-502-0PV3qJnPR9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107065-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 4772 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107065

--- Comment #4 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Andrey Grodzovsky from comment #3)
> Can you use addr2line or gdb with 'list' command to give the line number
> matching
> amdgpu_vm_cpu_set_ptes+0x76/0xf0 ?

That would have been easy had I used my self-compiled kernel - but it seems
there is no debuginfo file available for the Arch Linux supplied kernels, which
I ran in this case.

So I can only provide a disassembled listing of that function, with offset 0x76
aka +118 inside:

Dump of assembler code for function amdgpu_vm_cpu_set_ptes:
   0x0000000000027c80 <+0>:     callq  0x27c85 <amdgpu_vm_cpu_set_ptes+5>
   0x0000000000027c85 <+5>:     push   %r15
   0x0000000000027c87 <+7>:     mov    %rcx,%r15
   0x0000000000027c8a <+10>:    push   %r14
   0x0000000000027c8c <+12>:    mov    %rdi,%r14
   0x0000000000027c8f <+15>:    mov    %rsi,%rdi
   0x0000000000027c92 <+18>:    push   %r13
   0x0000000000027c94 <+20>:    mov    %r8d,%r13d
   0x0000000000027c97 <+23>:    push   %r12
   0x0000000000027c99 <+25>:    mov    %rdx,%r12
   0x0000000000027c9c <+28>:    push   %rbp
   0x0000000000027c9d <+29>:    mov    %r9d,%ebp
   0x0000000000027ca0 <+32>:    push   %rbx
   0x0000000000027ca1 <+33>:    callq  0x27ca6 <amdgpu_vm_cpu_set_ptes+38>
   0x0000000000027ca6 <+38>:    add    %rax,%r12
   0x0000000000027ca9 <+41>:    nopl   0x0(%rax,%rax,1)
   0x0000000000027cae <+46>:    xor    %ebx,%ebx
   0x0000000000027cb0 <+48>:    test   %r13d,%r13d
   0x0000000000027cb3 <+51>:    je     0x27cfb <amdgpu_vm_cpu_set_ptes+123>
   0x0000000000027cb5 <+53>:    mov    0x28(%r14),%rax
   0x0000000000027cb9 <+57>:    mov    %r15,%rcx
   0x0000000000027cbc <+60>:    test   %rax,%rax
   0x0000000000027cbf <+63>:    je     0x27cd3 <amdgpu_vm_cpu_set_ptes+83>
   0x0000000000027cc1 <+65>:    mov    %r15,%rdx
   0x0000000000027cc4 <+68>:    mov    $0xfffffffffffff000,%rcx
   0x0000000000027ccb <+75>:    shr    $0xc,%rdx
   0x0000000000027ccf <+79>:    and    (%rax,%rdx,8),%rcx
   0x0000000000027cd3 <+83>:    mov    (%r14),%rdi
   0x0000000000027cd6 <+86>:    mov    %ebx,%edx
   0x0000000000027cd8 <+88>:    add    $0x1,%ebx
   0x0000000000027cdb <+91>:    mov    0x38(%rsp),%r8
   0x0000000000027ce0 <+96>:    mov    %r12,%rsi
   0x0000000000027ce3 <+99>:    add    %rbp,%r15
   0x0000000000027ce6 <+102>:   mov    0x968(%rdi),%rax
   0x0000000000027ced <+109>:   mov    0x18(%rax),%rax
   0x0000000000027cf1 <+113>:   callq  0x27cf6 <amdgpu_vm_cpu_set_ptes+118>
   0x0000000000027cf6 <+118>:   cmp    %ebx,%r13d
   0x0000000000027cf9 <+121>:   jne    0x27cb5 <amdgpu_vm_cpu_set_ptes+53>
   0x0000000000027cfb <+123>:   pop    %rbx
   0x0000000000027cfc <+124>:   pop    %rbp
   0x0000000000027cfd <+125>:   pop    %r12
   0x0000000000027cff <+127>:   pop    %r13
   0x0000000000027d01 <+129>:   pop    %r14
   0x0000000000027d03 <+131>:   pop    %r15
   0x0000000000027d05 <+133>:   retq   
   0x0000000000027d06 <+134>:   mov    %gs:0x0(%rip),%eax        # 0x27d0d
<amdgpu_vm_cpu_set_ptes+141>
   0x0000000000027d0d <+141>:   mov    %eax,%eax
   0x0000000000027d0f <+143>:   bt     %rax,0x0(%rip)        # 0x27d17
<amdgpu_vm_cpu_set_ptes+151>
   0x0000000000027d17 <+151>:   jae    0x27cae <amdgpu_vm_cpu_set_ptes+46>
   0x0000000000027d19 <+153>:   incl   %gs:0x0(%rip)        # 0x27d20
<amdgpu_vm_cpu_set_ptes+160>
   0x0000000000027d20 <+160>:   mov    0x0(%rip),%rbx        # 0x27d27
<amdgpu_vm_cpu_set_ptes+167>
   0x0000000000027d27 <+167>:   test   %rbx,%rbx
   0x0000000000027d2a <+170>:   je     0x27d55 <amdgpu_vm_cpu_set_ptes+213>
   0x0000000000027d2c <+172>:   mov    (%rbx),%rax
   0x0000000000027d2f <+175>:   mov    0x8(%rbx),%rdi
   0x0000000000027d33 <+179>:   add    $0x18,%rbx
   0x0000000000027d37 <+183>:   mov    0x38(%rsp),%r9
   0x0000000000027d3c <+188>:   mov    %ebp,%r8d
   0x0000000000027d3f <+191>:   mov    %r13d,%ecx
   0x0000000000027d42 <+194>:   mov    %r15,%rdx
   0x0000000000027d45 <+197>:   mov    %r12,%rsi
   0x0000000000027d48 <+200>:   callq  0x27d4d <amdgpu_vm_cpu_set_ptes+205>
   0x0000000000027d4d <+205>:   mov    (%rbx),%rax
   0x0000000000027d50 <+208>:   test   %rax,%rax
   0x0000000000027d53 <+211>:   jne    0x27d2f <amdgpu_vm_cpu_set_ptes+175>
   0x0000000000027d55 <+213>:   decl   %gs:0x0(%rip)        # 0x27d5c
<amdgpu_vm_cpu_set_ptes+220>
   0x0000000000027d5c <+220>:   jne    0x27cae <amdgpu_vm_cpu_set_ptes+46>
   0x0000000000027d62 <+226>:   callq  0x27d67 <amdgpu_vm_cpu_set_ptes+231>
   0x0000000000027d67 <+231>:   jmpq   0x27cae <amdgpu_vm_cpu_set_ptes+46>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 6280 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-28 22:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 19:33 [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" at amdgpu_vm_cpu_set_ptes at S3 resume bugzilla-daemon
2018-06-28 19:42 ` bugzilla-daemon
2018-06-28 19:52 ` bugzilla-daemon
2018-06-28 20:49 ` bugzilla-daemon
2018-06-28 22:50 ` bugzilla-daemon [this message]
2018-06-29  0:37 ` bugzilla-daemon
2018-06-29 16:16 ` bugzilla-daemon
2018-06-29 19:10 ` bugzilla-daemon
2018-06-29 19:10 ` [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921 bugzilla-daemon
2018-06-29 19:17 ` bugzilla-daemon
2018-06-29 19:21 ` bugzilla-daemon
2018-07-02  3:11 ` bugzilla-daemon
2018-07-02 11:03 ` bugzilla-daemon
2018-07-02 19:48 ` bugzilla-daemon
2018-07-02 22:55 ` bugzilla-daemon
2018-07-03 20:42 ` bugzilla-daemon
2018-07-03 22:58 ` bugzilla-daemon
2018-07-04 22:55 ` bugzilla-daemon
2018-07-06 23:03 ` bugzilla-daemon
2018-07-09 18:16 ` bugzilla-daemon
2018-07-11 22:04 ` bugzilla-daemon
2018-07-11 22:23 ` bugzilla-daemon
2018-07-13 21:01 ` bugzilla-daemon
2018-07-13 23:45 ` bugzilla-daemon
2018-07-14  4:28 ` bugzilla-daemon
2018-07-14 13:15 ` bugzilla-daemon
2018-07-14 13:16 ` bugzilla-daemon
2018-07-16 13:52 ` bugzilla-daemon
2018-07-19 16:42 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107065-502-0PV3qJnPR9@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox