Why is the kernel panicking?

Question

linux

The computer was with the screen locked for about 4 hours. Then I turned off the computer through the Mint menu, while the applications (messengers, chrome, ide) remained open.

When I gave such an error, it started without problems.


A Google search suggested a problem with the file system, but everything is ok with it.
What can be wrong?

Answer 1

Why is the kernel panicking

immediate cause: init died (attempted to kill init in the first line), due to a signal (do_signal in the call stack).
Fallen code:

$ echo 'Code: 0f 7f 44 17 f0 f3 0f 7f 07 c3 48 83 fa 40 77 16 f3 0f 7f 07 f3 0f 7f 47 10 f3 0f 7f 44 17 f0 f3 0f 7f 44 17 e0 c3 48 8d 4f 40 <f3> 0f 7f 07 48 83 e1 c0 f3 0f 7f 44 17 f0 f3 0f 7f 47 10 f3 0f 7f' | scripts/decodecode
Code: 0f 7f 44 17 f0 f3 0f 7f 07 c3 48 83 fa 40 77 16 f3 0f 7f 07 f3 0f 7f 47 10 f3 0f 7f 44 17 f0 f3 0f 7f 44 17 e0 c3 48 8d 4f 40 <f3> 0f 7f 07 48 83 e1 c0 f3 0f 7f 44 17 f0 f3 0f 7f 47 10 f3 0f 7f
All code
========
   0:   0f 7f 44 17 f0          movq   %mm0,-0x10(%rdi,%rdx,1)
   5:   f3 0f 7f 07             movdqu %xmm0,(%rdi)
   9:   c3                      retq   
   a:   48 83 fa 40             cmp    $0x40,%rdx
   e:   77 16                   ja     0x26
  10:   f3 0f 7f 07             movdqu %xmm0,(%rdi)
  14:   f3 0f 7f 47 10          movdqu %xmm0,0x10(%rdi)
  19:   f3 0f 7f 44 17 f0       movdqu %xmm0,-0x10(%rdi,%rdx,1)
  1f:   f3 0f 7f 44 17 e0       movdqu %xmm0,-0x20(%rdi,%rdx,1)
  25:   c3                      retq   
  26:   48 8d 4f 40             lea    0x40(%rdi),%rcx
  2a:*  f3 0f 7f 07             movdqu %xmm0,(%rdi)             <-- trapping instruction
  2e:   48 83 e1 c0             and    $0xffffffffffffffc0,%rcx
  32:   f3 0f 7f 44 17 f0       movdqu %xmm0,-0x10(%rdi,%rdx,1)
  38:   f3 0f 7f 47 10          movdqu %xmm0,0x10(%rdi)
  3d:   f3                      repz
  3e:   0f                      .byte 0xf
  3f:   7f                      .byte 0x7f

Code starting with the faulting instruction
===========================================
   0:   f3 0f 7f 07             movdqu %xmm0,(%rdi)
   4:   48 83 e1 c0             and    $0xffffffffffffffc0,%rcx
   8:   f3 0f 7f 44 17 f0       movdqu %xmm0,-0x10(%rdi,%rdx,1)
   e:   f3 0f 7f 47 10          movdqu %xmm0,0x10(%rdi)
  13:   f3                      repz
  14:   0f                      .byte 0xf
  15:   7f                      .byte 0x7f

apparently this is some part of memcpy or a function like that.
Possible causes, in the order that seems most likely to me: a bug in init or memory leaks.

Answer 2

It's impossible to tell from the alarmist stack.
Most likely, ACPI support is traditionally crooked, load with the noacpi parameter, but you will have to forget about sleep modes.

Answer 3

• In any unclear situation, test the RAM (memtest86).
  
• In any unclear situation, update the BIOS.