[Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=206987

--- Comment #37 from krakopo at protonmail.com ---
I do see ldmxcsr in the disassembly:

ffffffff81038870 <kernel_fpu_begin>:
ffffffff81038870:       e8 9b 07 03 00          callq  ffffffff81069010
<__fentry__>
ffffffff81038875:       48 83 ec 10             sub    $0x10,%rsp
ffffffff81038879:       bf 01 00 00 00          mov    $0x1,%edi
ffffffff8103887e:       65 48 8b 04 25 28 00    mov    %gs:0x28,%rax
ffffffff81038885:       00 00 
ffffffff81038887:       48 89 44 24 08          mov    %rax,0x8(%rsp)
ffffffff8103888c:       31 c0                   xor    %eax,%eax
ffffffff8103888e:       c7 44 24 04 00 00 00    movl   $0x0,0x4(%rsp)
ffffffff81038895:       00 
ffffffff81038896:       e8 35 ae 08 00          callq  ffffffff810c36d0
<preempt_count_add>
ffffffff8103889b:       e8 80 fd ff ff          callq  ffffffff81038620
<irq_fpu_usable>
ffffffff810388a0:       65 8a 05 b1 f2 fd 7e    mov    %gs:0x7efdf2b1(%rip),%al
       # 17b58 <in_kernel_fpu>
ffffffff810388a7:       65 c6 05 a9 f2 fd 7e    movb  
$0x1,%gs:0x7efdf2a9(%rip)        # 17b58 <in_kernel_fpu>
ffffffff810388ae:       01 
ffffffff810388af:       65 48 8b 3c 25 c0 7b    mov    %gs:0x17bc0,%rdi
ffffffff810388b6:       01 00 
ffffffff810388b8:       f6 47 26 20             testb  $0x20,0x26(%rdi)
ffffffff810388bc:       74 3c                   je     ffffffff810388fa
<kernel_fpu_begin+0x8a>
ffffffff810388be:       48 c7 c7 57 43 40 82    mov    $0xffffffff82404357,%rdi
ffffffff810388c5:       e8 46 41 9c 00          callq  ffffffff819fca10
<__this_cpu_preempt_check>
ffffffff810388ca:       c7 44 24 04 80 1f 00    movl   $0x1f80,0x4(%rsp)
ffffffff810388d1:       00 
ffffffff810388d2:       65 48 c7 05 82 f2 fd    movq  
$0x0,%gs:0x7efdf282(%rip)        # 17b60 <fpu_fpregs_owner_ctx>
ffffffff810388d9:       7e 00 00 00 00 
ffffffff810388de:       0f ae 54 24 04          ldmxcsr 0x4(%rsp)
ffffffff810388e3:       db e3                   fninit 
ffffffff810388e5:       48 8b 44 24 08          mov    0x8(%rsp),%rax
ffffffff810388ea:       65 48 2b 04 25 28 00    sub    %gs:0x28,%rax
ffffffff810388f1:       00 00 
ffffffff810388f3:       75 20                   jne    ffffffff81038915
<kernel_fpu_begin+0xa5>
ffffffff810388f5:       48 83 c4 10             add    $0x10,%rsp
ffffffff810388f9:       c3                      retq   
ffffffff810388fa:       48 8b 07                mov    (%rdi),%rax
ffffffff810388fd:       f6 c4 40                test   $0x40,%ah
ffffffff81038900:       75 bc                   jne    ffffffff810388be
<kernel_fpu_begin+0x4e>
ffffffff81038902:       f0 80 4f 01 40          lock orb $0x40,0x1(%rdi)
ffffffff81038907:       48 81 c7 00 1b 00 00    add    $0x1b00,%rdi
ffffffff8103890e:       e8 5d fd ff ff          callq  ffffffff81038670
<copy_fpregs_to_fpstate>
ffffffff81038913:       eb a9                   jmp    ffffffff810388be
<kernel_fpu_begin+0x4e>
ffffffff81038915:       e8 36 3c 9c 00          callq  ffffffff819fc550
<__stack_chk_fail>
ffffffff8103891a:       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.