Hide Forgot
i face such stack traces randomly on several virtual servers (HP ProLian, VMware ESxi 5.5 with latest patchlevel) 4.4.7-300.fc23.x86_64 [796968.437315] WARNING: CPU: 2 PID: 0 at net/ipv4/tcp_output.c:1144 tcp_fragment+0x34d/0x370() [796968.437569] Modules linked in: cls_u32 sch_htb nf_nat_ftp nf_conntrack_ftp xt_TCPMSS xt_helper nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_connlimit xt_recent xt_iprange xt_conntrack xt_multiport iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack crct10dif_pclmul crc32_pclmul crc32c_intel vmw_balloon vmxnet3 vmw_vmci vmw_pvscsi [796968.438440] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.7-300.fc23.x86_64 #1 [796968.438571] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015 [796968.438706] 0000000000000286 e740241d1978a322 ffff88013fc838c8 ffffffff813b5f8e [796968.438867] 0000000000000000 ffffffff81af9f9a ffff88013fc83900 ffffffff810a4122 [796968.439027] ffff880069f83200 ffff8800344b3c00 0000000000000058 0000000000000001 [796968.439187] Call Trace: [796968.439257] <IRQ> [<ffffffff813b5f8e>] dump_stack+0x63/0x85 [796968.439372] [<ffffffff810a4122>] warn_slowpath_common+0x82/0xc0 [796968.439447] [<ffffffff810a426a>] warn_slowpath_null+0x1a/0x20 [796968.439521] [<ffffffff816e870d>] tcp_fragment+0x34d/0x370 [796968.439594] [<ffffffff816ddfef>] tcp_mark_head_lost+0x14f/0x240 [796968.439670] [<ffffffff816dedad>] tcp_update_scoreboard+0x5d/0x70 [796968.439746] [<ffffffff816e3bfe>] tcp_fastretrans_alert+0x75e/0xb00 [796968.439822] [<ffffffff816e4f5f>] tcp_ack+0x96f/0x12c0 [796968.439894] [<ffffffff816e5ce5>] tcp_rcv_established+0x105/0x780 [796968.439973] [<ffffffff816f0a25>] tcp_v4_do_rcv+0x145/0x200 [796968.440046] [<ffffffff816f1bd9>] tcp_v4_rcv+0x869/0xa10 [796968.440122] [<ffffffffa001a23d>] ? ipv4_confirm+0x7d/0x100 [nf_conntrack_ipv4] [796968.440244] [<ffffffff816c25f2>] ? nf_iterate+0x62/0x80 [796968.440319] [<ffffffff816cbbf4>] ip_local_deliver_finish+0x94/0x1e0 [796968.440396] [<ffffffff816cbeff>] ip_local_deliver+0x6f/0xe0 [796968.440469] [<ffffffff816cbb60>] ? ip_rcv_finish+0x320/0x320 [796968.440543] [<ffffffff816cb8d2>] ip_rcv_finish+0x92/0x320 [796968.440615] [<ffffffff816cc201>] ip_rcv+0x291/0x3a0 [796968.440689] [<ffffffff810db502>] ? enqueue_entity+0xc72/0xc90 [796968.440763] [<ffffffff816cb840>] ? inet_del_offload+0x40/0x40 [796968.440842] [<ffffffff816898d4>] __netif_receive_skb_core+0x704/0xa60 [796968.440923] [<ffffffff810cceb9>] ? ttwu_do_wakeup+0x19/0xe0 [796968.440997] [<ffffffff816f6ad0>] ? tcp4_gro_receive+0x130/0x1d0 [796968.441071] [<ffffffff81689c48>] __netif_receive_skb+0x18/0x60 [796968.441146] [<ffffffff81689cd0>] netif_receive_skb_internal+0x40/0xb0 [796968.441223] [<ffffffff8168a933>] napi_gro_receive+0xc3/0x120 [796968.441299] [<ffffffffa0022bdc>] vmxnet3_rq_rx_complete+0x4ac/0xc70 [vmxnet3] [796968.441416] [<ffffffffa00234ea>] vmxnet3_poll_rx_only+0x3a/0xb0 [vmxnet3] [796968.441502] [<ffffffff811105e7>] ? hrtimer_start_range_ns+0x1c7/0x3d0 [796968.441581] [<ffffffff8168a18c>] net_rx_action+0x20c/0x340 [796968.441654] [<ffffffff810a8b26>] __do_softirq+0x106/0x2d0 [796968.441727] [<ffffffff810a8ef5>] irq_exit+0x105/0x110 [796968.441809] [<ffffffff817a3b44>] do_IRQ+0x54/0xd0 [796968.441880] [<ffffffff817a1b87>] common_interrupt+0x87/0x87 [796968.441953] <EOI> [<ffffffff810635d6>] ? native_safe_halt+0x6/0x10 [796968.442051] [<ffffffff81021c4e>] default_idle+0x1e/0xe0 [796968.442124] [<ffffffff8102245f>] arch_cpu_idle+0xf/0x20 [796968.442201] [<ffffffff810e65da>] default_idle_call+0x2a/0x40 [796968.442275] [<ffffffff810e6941>] cpu_startup_entry+0x2f1/0x350 [796968.442354] [<ffffffff81050397>] start_secondary+0x157/0x190 [796968.442430] ---[ end trace 8c72d2bad3ba75e4 ]---
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.