Crash on __list_del_entry

General support questions
Post Reply
xxteknolustxx
Posts: 15
Joined: 2019/11/27 14:58:11

Crash on __list_del_entry

Post by xxteknolustxx » 2023/03/17 15:05:45

Hello,

Running 7.9.2009/Linux dedicated-server 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I keep getting crashes that seem to all fail with similar backtrace __list_del_entry with a panic message "general protection fault: 0000 [#1] SMP" with different commands (this last one was kswapd, last week it was nginx)

Is this a bug with the kernel or am I having some sort of memory issue?

Code: Select all

      KERNEL: /usr/lib/debug/lib/modules/3.10.0-1160.11.1.el7.x86_64/vmlinux
    DUMPFILE: 127.0.0.1-2023-03-17-07:56:31/vmcore  [PARTIAL DUMP]
        CPUS: 24
        DATE: Fri Mar 17 07:56:21 2023
      UPTIME: 4 days, 07:16:53
LOAD AVERAGE: 0.21, 0.38, 0.41
       TASKS: 3137
     RELEASE: 3.10.0-1160.11.1.el7.x86_64
     VERSION: #1 SMP Fri Dec 18 16:34:56 UTC 2020
     MACHINE: x86_64  (3492 Mhz)
      MEMORY: 63.9 GB
       PANIC: "general protection fault: 0000 [#1] SMP "
         PID: 148
     COMMAND: "kswapd0"
        TASK: ffffa02040fa5280  [THREAD_INFO: ffffa020517c0000]
         CPU: 7
       STATE: TASK_RUNNING (PANIC)

Code: Select all


crash> bt
PID: 148    TASK: ffffa02040fa5280  CPU: 7   COMMAND: "kswapd0"
 #0 [ffffa020517c3838] machine_kexec at ffffffff894662c4
 #1 [ffffa020517c3898] __crash_kexec at ffffffff89522802
 #2 [ffffa020517c3968] crash_kexec at ffffffff895228f0
 #3 [ffffa020517c3980] oops_end at ffffffff89b8b798
 #4 [ffffa020517c39a8] die at ffffffff89430a7b
 #5 [ffffa020517c39d8] do_general_protection at ffffffff89b8b092
 #6 [ffffa020517c3a10] general_protection at ffffffff89b8a718
    [exception RIP: __list_del_entry+41]
    RIP: ffffffff897a5d09  RSP: ffffa020517c3ac0  RFLAGS: 00010006
    RAX: fbffd2dd5c435fa0  RBX: 000000000000001a  RCX: dead000000000200
    RDX: ffffa02078781440  RSI: 0000000000000003  RDI: ffffd2dd504c6fe0
    RBP: ffffa020517c3ac0   R8: ffffd2dd504c6f60   R9: 0000000000000000
    R10: 0000000000000000  R11: ffffa02bd6bf2c98  R12: 000000000000001a
    R13: 0000000000000020  R14: ffffd2dd504c6fe0  R15: ffffa02078781440
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #7 [ffffa020517c3ac8] isolate_lru_pages at ffffffff895d1e21
 #8 [ffffa020517c3b38] shrink_active_list at ffffffff895d3b1a
 #9 [ffffa020517c3bf0] shrink_lruvec at ffffffff895d4191
#10 [ffffa020517c3cf0] shrink_zone at ffffffff895d4556
#11 [ffffa020517c3d48] balance_pgdat at ffffffff895d5763
#12 [ffffa020517c3e20] kswapd at ffffffff895d5b33
#13 [ffffa020517c3ec8] kthread at ffffffff894c5e71
#14 [ffffa020517c3f50] ret_from_fork_nospec_begin at ffffffff89b93de4
Last edited by xxteknolustxx on 2023/03/21 02:28:15, edited 1 time in total.
Top
tunk
Posts: 1188
Joined: 2017/02/22 15:08:17

Re: Crash on __list_del_entry

Post by tunk » 2023/03/17 15:57:13

This is the newest kernel: 3.10.0-1160.88.1.el7.x86_64
Maybe you could run yum update?
Top
User avatar
TrevorH
Site Admin
Posts: 32978
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Crash on __list_del_entry

Post by TrevorH » 2023/03/17 16:06:17

Fri Dec 18 16:34:56 UTC 2020
Your kernel is over 2 years out of date. Run yum update to pick up all updates, reboot and see if the problem recurs.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Top
xxteknolustxx
Posts: 15
Joined: 2019/11/27 14:58:11

Re: Crash on __list_del_entry

Post by xxteknolustxx » 2023/03/17 16:25:03

I will, thanks for reply
Top
xxteknolustxx
Posts: 15
Joined: 2019/11/27 14:58:11

Re: Crash on __list_del_entry

Post by xxteknolustxx » 2023/03/21 02:28:05

TrevorH wrote: ↑
2023/03/17 16:06:17
Fri Dec 18 16:34:56 UTC 2020
Your kernel is over 2 years out of date. Run yum update to pick up all updates, reboot and see if the problem recurs.
I updated kernel to 3.10.0-1160.88.1 and got another crash randomly. Same back trace as before (see below)

Any ideas?

Code: Select all


      KERNEL: /usr/lib/debug/lib/modules/3.10.0-1160.88.1.el7.x86_64/vmlinux
    DUMPFILE: 127.0.0.1-2023-03-20-22:15:08/vmcore  [PARTIAL DUMP]
        CPUS: 24
        DATE: Mon Mar 20 22:14:57 2023
      UPTIME: 21:59:41
LOAD AVERAGE: 0.38, 0.54, 0.83
       TASKS: 3196
     RELEASE: 3.10.0-1160.88.1.el7.x86_64
     VERSION: #1 SMP Tue Mar 7 15:41:52 UTC 2023
     MACHINE: x86_64  (3493 Mhz)
      MEMORY: 63.9 GB
       PANIC: "general protection fault: 0000 [#1] SMP "
         PID: 147
     COMMAND: "kswapd0"
        TASK: ffff9c317964c200  [THREAD_INFO: ffff9c31790dc000]
         CPU: 7
       STATE: TASK_RUNNING (PANIC)

Code: Select all

crash> bt
PID: 147    TASK: ffff9c317964c200  CPU: 7   COMMAND: "kswapd0"
 #0 [ffff9c31790df828] machine_kexec at ffffffff9fa69514
 #1 [ffff9c31790df888] __crash_kexec at ffffffff9fb29e82
 #2 [ffff9c31790df958] crash_kexec at ffffffff9fb29f78
 #3 [ffff9c31790df970] oops_end at ffffffffa01bc818
 #4 [ffff9c31790df998] die at ffffffff9fa31c0b
 #5 [ffff9c31790df9c8] do_general_protection at ffffffffa01bc0f2
 #6 [ffff9c31790dfa00] general_protection at ffffffffa01bb758
    [exception RIP: __list_del_entry+45]
    RIP: ffffffff9fdbd23d  RSP: ffff9c31790dfab0  RFLAGS: 00010002
    RAX: fbffe8da500a3c20  RBX: 0000000000000009  RCX: dead000000000200
    RDX: ffff9c312fde3430  RSI: 0000000000000002  RDI: ffffe8da504c6fe0
    RBP: ffff9c31790dfab0   R8: ffffe8da4ff76ba0   R9: 0000000000000000
    R10: 0000000000000000  R11: fff00000f0000000  R12: 0000000000000009
    R13: 0000000000000020  R14: ffffe8da504c6fe0  R15: ffff9c312fde3430
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #7 [ffff9c31790dfab8] isolate_lru_pages at ffffffff9fbddac1
 #8 [ffff9c31790dfb28] shrink_inactive_list at ffffffff9fbdf240
 #9 [ffff9c31790dfbf0] shrink_lruvec at ffffffff9fbdfde5
#10 [ffff9c31790dfcf0] shrink_zone at ffffffff9fbe0216
#11 [ffff9c31790dfd48] balance_pgdat at ffffffff9fbe1443
#12 [ffff9c31790dfe20] kswapd at ffffffff9fbe1813
#13 [ffff9c31790dfec8] kthread at ffffffff9facb621
Top
User avatar
TrevorH
Site Admin
Posts: 32978
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Crash on __list_del_entry

Post by TrevorH » 2023/03/21 11:03:09

I would boot and run memtest86+ for a few hours, maybe a day and see if it finds any RAM problems. I do not think it will but it's worth checking first. If it passes then you probably need to create a bugzilla.redhat.com entry for the crash as only RH can fix kernel bugs. If it fails then you need to fix that first.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Top
xxteknolustxx
Posts: 15
Joined: 2019/11/27 14:58:11

Re: Crash on __list_del_entry

Post by xxteknolustxx » 2023/03/21 18:25:52

will do, thanks
Top
xxteknolustxx
Posts: 15
Joined: 2019/11/27 14:58:11

Re: Crash on __list_del_entry

Post by xxteknolustxx » 2023/03/21 18:38:02

Lol within 15 minutes it was throwing errors on memtest, guess I'll replace ram
Top
Post Reply

Return to “CentOS 7 - General Support”