Description of problem: Network is disconnected, when the problems occur Version-Release number of selected component (if applicable): kernel-2.6.29.4-167.fc11.x86_64 How reproducible: Usually when there is a high network traffic Steps to Reproduce: 1. Download a big file 2. Wait for a while Actual results: The following error messages are emitted and the network is disconnected. Jul 28 15:31:08 bb229 kernel: sky2 eth0: rx error, status 0xdbc4dbc4 length 0 Jul 28 15:32:42 bb229 kernel: eth0: hw csum failure. Jul 28 15:32:42 bb229 kernel: Pid: 18722, comm: X Not tainted 2.6.29.6-213.fc11.x86_64 #1 Jul 28 15:32:42 bb229 kernel: Call Trace: Jul 28 15:32:42 bb229 kernel: <IRQ> [<ffffffff813106a1>] netdev_rx_csum_fault+0x3b/0x40 Jul 28 15:32:42 bb229 kernel: [<ffffffff8130b033>] __skb_checksum_complete_head+0x51/0x65 Jul 28 15:32:42 bb229 kernel: [<ffffffff8130b058>] __skb_checksum_complete+0x11/0x13 Jul 28 15:32:42 bb229 kernel: [<ffffffff8136e4cd>] nf_ip_checksum+0xdd/0xe3 Jul 28 15:32:42 bb229 kernel: [<ffffffff81331a40>] udp_error+0x137/0x191 Jul 28 15:32:42 bb229 kernel: [<ffffffff8132df88>] nf_conntrack_in+0x130/0x545 Jul 28 15:32:42 bb229 kernel: [<ffffffff81039ca7>] ? check_preempt_wakeup+0x196/0x1de Jul 28 15:32:42 bb229 kernel: [<ffffffff813abce2>] ? _spin_lock+0xe/0x11 Jul 28 15:32:42 bb229 kernel: [<ffffffff810398f1>] ? account_group_exec_runtime+0x48/0x52 Jul 28 15:32:42 bb229 kernel: [<ffffffff8136ea25>] ipv4_conntrack_in+0x21/0x23 Jul 28 15:32:42 bb229 kernel: [<ffffffff8132b964>] nf_iterate+0x46/0x89 Jul 28 15:32:42 bb229 kernel: [<ffffffff813395ce>] ? ip_rcv_finish+0x0/0x357 Jul 28 15:32:42 bb229 kernel: [<ffffffff8132ba11>] nf_hook_slow+0x6a/0xcb Jul 28 15:32:42 bb229 kernel: [<ffffffff813395ce>] ? ip_rcv_finish+0x0/0x357 Jul 28 15:32:42 bb229 kernel: [<ffffffff81339b4a>] ip_rcv+0x225/0x270 Jul 28 15:32:42 bb229 kernel: [<ffffffff81310096>] netif_receive_skb+0x3ba/0x3df Jul 28 15:32:42 bb229 kernel: [<ffffffffa00a0daf>] sky2_poll+0x7c1/0x9ec [sky2] Jul 28 15:32:42 bb229 kernel: [<ffffffff8130e599>] net_rx_action+0xb7/0x1b1 Jul 28 15:32:42 bb229 kernel: [<ffffffff8104df6f>] __do_softirq+0x94/0x155 Jul 28 15:32:42 bb229 kernel: [<ffffffffa009faa2>] ? napi_schedule+0x20/0x22 [sky2] Jul 28 15:32:42 bb229 kernel: [<ffffffff8101274c>] call_softirq+0x1c/0x30 Jul 28 15:32:42 bb229 kernel: [<ffffffff810138ce>] do_softirq+0x52/0xb9 Jul 28 15:32:42 bb229 kernel: [<ffffffff8104db92>] irq_exit+0x53/0x90 Jul 28 15:32:42 bb229 kernel: [<ffffffff81013bf7>] do_IRQ+0x12c/0x151 Jul 28 15:32:42 bb229 kernel: [<ffffffff81011e93>] ret_from_intr+0x0/0x2e Jul 28 15:32:42 bb229 kernel: <EOI> <3>eth0: hw csum failure. Expected results: No kernel errors messages and interruption of service Additional info: I have to issue "/etc/init.d/network restart" to restore my internet connection. This is an old sin, since fedora 9 or 10. It can be reproduced easily. Sometimes works fine some others not.
Well, the last time I had observed such kind of problems was in Aug 6 2009 16:20:17, according to my logs. I haven't experience any problem since then. I think we could safely conclude that it has been fixed somehow on newer kernel versions.
For reference kernel-2.6.29.6-217.2.8.fc11.x86_64 was the latest kernel installed on my system where no problems observed since then according to my logs.
It seems that the problem has returned in kernel-2.6.31.9-174.fc12.x86_64. Feb 16 11:46:10 bb229 kernel: eth0: hw csum failure. Feb 16 11:46:10 bb229 kernel: Pid: 0, comm: swapper Not tainted 2.6.31.12-174.2. 3.fc12.x86_64 #1 Feb 16 11:46:10 bb229 kernel: Call Trace: Feb 16 11:46:10 bb229 kernel: <IRQ> [<ffffffff8137ef30>] netdev_rx_csum_fault+0 x3b/0x3f Feb 16 11:46:10 bb229 kernel: [<ffffffff81378f43>] __skb_checksum_complete_head+ 0x51/0x65 Feb 16 11:46:10 bb229 kernel: [<ffffffff81378f68>] __skb_checksum_complete+0x11/ 0x13 Feb 16 11:46:10 bb229 kernel: [<ffffffff813e10f1>] nf_ip_checksum+0xdd/0xe3 Feb 16 11:46:10 bb229 kernel: [<ffffffff813a2754>] udp_error+0x137/0x191 Feb 16 11:46:10 bb229 kernel: [<ffffffff8139e1d9>] nf_conntrack_in+0x17a/0x86e Feb 16 11:46:10 bb229 kernel: [<ffffffff810f1bad>] ? virt_to_head_page+0xe/0x2f Feb 16 11:46:10 bb229 kernel: [<ffffffff813766fa>] ? __kfree_skb+0x7d/0x81 Feb 16 11:46:10 bb229 kernel: [<ffffffff81376797>] ? kfree_skb+0x6a/0x72 Feb 16 11:46:10 bb229 kernel: [<ffffffff813e1710>] ipv4_conntrack_in+0x21/0x23 Feb 16 11:46:10 bb229 kernel: [<ffffffff8139b3b6>] nf_iterate+0x46/0x89 Feb 16 11:46:10 bb229 kernel: [<ffffffff813aa936>] ? ip_rcv_finish+0x0/0x3ba Feb 16 11:46:10 bb229 kernel: [<ffffffff8139b463>] nf_hook_slow+0x6a/0xcb Feb 16 11:46:10 bb229 kernel: [<ffffffff813aa936>] ? ip_rcv_finish+0x0/0x3ba Feb 16 11:46:10 bb229 kernel: [<ffffffff813aaf6c>] ip_rcv+0x27c/0x2c9 Feb 16 11:46:10 bb229 kernel: [<ffffffff8137e691>] netif_receive_skb+0x402/0x427 Feb 16 11:46:10 bb229 kernel: [<ffffffff8137e81b>] napi_skb_finish+0x29/0x3d Feb 16 11:46:10 bb229 kernel: [<ffffffff8137ec7a>] napi_gro_receive+0x2f/0x34 Feb 16 11:46:10 bb229 kernel: [<ffffffffa011c0cb>] sky2_poll+0x811/0xa5f [sky2] Feb 16 11:46:10 bb229 kernel: [<ffffffff8101831c>] ? native_sched_clock+0x2d/0x6 1 Feb 16 11:46:10 bb229 kernel: [<ffffffff81017bc1>] ? read_tsc+0x9/0x1b Feb 16 11:46:10 bb229 kernel: [<ffffffff8137edb0>] net_rx_action+0xaf/0x1c9 Feb 16 11:46:10 bb229 kernel: [<ffffffff8137c5fe>] ? list_add_tail+0x15/0x17 Feb 16 11:46:10 bb229 kernel: [<ffffffff81057630>] __do_softirq+0xdd/0x1ad Feb 16 11:46:10 bb229 kernel: [<ffffffff81026966>] ? apic_write+0x16/0x18 Feb 16 11:46:10 bb229 kernel: [<ffffffff81012eac>] call_softirq+0x1c/0x30 Feb 16 11:46:10 bb229 kernel: [<ffffffff810143fb>] do_softirq+0x47/0x8d Feb 16 11:46:10 bb229 kernel: [<ffffffff81057342>] irq_exit+0x44/0x86 Feb 16 11:46:10 bb229 kernel: [<ffffffff814215d5>] do_IRQ+0xa5/0xbc Feb 16 11:46:10 bb229 kernel: [<ffffffff810126d3>] ret_from_intr+0x0/0x11 Feb 16 11:46:10 bb229 kernel: <EOI> [<ffffffff8101907f>] ? mwait_idle+0x91/0xae Feb 16 11:46:10 bb229 kernel: [<ffffffff81019021>] ? mwait_idle+0x33/0xae Feb 16 11:46:10 bb229 kernel: [<ffffffff8141fc39>] ? atomic_notifier_call_chain+ 0x13/0x15 Feb 16 11:46:10 bb229 kernel: [<ffffffff81010bb8>] ? enter_idle+0x25/0x27 Feb 16 11:46:10 bb229 kernel: [<ffffffff81010c60>] ? cpu_idle+0xa6/0xe9 Feb 16 11:46:10 bb229 kernel: [<ffffffff81408697>] ? rest_init+0x6b/0x6d Feb 16 11:46:10 bb229 kernel: [<ffffffff81716dc7>] ? start_kernel+0x3ef/0x3fa Feb 16 11:46:10 bb229 kernel: [<ffffffff817162a1>] ? x86_64_start_reservations+0xac/0xb0 Feb 16 11:46:10 bb229 kernel: [<ffffffff8171639d>] ? x86_64_start_kernel+0xf8/0x107
This is a bug reported and solved on older version. For version 12 a new bug 574455 has been created. It can be safely closed with a fixed status.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.