mikefallen Posted April 17, 2018 Share Posted April 17, 2018 (edited) On latest unraid version i have been having some seemingly random kernel panics .... weirdly this causes my plex docker to stop working but the server is still up and running fine See a lot of errors related to IPMI so i uninstalled the IPMI plugin... see if that helps Apr 17 01:29:31 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout Apr 17 01:57:56 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout Apr 17 02:13:30 Tower root: /mnt/cache: 95.5 GiB (102534463488 bytes) trimmed Apr 17 02:26:20 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout Apr 17 02:54:44 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout Apr 17 03:04:32 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 Apr 17 03:04:32 Tower kernel: IP: tcp_push+0x4e/0xee Apr 17 03:04:32 Tower kernel: PGD 15f68a067 P4D 15f68a067 PUD 3dbefc067 PMD 0 Apr 17 03:04:32 Tower kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI Apr 17 03:04:32 Tower kernel: Modules linked in: tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod ipmi_devintf forcedeth amd64_edac_mod edac_mce_amd kvm_amd kvm k10temp sata_nv sata_mv button ipmi_si acpi_cpufreq [last unloaded: forcedeth] Apr 17 03:04:32 Tower kernel: CPU: 4 PID: 12621 Comm: Plex Media Serv Not tainted 4.14.26-unRAID #1 Apr 17 03:04:32 Tower kernel: Hardware name: Supermicro H8DM8-2/H8DM8-2, BIOS 080014 10/22/2009 Apr 17 03:04:32 Tower kernel: task: ffff8803bd71cc80 task.stack: ffffc900052a8000 Apr 17 03:04:32 Tower kernel: RIP: 0010:tcp_push+0x4e/0xee Apr 17 03:04:32 Tower kernel: RSP: 0018:ffffc900052abc70 EFLAGS: 00010246 Apr 17 03:04:32 Tower kernel: RAX: 0000000000000000 RBX: 00000000000005a0 RCX: 0000000000000000 Apr 17 03:04:32 Tower kernel: RDX: 0000000000000000 RSI: 0000000000004040 RDI: ffff88000fbae000 Apr 17 03:04:32 Tower kernel: RBP: ffff8803bd71d5a0 R08: 0000000000004920 R09: ffffffff8151be00 Apr 17 03:04:32 Tower kernel: R10: ffff88000fbae158 R11: 0000000000000000 R12: ffff88000fbae000 Apr 17 03:04:32 Tower kernel: R13: 0000000000000000 R14: ffff8802f8c42000 R15: 00000000ffffffe0 Apr 17 03:04:32 Tower kernel: FS: 0000151d235fe700(0000) GS:ffff88040fd00000(0000) knlGS:0000000000000000 Apr 17 03:04:32 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 17 03:04:32 Tower kernel: CR2: 0000000000000038 CR3: 00000002b096c000 CR4: 00000000000006e0 Apr 17 03:04:32 Tower kernel: Call Trace: Apr 17 03:04:32 Tower kernel: tcp_sendmsg_locked+0xa53/0xbac Apr 17 03:04:32 Tower kernel: tcp_sendmsg+0x23/0x35 Apr 17 03:04:32 Tower kernel: sock_sendmsg+0x14/0x1e Apr 17 03:04:32 Tower kernel: ___sys_sendmsg+0x1ab/0x229 Apr 17 03:04:32 Tower kernel: ? enqueue_task_fair+0x94/0x42c Apr 17 03:04:32 Tower kernel: ? ttwu_do_wakeup.isra.4+0xd/0x87 Apr 17 03:04:32 Tower kernel: ? seccomp_run_filters+0xdc/0x106 Apr 17 03:04:32 Tower kernel: ? wake_up_q+0x2d/0x48 Apr 17 03:04:32 Tower kernel: ? __seccomp_filter+0x26/0x1c5 Apr 17 03:04:32 Tower kernel: ? ep_poll+0x2a9/0x2cb Apr 17 03:04:32 Tower kernel: ? __sys_sendmsg+0x3c/0x5d Apr 17 03:04:32 Tower kernel: __sys_sendmsg+0x3c/0x5d Apr 17 03:04:32 Tower kernel: do_syscall_64+0xfe/0x107 Apr 17 03:04:32 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Apr 17 03:04:32 Tower kernel: RIP: 0033:0x151d30332a6d Apr 17 03:04:32 Tower kernel: RSP: 002b:0000151d235fdb00 EFLAGS: 00000293 ORIG_RAX: 000000000000002e Apr 17 03:04:32 Tower kernel: RAX: ffffffffffffffda RBX: 0000151d235fdb30 RCX: 0000151d30332a6d Apr 17 03:04:32 Tower kernel: RDX: 0000000000004000 RSI: 0000151d235fdb30 RDI: 000000000000006b Apr 17 03:04:32 Tower kernel: RBP: 0000151d235fdb30 R08: 0000151d0fd25d58 R09: 0000151d0fd25d68 Apr 17 03:04:32 Tower kernel: R10: 0000000000000001 R11: 0000000000000293 R12: 0000151d235fe5b8 Apr 17 03:04:32 Tower kernel: R13: 0000000000000004 R14: 0000000000000001 R15: 0000151d0fd25d58 Apr 17 03:04:32 Tower kernel: Code: d0 75 02 31 c0 41 89 f3 41 81 e3 00 80 00 00 74 1a 44 8b 8f 68 05 00 00 41 d1 e9 44 2b 8f 6c 06 00 00 44 03 8f 74 06 00 00 79 10 <80> 48 38 08 8b 8f 6c 06 00 00 89 8f 74 06 00 00 40 80 e6 01 74 Apr 17 03:04:32 Tower kernel: RIP: tcp_push+0x4e/0xee RSP: ffffc900052abc70 Apr 17 03:04:32 Tower kernel: CR2: 0000000000000038 Apr 17 03:04:32 Tower kernel: ---[ end trace 91a87adbe15f760f ]--- Apr 17 03:13:11 Tower root: /mnt/cache: 95.5 GiB (102571241472 bytes) trimmed Apr 17 03:23:10 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout Apr 17 03:40:02 Tower crond[1655]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Apr 17 03:51:35 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout tower-diagnostics-20180417-1212.zip Edited April 17, 2018 by mikefallen Quote Link to comment
JorgeB Posted April 17, 2018 Share Posted April 17, 2018 That's a known kernel bug, upgrading to latest rc will fix it. Quote Link to comment
Recommended Posts
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.