Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unstable server - kernel errors in logs

Featured Replies

I don't have the most stable server and I cannot pinpoint the issue. I have already run memtest for multiple days with no errors found. Multiple kernel errors keep showing up in the logs and I don't really understand them.

I recently changed the USB flash drive as well but errors remain the same.

Looking for help. I have to kill the power and power on again to reset and reboot the server almost every time which is unfortunate.

<Jul 24 06:03:26 Tower kernel: WARNING: CPU: 14 PID: 30879 at fs/dcache.c:430 retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: Modules linked in: xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun nft_compat nf_tables ipvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge 8021q garp mrp stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 drm aesni_intel btusb crypto_simd btrtl cryptd btbcm btintel

Jul 24 06:03:26 Tower kernel: rapl intel_cstate mei_hdcp mei_pxp wmi_bmof mxm_wmi bluetooth i2c_i801 intel_gtt intel_uncore nvme agpgart i2c_smbus input_leds mei_me ahci igc led_class joydev i2c_core mei nvme_core ecdh_generic libahci ecc syscopyarea sysfillrect sysimgblt thermal fb_sys_fops fan tpm_crb tpm_tis video tpm_tis_core tpm wmi backlight intel_pmc_core acpi_pad acpi_tad button unix

Jul 24 06:03:26 Tower kernel: CPU: 14 PID: 30879 Comm: lsof Tainted: P O 6.1.106-Unraid #1

Jul 24 06:03:26 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D32/MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32), BIOS 1.G0 01/18/2024

Jul 24 06:03:26 Tower kernel: RIP: 0010:retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: Code: 74 18 eb e9 48 8b 43 60 48 89 df 48 8b 40 20 ff d0 0f 1f 00 85 c0 74 e4 eb d3 ff 4b 5c 0f ba e0 13 72 49 a9 00 04 08 00 74 02 <0f> 0b 0d 00 00 08 00 89 03 65 48 ff 05 b7 fb dc 7e f7 03 00 00 70

Jul 24 06:03:26 Tower kernel: RSP: 0018:ffffc90022097d98 EFLAGS: 00010206

Jul 24 06:03:26 Tower kernel: RAX: 0000000000600c00 RBX: ffff88806d440cc0 RCX: 0000000000000064

Jul 24 06:03:26 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff88806d440cc0

Jul 24 06:03:26 Tower kernel: RBP: ffffc90022097e65 R08: 00000000004f92e7 R09: 000000000000000a

Jul 24 06:03:26 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002

Jul 24 06:03:26 Tower kernel: R13: ffffffff812b089e R14: ffff88806d440cc0 R15: ffff88806d440cc0

Jul 24 06:03:26 Tower kernel: FS: 0000146b47686e00(0000) GS:ffff88903f380000(0000) knlGS:0000000000000000

Jul 24 06:03:26 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jul 24 06:03:26 Tower kernel: CR2: 00007f71989ef000 CR3: 000000078461c005 CR4: 0000000000772ee0

Jul 24 06:03:26 Tower kernel: PKRU: 55555554

Jul 24 06:03:26 Tower kernel: Call Trace:

Jul 24 06:03:26 Tower kernel: <TASK>

Jul 24 06:03:26 Tower kernel: ? __warn+0xab/0x122

Jul 24 06:03:26 Tower kernel: ? report_bug+0x109/0x17e

Jul 24 06:03:26 Tower kernel: ? retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: ? handle_bug+0x41/0x6f

Jul 24 06:03:26 Tower kernel: ? exc_invalid_op+0x13/0x60

Jul 24 06:03:26 Tower kernel: ? asm_exc_invalid_op+0x16/0x20

Jul 24 06:03:26 Tower kernel: ? tid_fd_update_inode+0x4d/0x4d

Jul 24 06:03:26 Tower kernel: ? retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: dput+0x41/0x17b

Jul 24 06:03:26 Tower kernel: proc_fill_cache+0x110/0x156

Jul 24 06:03:26 Tower kernel: ? compat_filldir+0x17a/0x17a

Jul 24 06:03:26 Tower kernel: proc_readfd_common+0x16b/0x1bc

Jul 24 06:03:26 Tower kernel: ? tid_fd_update_inode+0x4d/0x4d

Jul 24 06:03:26 Tower kernel: iterate_dir+0x94/0x149

Jul 24 06:03:26 Tower kernel: __do_sys_getdents64+0x6b/0xd8

Jul 24 06:03:26 Tower kernel: ? compat_filldir+0x17a/0x17a

Jul 24 06:03:26 Tower kernel: do_syscall_64+0x65/0x7b

Jul 24 06:03:26 Tower kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Jul 24 06:03:26 Tower kernel: RIP: 0033:0x146b478e6283

Jul 24 06:03:26 Tower kernel: Code: 89 df e8 20 05 fb ff 48 83 c4 08 48 89 e8 5b 5d c3 66 0f 1f 44 00 00 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 61 0b 11 00 f7 d8

Jul 24 06:03:26 Tower kernel: RSP: 002b:00007ffc0a8a52b8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9

Jul 24 06:03:26 Tower kernel: RAX: ffffffffffffffda RBX: 00000000004de380 RCX: 0000146b478e6283

Jul 24 06:03:26 Tower kernel: RDX: 0000000000008000 RSI: 00000000004de3b0 RDI: 0000000000000004

Jul 24 06:03:26 Tower kernel: RBP: 00000000004de384 R08: 0000146b479f8300 R09: 0000146b479f8300

Jul 24 06:03:26 Tower kernel: R10: 0000000000000000 R11: 0000000000000293 R12: ffffffffffffff88

Jul 24 06:03:26 Tower kernel: R13: 0000000000000002 R14: 0000000000433dd0 R15: 0000146b47a79000

Jul 24 06:03:26 Tower kernel: </TASK>

Jul 24 06:03:26 Tower kernel: ---[ end trace 0000000000000000 ]---

Jul 24 06:03:33 Tower kernel: ------------[ cut here ]------------

Jul 24 06:03:33 Tower kernel: WARNING: CPU: 0 PID: 313 at fs/dcache.c:483 d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: Modules linked in: xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun nft_compat nf_tables ipvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge 8021q garp mrp stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 drm aesni_intel btusb crypto_simd btrtl cryptd btbcm btintel

Jul 24 06:03:33 Tower kernel: rapl intel_cstate mei_hdcp mei_pxp wmi_bmof mxm_wmi bluetooth i2c_i801 intel_gtt intel_uncore nvme agpgart i2c_smbus input_leds mei_me ahci igc led_class joydev i2c_core mei nvme_core ecdh_generic libahci ecc syscopyarea sysfillrect sysimgblt thermal fb_sys_fops fan tpm_crb tpm_tis video tpm_tis_core tpm wmi backlight intel_pmc_core acpi_pad acpi_tad button unix

Jul 24 06:03:33 Tower kernel: CPU: 0 PID: 313 Comm: kswapd0 Tainted: P W O 6.1.106-Unraid #1

Jul 24 06:03:33 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D32/MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32), BIOS 1.G0 01/18/2024

Jul 24 06:03:33 Tower kernel: RIP: 0010:d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: Code: e7 e8 31 c2 62 00 5a 48 89 d8 5b 5d 41 5c c3 cc cc cc cc 0f 1f 44 00 00 8b 06 89 c1 81 e1 00 04 08 00 81 f9 00 00 08 00 74 02 <0f> 0b 89 c1 80 cd 04 a9 00 00 70 00 89 0e 75 08 65 48 ff 0d 44 f9

Jul 24 06:03:33 Tower kernel: RSP: 0018:ffffc90004c4fab0 EFLAGS: 00010206

Jul 24 06:03:33 Tower kernel: RAX: 0000000000680c00 RBX: ffff88806d440d40 RCX: 0000000000080400

Jul 24 06:03:33 Tower kernel: RDX: ffffc90004c4fb78 RSI: ffff88806d440cc0 RDI: ffff888109558348

Jul 24 06:03:33 Tower kernel: RBP: ffff88806d440d18 R08: 0000000000000000 R09: 000000000000002c

Jul 24 06:03:33 Tower kernel: R10: ffff88806d440e00 R11: 0000000000000006 R12: ffff888109558348

Jul 24 06:03:33 Tower kernel: R13: ffffc90004c4fb78 R14: ffffffff8125be2d R15: ffff88806d440d40

Jul 24 06:03:33 Tower kernel: FS: 0000000000000000(0000) GS:ffff88903f000000(0000) knlGS:0000000000000000

Jul 24 06:03:33 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jul 24 06:03:33 Tower kernel: CR2: 000014dea8a4e000 CR3: 0000000923ee6003 CR4: 0000000000772ef0

Jul 24 06:03:33 Tower kernel: PKRU: 55555554

Jul 24 06:03:33 Tower kernel: Call Trace:

Jul 24 06:03:33 Tower kernel: <TASK>

Jul 24 06:03:33 Tower kernel: ? __warn+0xab/0x122

Jul 24 06:03:33 Tower kernel: ? report_bug+0x109/0x17e

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: ? handle_bug+0x41/0x6f

Jul 24 06:03:33 Tower kernel: ? exc_invalid_op+0x13/0x60

Jul 24 06:03:33 Tower kernel: ? asm_exc_invalid_op+0x16/0x20

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x38/0x38

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: dentry_lru_isolate+0x9c/0xb1

Jul 24 06:03:33 Tower kernel: __list_lru_walk_one+0x90/0x123

Jul 24 06:03:33 Tower kernel: list_lru_walk_one+0x60/0x7d

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x38/0x38

Jul 24 06:03:33 Tower kernel: prune_dcache_sb+0x46/0x73

Jul 24 06:03:33 Tower kernel: super_cache_scan+0xf4/0x17c

Jul 24 06:03:33 Tower kernel: do_shrink_slab+0x188/0x2a1

Jul 24 06:03:33 Tower kernel: shrink_slab+0x1f9/0x267

Jul 24 06:03:33 Tower kernel: shrink_node+0x334/0x588

Jul 24 06:03:33 Tower kernel: balance_pgdat+0x4e9/0x6a2

Jul 24 06:03:33 Tower kernel: ? sysvec_apic_timer_interrupt+0x92/0xa6

Jul 24 06:03:33 Tower kernel: kswapd+0x2f0/0x333

Jul 24 06:03:33 Tower kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20

Jul 24 06:03:33 Tower kernel: ? balance_pgdat+0x6a2/0x6a2

Jul 24 06:03:33 Tower kernel: kthread+0xe4/0xef

Jul 24 06:03:33 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b

Jul 24 06:03:33 Tower kernel: ret_from_fork+0x1f/0x30

Jul 24 06:03:33 Tower kernel: </TASK>

Jul 24 06:03:33 Tower kernel: ---[ end trace 0000000000000000 ]---

Jul 24 06:19:24 Tower ool www[13200]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config

Jul 24 06:19:27 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="19777" x-info="https://www.rsyslog.com"] start

Jul 24 06:20:01 Tower ool www[25333]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config

Jul 24 06:20:03 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="25668" x-info="https://www.rsyslog.com"] start/>

Any help is greatly appreciated!

tower-diagnostics-20250724-2109.zip

Your Motherboard bios is very old (7 versions out of date) and is missing the stability and longevity modifications made by intel in an attempt to "save" the faulty Raptor Lake CPUs, so I'd be wary of that as using raptor lake CPUs especially K models without those microcode updates will permanently damage the CPU over time. The 13/14700k and 13/14900k being the most commonly affected models in that range.

Before doing any other troubleshooting I would update the bios, but if you are affected by that issue the damage may already be done and the CPU will need to be replaced under warranty.

Edited by Faceman

  • Author

Thank you, i was not aware of the issues with the Intel chips. I am also not the most techie either.

I will work on getting the BIOS updated this weekend.

Could you or somebody shed some light on the warranty process please? What proof would i need to show Intel and how can i generate it to start the warranty process?

Thank you very much!!

  • Community Expert
10 hours ago, dynamo666 said:

I don't have the most stable server and I cannot pinpoint the issue. I have already run memtest for multiple days with no errors found. Multiple kernel errors keep showing up in the logs and I don't really understand them.

I recently changed the USB flash drive as well but errors remain the same.

Looking for help. I have to kill the power and power on again to reset and reboot the server almost every time which is unfortunate.

<Jul 24 06:03:26 Tower kernel: WARNING: CPU: 14 PID: 30879 at fs/dcache.c:430 retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: Modules linked in: xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun nft_compat nf_tables ipvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge 8021q garp mrp stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 drm aesni_intel btusb crypto_simd btrtl cryptd btbcm btintel

Jul 24 06:03:26 Tower kernel: rapl intel_cstate mei_hdcp mei_pxp wmi_bmof mxm_wmi bluetooth i2c_i801 intel_gtt intel_uncore nvme agpgart i2c_smbus input_leds mei_me ahci igc led_class joydev i2c_core mei nvme_core ecdh_generic libahci ecc syscopyarea sysfillrect sysimgblt thermal fb_sys_fops fan tpm_crb tpm_tis video tpm_tis_core tpm wmi backlight intel_pmc_core acpi_pad acpi_tad button unix

Jul 24 06:03:26 Tower kernel: CPU: 14 PID: 30879 Comm: lsof Tainted: P O 6.1.106-Unraid #1

Jul 24 06:03:26 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D32/MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32), BIOS 1.G0 01/18/2024

Jul 24 06:03:26 Tower kernel: RIP: 0010:retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: Code: 74 18 eb e9 48 8b 43 60 48 89 df 48 8b 40 20 ff d0 0f 1f 00 85 c0 74 e4 eb d3 ff 4b 5c 0f ba e0 13 72 49 a9 00 04 08 00 74 02 <0f> 0b 0d 00 00 08 00 89 03 65 48 ff 05 b7 fb dc 7e f7 03 00 00 70

Jul 24 06:03:26 Tower kernel: RSP: 0018:ffffc90022097d98 EFLAGS: 00010206

Jul 24 06:03:26 Tower kernel: RAX: 0000000000600c00 RBX: ffff88806d440cc0 RCX: 0000000000000064

Jul 24 06:03:26 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff88806d440cc0

Jul 24 06:03:26 Tower kernel: RBP: ffffc90022097e65 R08: 00000000004f92e7 R09: 000000000000000a

Jul 24 06:03:26 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002

Jul 24 06:03:26 Tower kernel: R13: ffffffff812b089e R14: ffff88806d440cc0 R15: ffff88806d440cc0

Jul 24 06:03:26 Tower kernel: FS: 0000146b47686e00(0000) GS:ffff88903f380000(0000) knlGS:0000000000000000

Jul 24 06:03:26 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jul 24 06:03:26 Tower kernel: CR2: 00007f71989ef000 CR3: 000000078461c005 CR4: 0000000000772ee0

Jul 24 06:03:26 Tower kernel: PKRU: 55555554

Jul 24 06:03:26 Tower kernel: Call Trace:

Jul 24 06:03:26 Tower kernel: <TASK>

Jul 24 06:03:26 Tower kernel: ? __warn+0xab/0x122

Jul 24 06:03:26 Tower kernel: ? report_bug+0x109/0x17e

Jul 24 06:03:26 Tower kernel: ? retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: ? handle_bug+0x41/0x6f

Jul 24 06:03:26 Tower kernel: ? exc_invalid_op+0x13/0x60

Jul 24 06:03:26 Tower kernel: ? asm_exc_invalid_op+0x16/0x20

Jul 24 06:03:26 Tower kernel: ? tid_fd_update_inode+0x4d/0x4d

Jul 24 06:03:26 Tower kernel: ? retain_dentry+0x52/0xa5

Jul 24 06:03:26 Tower kernel: dput+0x41/0x17b

Jul 24 06:03:26 Tower kernel: proc_fill_cache+0x110/0x156

Jul 24 06:03:26 Tower kernel: ? compat_filldir+0x17a/0x17a

Jul 24 06:03:26 Tower kernel: proc_readfd_common+0x16b/0x1bc

Jul 24 06:03:26 Tower kernel: ? tid_fd_update_inode+0x4d/0x4d

Jul 24 06:03:26 Tower kernel: iterate_dir+0x94/0x149

Jul 24 06:03:26 Tower kernel: __do_sys_getdents64+0x6b/0xd8

Jul 24 06:03:26 Tower kernel: ? compat_filldir+0x17a/0x17a

Jul 24 06:03:26 Tower kernel: do_syscall_64+0x65/0x7b

Jul 24 06:03:26 Tower kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Jul 24 06:03:26 Tower kernel: RIP: 0033:0x146b478e6283

Jul 24 06:03:26 Tower kernel: Code: 89 df e8 20 05 fb ff 48 83 c4 08 48 89 e8 5b 5d c3 66 0f 1f 44 00 00 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 61 0b 11 00 f7 d8

Jul 24 06:03:26 Tower kernel: RSP: 002b:00007ffc0a8a52b8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9

Jul 24 06:03:26 Tower kernel: RAX: ffffffffffffffda RBX: 00000000004de380 RCX: 0000146b478e6283

Jul 24 06:03:26 Tower kernel: RDX: 0000000000008000 RSI: 00000000004de3b0 RDI: 0000000000000004

Jul 24 06:03:26 Tower kernel: RBP: 00000000004de384 R08: 0000146b479f8300 R09: 0000146b479f8300

Jul 24 06:03:26 Tower kernel: R10: 0000000000000000 R11: 0000000000000293 R12: ffffffffffffff88

Jul 24 06:03:26 Tower kernel: R13: 0000000000000002 R14: 0000000000433dd0 R15: 0000146b47a79000

Jul 24 06:03:26 Tower kernel: </TASK>

Jul 24 06:03:26 Tower kernel: ---[ end trace 0000000000000000 ]---

Jul 24 06:03:33 Tower kernel: ------------[ cut here ]------------

Jul 24 06:03:33 Tower kernel: WARNING: CPU: 0 PID: 313 at fs/dcache.c:483 d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: Modules linked in: xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun nft_compat nf_tables ipvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge 8021q garp mrp stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 drm aesni_intel btusb crypto_simd btrtl cryptd btbcm btintel

Jul 24 06:03:33 Tower kernel: rapl intel_cstate mei_hdcp mei_pxp wmi_bmof mxm_wmi bluetooth i2c_i801 intel_gtt intel_uncore nvme agpgart i2c_smbus input_leds mei_me ahci igc led_class joydev i2c_core mei nvme_core ecdh_generic libahci ecc syscopyarea sysfillrect sysimgblt thermal fb_sys_fops fan tpm_crb tpm_tis video tpm_tis_core tpm wmi backlight intel_pmc_core acpi_pad acpi_tad button unix

Jul 24 06:03:33 Tower kernel: CPU: 0 PID: 313 Comm: kswapd0 Tainted: P W O 6.1.106-Unraid #1

Jul 24 06:03:33 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D32/MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32), BIOS 1.G0 01/18/2024

Jul 24 06:03:33 Tower kernel: RIP: 0010:d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: Code: e7 e8 31 c2 62 00 5a 48 89 d8 5b 5d 41 5c c3 cc cc cc cc 0f 1f 44 00 00 8b 06 89 c1 81 e1 00 04 08 00 81 f9 00 00 08 00 74 02 <0f> 0b 89 c1 80 cd 04 a9 00 00 70 00 89 0e 75 08 65 48 ff 0d 44 f9

Jul 24 06:03:33 Tower kernel: RSP: 0018:ffffc90004c4fab0 EFLAGS: 00010206

Jul 24 06:03:33 Tower kernel: RAX: 0000000000680c00 RBX: ffff88806d440d40 RCX: 0000000000080400

Jul 24 06:03:33 Tower kernel: RDX: ffffc90004c4fb78 RSI: ffff88806d440cc0 RDI: ffff888109558348

Jul 24 06:03:33 Tower kernel: RBP: ffff88806d440d18 R08: 0000000000000000 R09: 000000000000002c

Jul 24 06:03:33 Tower kernel: R10: ffff88806d440e00 R11: 0000000000000006 R12: ffff888109558348

Jul 24 06:03:33 Tower kernel: R13: ffffc90004c4fb78 R14: ffffffff8125be2d R15: ffff88806d440d40

Jul 24 06:03:33 Tower kernel: FS: 0000000000000000(0000) GS:ffff88903f000000(0000) knlGS:0000000000000000

Jul 24 06:03:33 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jul 24 06:03:33 Tower kernel: CR2: 000014dea8a4e000 CR3: 0000000923ee6003 CR4: 0000000000772ef0

Jul 24 06:03:33 Tower kernel: PKRU: 55555554

Jul 24 06:03:33 Tower kernel: Call Trace:

Jul 24 06:03:33 Tower kernel: <TASK>

Jul 24 06:03:33 Tower kernel: ? __warn+0xab/0x122

Jul 24 06:03:33 Tower kernel: ? report_bug+0x109/0x17e

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: ? handle_bug+0x41/0x6f

Jul 24 06:03:33 Tower kernel: ? exc_invalid_op+0x13/0x60

Jul 24 06:03:33 Tower kernel: ? asm_exc_invalid_op+0x16/0x20

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x38/0x38

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x17/0x38

Jul 24 06:03:33 Tower kernel: dentry_lru_isolate+0x9c/0xb1

Jul 24 06:03:33 Tower kernel: __list_lru_walk_one+0x90/0x123

Jul 24 06:03:33 Tower kernel: list_lru_walk_one+0x60/0x7d

Jul 24 06:03:33 Tower kernel: ? d_lru_shrink_move+0x38/0x38

Jul 24 06:03:33 Tower kernel: prune_dcache_sb+0x46/0x73

Jul 24 06:03:33 Tower kernel: super_cache_scan+0xf4/0x17c

Jul 24 06:03:33 Tower kernel: do_shrink_slab+0x188/0x2a1

Jul 24 06:03:33 Tower kernel: shrink_slab+0x1f9/0x267

Jul 24 06:03:33 Tower kernel: shrink_node+0x334/0x588

Jul 24 06:03:33 Tower kernel: balance_pgdat+0x4e9/0x6a2

Jul 24 06:03:33 Tower kernel: ? sysvec_apic_timer_interrupt+0x92/0xa6

Jul 24 06:03:33 Tower kernel: kswapd+0x2f0/0x333

Jul 24 06:03:33 Tower kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20

Jul 24 06:03:33 Tower kernel: ? balance_pgdat+0x6a2/0x6a2

Jul 24 06:03:33 Tower kernel: kthread+0xe4/0xef

Jul 24 06:03:33 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b

Jul 24 06:03:33 Tower kernel: ret_from_fork+0x1f/0x30

Jul 24 06:03:33 Tower kernel: </TASK>

Jul 24 06:03:33 Tower kernel: ---[ end trace 0000000000000000 ]---

Jul 24 06:19:24 Tower ool www[13200]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config

Jul 24 06:19:27 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="19777" x-info="https://www.rsyslog.com"] start

Jul 24 06:20:01 Tower ool www[25333]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config

Jul 24 06:20:03 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="25668" x-info="https://www.rsyslog.com"] start/>

Any help is greatly appreciated!

tower-diagnostics-20250724-2109.zip

given you still run an "out of date" bios, without the microcode update for 13th and 14th gen, you might be in for a "fun time"

  • Author
1 hour ago, kagurazaki said:

This looks like the same problem I have been having with my recently purchased dell r930 server.

I reverted back to unraid 6.12.15 and that solved my problem.

check https://forums.unraid.net/topic/192180-unraid-server-crashing/

maybe it can help you too.

I am on 6.12.13 and haven't upgraded since. Do you think I should I try go to 6.12.15 for now and test it out for a few weeks before jumping to 7?

  • Author
1 hour ago, Mainfrezzer said:

given you still run an "out of date" bios, without the microcode update for 13th and 14th gen, you might be in for a "fun time"

Oh boy.. that doesn't sound good. Am I at a risk of losing my entire array/library if I try to upgrade the BIOS? Could you please elaborate more. Of course I would like for it go smooth, but I know that's a pipe dream as well.

the drive assignments for the array is stored on the flash drive, updating your bios should not interfere with your drives.

as long as the same drives are used with your unraid config you can change almost anything with your other hardware. But it is still recommended to have some form of data backup in the event of a catastrophic failure.

as for the unraid version, i assumed you were already on version 7, in which case your kernel error problem is different than mine so i cant help you there.

  • Author

I updated the BIOS with the latest on the MSI website. I nervously went with Beta version of the BIOS. Hoping the server will be more stable. Will monitor for the next few days.

Edited by dynamo666

  • Author

Had another event overnight where I could ping the server's IP address, but I was not able to access the webpage, shares or open any of the docker container's webpages. Happened between 140am till 755am. Not sure if related to the processor issues noted before? Surprisingly systems came back online by itself without any intervention. Should I look to start the warranty replacement of the processor at this time? I am unable to download diagnostics. Been running for the last 30min.

Several events in the log some of which are shown below and syslog from last night attached :syslog.txt

<

1:52:50 Tower kernel: smbd invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0

Jul 27 02:30:58 Tower kernel: CPU: 10 PID: 6422 Comm: smbd Tainted: P O 6.1.106-Unraid #1

Jul 27 02:59:23 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D32/MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32), BIOS 1.M1 05/20/2025

Jul 27 03:33:58 Tower kernel: Call Trace:

Jul 27 04:07:38 Tower kernel: <TASK>

Jul 27 04:40:48 Tower kernel: dump_stack_lvl+0x44/0x5c

Jul 27 05:31:14 Tower kernel: dump_header+0x4a/0x211

Jul 27 06:24:52 Tower kernel: oom_kill_process+0x80/0x111

Jul 27 06:58:14 Tower kernel: out_of_memory+0x3b3/0x3e5

Jul 27 07:55:49 Tower kernel: __alloc_pages_slowpath.constprop.0+0x780/0x97e

Jul 27 07:55:49 Tower kernel: __alloc_pages+0x132/0x1e8

Jul 27 07:55:49 Tower kernel: folio_alloc+0x14/0x35

Jul 27 07:55:49 Tower kernel: __filemap_get_folio+0x185/0x213

Jul 27 07:55:49 Tower kernel: ? preempt_latency_start+0x1e/0x46

Jul 27 07:55:49 Tower kernel: filemap_fault+0x317/0x52f

Jul 27 07:55:49 Tower kernel: __do_fault+0x2a/0x6b

Jul 27 07:55:49 Tower kernel: __handle_mm_fault+0xa22/0xcf9

Jul 27 07:55:49 Tower kernel: handle_mm_fault+0x13d/0x20f

Jul 27 07:55:49 Tower kernel: do_user_addr_fault+0x2c3/0x465

Jul 27 07:55:49 Tower kernel: exc_page_fault+0xfb/0x11d

Jul 27 07:55:49 Tower kernel: asm_exc_page_fault+0x22/0x30

Jul 27 07:55:49 Tower kernel: RIP: 0033:0x150a3ff2f607

Jul 27 07:55:49 Tower kernel: Code: Unable to access opcode bytes at 0x150a3ff2f5dd.

Jul 27 07:55:49 Tower kernel: RSP: 002b:00007fffc57f6810 EFLAGS: 00010246

Jul 27 07:55:49 Tower kernel: RAX: 0000150a3ff771f0 RBX: 0000000000000000 RCX: 00007fffc57f6850

Jul 27 07:55:49 Tower kernel: RDX: 0000150a3fd5e32b RSI: 0000000000000003 RDI: 0000000000000000

Jul 27 07:55:49 Tower kernel: RBP: 0000150a3fd5e32b R08: 0000150a40088b75 R09: 000055d473bd5fe0

Jul 27 07:55:49 Tower kernel: R10: 000055d473b97c80 R11: 00007fffc57f6940 R12: 00007fffc57f6850

Jul 27 07:55:49 Tower kernel: R13: 00000000ffffffff R14: 0000000000000000 R15: 000055d473bb7d50

Jul 27 07:55:49 Tower kernel: </TASK>

Jul 27 07:55:49 Tower kernel: Mem-Info:

Jul 27 07:55:49 Tower kernel: active_anon:2888151 inactive_anon:12783875 isolated_anon:0

Jul 27 07:55:49 Tower kernel: active_file:0 inactive_file:20641 isolated_file:81

Jul 27 07:55:49 Tower kernel: unevictable:24736 dirty:240 writeback:0

Jul 27 07:55:49 Tower kernel: slab_reclaimable:192647 slab_unreclaimable:130254

Jul 27 07:55:49 Tower kernel: mapped:71887 shmem:378950 pagetables:131447

Jul 27 07:55:49 Tower kernel: sec_pagetables:1356 bounce:0

Jul 27 07:55:49 Tower kernel: kernel_misc_reclaimable:0

Jul 27 07:55:49 Tower kernel: free:122680 free_pcp:166 free_cma:0

Jul 27 07:55:49 Tower kernel: Node 0 active_anon:11552604kB inactive_anon:51135500kB active_file:0kB inactive_file:82564kB unevictable:98944kB isolated(anon):0kB isolated(file):324kB mapped:287548kB dirty:960kB writeback:0kB shmem:1515800kB shmem_thp: 12288kB shmem_pmdmapped: 0kB anon_thp: 19103744kB writeback_tmp:0kB kernel_stack:56736kB pagetables:525788kB sec_pagetables:5424kB all_unreclaimable? no

Jul 27 07:55:49 Tower kernel: Node 0 DMA free:15360kB boost:0kB min:12kB low:24kB high:36kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB

Jul 27 07:55:49 Tower kernel: lowmem_reserve[]: 0 1646 64000 64000 64000

Jul 27 07:55:49 Tower kernel: Node 0 DMA32 free:251020kB boost:0kB min:1736kB low:3420kB high:5104kB reserved_highatomic:0KB active_anon:77612kB inactive_anon:1378360kB active_file:0kB inactive_file:532kB unevictable:1172kB writepending:32kB present:1810888kB managed:1720268kB mlocked:0kB bounce:0kB free_pcp:248kB local_pcp:0kB free_cma:0kB

Jul 27 07:55:49 Tower kernel: lowmem_reserve[]: 0 0 62353 62353 62353

Jul 27 07:55:49 Tower kernel: Node 0 Normal free:224340kB boost:83968kB min:149796kB low:213644kB high:277492kB reserved_highatomic:0KB active_anon:11474992kB inactive_anon:49757140kB active_file:0kB inactive_file:83236kB unevictable:97772kB writepending:928kB present:65003520kB managed:63850244kB mlocked:352kB bounce:0kB free_pcp:416kB local_pcp:0kB free_cma:0kB

Jul 27 07:55:49 Tower kernel: lowmem_reserve[]: 0 0 0 0 0

Jul 27 07:55:49 Tower kernel: Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15360kB

Jul 27 07:55:49 Tower kernel: Node 0 DMA32: 87*4kB (UE) 669*8kB (UM) 727*16kB (UME) 527*32kB (UME) 354*64kB (UME) 183*128kB (UME) 101*256kB (UME) 55*512kB (UME) 12*1024kB (UME) 3*2048kB (UE) 24*4096kB (UM) = 251028kB/>

out of memory errors all through that syslog, check your container memory usage.

Particularly chromium, it's showing up a lot in that syslog.

  • Author
On 7/28/2025 at 5:53 PM, Faceman said:

out of memory errors all through that syslog, check your container memory usage.

Particularly chromium, it's showing up a lot in that syslog.

Thanks for reviewing. Although it doesn't look outrageous when I look aunder the Docker tab but I will try and shut it down when I am not using the Chromium container moving forward.

image.png

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.