Leondre Posted March 20, 2018 Share Posted March 20, 2018 Anyone know what this is and what I would need to do to fix it? Mar 20 09:46:37 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 Mar 20 09:46:37 Tower kernel: IP: tcp_push+0x4e/0xee Mar 20 09:46:37 Tower kernel: PGD 800000038777e067 P4D 800000038777e067 PUD 385c36067 PMD 0 Mar 20 09:46:37 Tower kernel: Oops: 0002 [#1] PREEMPT SMP PTI Mar 20 09:46:37 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap 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 bonding e1000e igb ptp pps_core i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd mpt3sas intel_cstate intel_uncore ahci libahci i2c_i801 intel_rapl_perf i2c_core raid_class scsi_transport_sas video backlight thermal acpi_pad button fan [last unloaded: pps_core] Mar 20 09:46:37 Tower kernel: CPU: 6 PID: 29298 Comm: docker-proxy Not tainted 4.14.26-unRAID #1 Mar 20 09:46:37 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z270N-WIFI/Z270N-WIFI-CF, BIOS F5 07/06/2017 Mar 20 09:46:37 Tower kernel: task: ffff8803f1b52b80 task.stack: ffffc90002134000 Mar 20 09:46:37 Tower kernel: RIP: 0010:tcp_push+0x4e/0xee Mar 20 09:46:37 Tower kernel: RSP: 0018:ffffc90002137d30 EFLAGS: 00010246 Mar 20 09:46:37 Tower kernel: RAX: 0000000000000000 RBX: 00000000000005a8 RCX: 0000000000000001 Mar 20 09:46:37 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000040 RDI: ffff8803efa4cc80 Mar 20 09:46:37 Tower kernel: RBP: ffff8803f1b534a0 R08: 0000000000003890 R09: ffffffff8151db5d Mar 20 09:46:37 Tower kernel: R10: ffff8803efa4cdd8 R11: 0000000000000000 R12: ffff8803efa4cc80 Mar 20 09:46:37 Tower kernel: R13: 0000000000000000 R14: ffff88002e81e000 R15: 00000000ffffffe0 Mar 20 09:46:37 Tower kernel: FS: 000000c420056090(0000) GS:ffff88042ed80000(0000) knlGS:0000000000000000 Mar 20 09:46:37 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 20 09:46:37 Tower kernel: CR2: 0000000000000038 CR3: 000000039335a002 CR4: 00000000003626e0 Mar 20 09:46:37 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 20 09:46:37 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 20 09:46:37 Tower kernel: Call Trace: Mar 20 09:46:37 Tower kernel: tcp_sendmsg_locked+0xa53/0xbac Mar 20 09:46:37 Tower kernel: tcp_sendmsg+0x23/0x35 Mar 20 09:46:37 Tower kernel: sock_sendmsg+0x14/0x1e Mar 20 09:46:37 Tower kernel: sock_write_iter+0x70/0x86 Mar 20 09:46:37 Tower kernel: __vfs_write+0xe1/0x109 Mar 20 09:46:37 Tower kernel: vfs_write+0xc3/0x166 Mar 20 09:46:37 Tower kernel: SyS_write+0x48/0x81 Mar 20 09:46:37 Tower kernel: do_syscall_64+0xfe/0x107 Mar 20 09:46:37 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 20 09:46:37 Tower kernel: RIP: 0033:0x46f214 Mar 20 09:46:37 Tower kernel: RSP: 002b:000000c4204b4ab8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 Mar 20 09:46:37 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000046f214 Mar 20 09:46:37 Tower kernel: RDX: 0000000000008000 RSI: 000000c4205d4000 RDI: 0000000000000009 Mar 20 09:46:37 Tower kernel: RBP: 000000c4204b4b08 R08: 0000000000000000 R09: 0000000000000000 Mar 20 09:46:37 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Mar 20 09:46:37 Tower kernel: R13: 0000000000000000 R14: 0000000000455570 R15: 0000000000000000 Mar 20 09:46:37 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 Mar 20 09:46:37 Tower kernel: RIP: tcp_push+0x4e/0xee RSP: ffffc90002137d30 Mar 20 09:46:37 Tower kernel: CR2: 0000000000000038 Mar 20 09:46:37 Tower kernel: ---[ end trace b00939d58195ba58 ]--- tower-diagnostics-20180320-1059.zip Quote Link to comment
JorgeB Posted March 20, 2018 Share Posted March 20, 2018 Several users have the same error with v6.5, possibly plex related?? If it more than the call trace, i.e., something is not working correctly you can downgrade to v6.4.1 Quote Link to comment
Leondre Posted March 20, 2018 Author Share Posted March 20, 2018 Could be plex related, though nothing is not working as far as I can tell. Quote Link to comment
JorgeB Posted March 20, 2018 Share Posted March 20, 2018 Looks like it's a kernel bug: https://lime-technology.com/forums/topic/70095-unraid-os-version-650-stable-release-available/?do=findComment&comment=642386 Quote Link to comment
andreidelait Posted March 20, 2018 Share Posted March 20, 2018 In this case doesn't look to be plex Mar 20 09:46:37 Tower kernel: CPU: 6 PID: 29298 Comm: docker-proxy Not tainted 4.14.26-unRAID #1 This is the line where you can identify what docker stopped working. It is a bug present in 6.5.0 that may be kernel related. I'll have a look in the thread posted above. 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.