LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Ethernet driver crashes with a "Call trace" (http://www.linuxquestions.org/questions/slackware-14/ethernet-driver-crashes-with-a-call-trace-4175430948/)

Unix76 10-07-2012 08:22 AM

Ethernet driver crashes with a "Call trace"
 
Hello, dear friends !

First time here, and as the topic says - because of an issue I can't handle on my own.
I started "experiencing" a very odd and unexplainable to me issue with my ethernet,
it all started a week ago or so - when I am browsing or worse - torrenting,
I loose connectivity completely, and only a reboot is the cure.Until the next time it happens again.

It all goes to the infamous "sky2"-driver for Marvell chip-sets, which could be dated back to 2006 and 2007. Most oddly (and after doing some research),this issue continues to reappear with the 3rd-line of Linux kernels. Or just my side.

A bit more background - I replaced my X48-based mobo an year ago with a brand new P45-based, because I didn't want to fully upgrade my 2009-bought hardware. Although technologically "old", the mobo was brand new and comes with a 3-years warranty.

So, with this mobo, I have been using various distros, among which Debian Wheezy for at least half an year, without any issues. A week ago or so, I started noticing random network connectivity drops which couldn't be solved until a reboot is done.
The first time, when I was browsing the web and noticed that no web-page could be loaded anymore, I went to the terminal, did some pings, traceroutes, brought the ethernet interface up/down until I decided to call my ISP and ask if there were some issues or works at moment causing this.

As you might have guessed, from the ISP-side everything was fine - they were able to trace the network down to their gateway, but not after it, so I was invisible as much as I could not reach the same gateway myself. I started parsing the logs and there I saw many "rx-timeouts",
tx-timeouts", "eth0 hw chksm errors" and "Call traces".

Then I decided to try the just-released Slackware64 14, see if this sky2-driver issue would come here as well, and surely foremost - have some fun with this awesome distro.

And...to my big surprise - same happens here, too.

Here the traces left in the logs :
dmesg :
Code:

[    8.963574] sky2: driver version 1.30
[    8.963701] sky2 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    8.963800] sky2 0000:02:00.0: setting latency timer to 64
[    8.963846] sky2 0000:02:00.0: Yukon-2 EC Ultra chip revision 3
[    8.964013] sky2 0000:02:00.0: irq 46 for MSI/MSI-X


debug log :
Code:

Oct  6 20:00:10  kernel: [    8.281102] sky2 0000:02:00.0: setting latency timer to 64
Oct  6 20:00:10  kernel: [    8.281317] sky2 0000:02:00.0: irq 45 for MSI/MSI-X
Oct  6 20:00:10  kernel: [    8.528464] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
Oct  6 20:00:10  kernel: [    8.528483] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
Oct  6 20:00:10  kernel: [    8.765993] Monitor-Mwait will be used to enter C-1 state
Oct  6 20:00:10  kernel: [    8.766315] Monitor-Mwait will be used to enter C-2 state
Oct  6 20:00:10  kernel: [    8.766349] Monitor-Mwait will be used to enter C-3 state
Oct  6 20:00:10  kernel: [    8.766470] ACPI: acpi_idle registered with cpuidle
Oct  6 20:00:10  kernel: [    9.225625] nvidia 0000:01:00.0: setting latency timer to 64
Oct  6 20:00:24  ntpd[2048]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct  6 20:00:27  ntpd[2048]: new interface(s) found: waking up resolver
Oct  6 20:00:34  kernel: [  41.922027] eth0: no IPv6 routers present
Oct  6 20:03:14  kernel: [  202.172323] ISO 9660 Extensions: Microsoft Joliet Level 3
Oct  6 20:03:14  kernel: [  202.220009] ISO 9660 Extensions: RRIP_1991A
Oct  6 20:21:42  kernel: [ 1309.712138] sky2 0000:02:00.0: eth0: transmit ring 103 .. 126 report=103 done=103
Oct  6 20:21:49  kernel: [ 1316.704032] sky2 0000:02:00.0: eth0: transmit ring 2 .. 24 report=2 done=2
Oct  6 20:21:56  kernel: [ 1323.712045] sky2 0000:02:00.0: eth0: transmit ring 2 .. 23 report=2 done=2
Oct  6 20:22:03  kernel: [ 1330.720026] sky2 0000:02:00.0: eth0: transmit ring 2 .. 23 report=2 done=2
Oct  6 20:22:10  kernel: [ 1337.712034] sky2 0000:02:00.0: eth0: transmit ring 2 .. 24 report=2 done=2
Oct  6 20:22:17  kernel: [ 1344.704031] sky2 0000:02:00.0: eth0: transmit ring 2 .. 24 report=2 done=2
Oct  6 20:22:29  kernel: [ 1356.704030] sky2 0000:02:00.0: eth0: transmit ring 2 .. 25 report=2 done=2
Oct  6 20:22:36  kernel: [ 1363.712032] sky2 0000:02:00.0: eth0: transmit ring 2 .. 23 report=2 done=2
Oct  6 20:22:43  kernel: [ 1370.704032] sky2 0000:02:00.0: eth0: transmit ring 3 .. 25 report=3 done=3
Oct  6 20:22:50  kernel: [ 1377.712047] sky2 0000:02:00.0: eth0: transmit ring 3 .. 24 report=3 done=3
Oct  6 20:22:57  kernel: [ 1384.704029] sky2 0000:02:00.0: eth0: transmit ring 2 .. 25 report=2 done=2
Oct  6 20:23:04  kernel: [ 1391.712031] sky2 0000:02:00.0: eth0: transmit ring 3 .. 24 report=3 done=3


messages :
Code:

Oct  6 20:21:42  kernel: [ 1309.712039] NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
Oct  6 20:21:44  kernel: [ 1311.583193] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  6 20:21:46  kernel: [ 1314.092935] TCP: Possible SYN flooding on port 51000. Sending cookies.  Check SNMP counters.
Oct  6 20:21:51  kernel: [ 1318.446646] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  6 20:21:58  kernel: [ 1325.381255] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  6 20:22:05  kernel: [ 1332.407574] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  6 20:22:12  kernel: [ 1339.638141] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  6 20:22:19  kernel: [ 1346.776948] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both

Port 51000 is used when torrenting


syslog
Code:

Oct  6 20:21:32  kernel: [ 1300.142001] sky2 0000:02:00.0: error interrupt status=0x80000000
Oct  6 20:21:32  kernel: [ 1300.142008] sky2 0000:02:00.0: PCI hardware error (0x2010)
Oct  6 20:21:42  kernel: [ 1309.712012] ------------[ cut here ]------------
Oct  6 20:21:42  kernel: [ 1309.712036] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x220/0x230()
Oct  6 20:21:42  kernel: [ 1309.712037] Hardware name: P5Q3 DELUXE
Oct  6 20:21:42  kernel: [ 1309.712040] Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 xt_limit xt_multiport xt_tcpudp ipt_ULOG xt_conntrack xt_recent nf_conntrack_proto_udplite nf_conntrack_ftp nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables lp ppdev parport_pc parport fuse hid_apple nvidia(P) hid_a4tech usbhid hid snd_hda_codec_analog asus_atk0110 processor button thermal_sys hwmon intel_agp intel_gtt agpgart i2c_i801 i2c_core snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore sky2 psmouse serio_raw evdev loop
Oct  6 20:21:42  kernel: [ 1309.712072] Pid: 0, comm: swapper/2 Tainted: P          O 3.2.29 #2
Oct  6 20:21:42  kernel: [ 1309.712074] Call Trace:
Oct  6 20:21:42  kernel: [ 1309.712075]  <IRQ>  [<ffffffff8105340f>] warn_slowpath_common+0x7f/0xc0
Oct  6 20:21:42  kernel: [ 1309.712083]  [<ffffffff8101ee8d>] ? lapic_next_event+0x1d/0x30
Oct  6 20:21:42  kernel: [ 1309.712085]  [<ffffffff81053506>] warn_slowpath_fmt+0x46/0x50
Oct  6 20:21:42  kernel: [ 1309.712088]  [<ffffffff81a46700>] dev_watchdog+0x220/0x230
Oct  6 20:21:42  kernel: [ 1309.712091]  [<ffffffff81a464e0>] ? dev_graft_qdisc+0x90/0x90
Oct  6 20:21:42  kernel: [ 1309.712093]  [<ffffffff810624bc>] run_timer_softirq+0x14c/0x350
Oct  6 20:21:42  kernel: [ 1309.712096]  [<ffffffff8105a475>] __do_softirq+0xb5/0x1c0
Oct  6 20:21:42  kernel: [ 1309.712099]  [<ffffffff81b311ac>] call_softirq+0x1c/0x30
Oct  6 20:21:42  kernel: [ 1309.712101]  [<ffffffff81003d85>] do_softirq+0x55/0x90
Oct  6 20:21:42  kernel: [ 1309.712103]  [<ffffffff8105a7fd>] irq_exit+0xad/0xc0
Oct  6 20:21:42  kernel: [ 1309.712106]  [<ffffffff81b31893>] do_IRQ+0x63/0xe0
Oct  6 20:21:42  kernel: [ 1309.712108]  [<ffffffff81b2eb2b>] common_interrupt+0x6b/0x6b
Oct  6 20:21:42  kernel: [ 1309.712110]  <EOI>  [<ffffffffa00d8c83>] ? acpi_idle_enter_simple+0xc5/0x102 [processor]
Oct  6 20:21:42  kernel: [ 1309.712117]  [<ffffffffa00d8c7e>] ? acpi_idle_enter_simple+0xc0/0x102 [processor]
Oct  6 20:21:42  kernel: [ 1309.712120]  [<ffffffffa00d8dad>] acpi_idle_enter_bm+0xed/0x257 [processor]
Oct  6 20:21:42  kernel: [ 1309.712124]  [<ffffffff819f6939>] cpuidle_idle_call+0xc9/0x230
Oct  6 20:21:42  kernel: [ 1309.712126]  [<ffffffff8100096a>] cpu_idle+0xaa/0x110
Oct  6 20:21:42  kernel: [ 1309.712129]  [<ffffffff81b149da>] start_secondary+0x1cf/0x1d6
Oct  6 20:21:42  kernel: [ 1309.712131] ---[ end trace 2a8fd3166b56b91f ]---
Oct  6 20:21:42  kernel: [ 1309.712134] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:21:49  kernel: [ 1316.704024] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:21:56  kernel: [ 1323.712037] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:03  kernel: [ 1330.720018] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:10  kernel: [ 1337.712027] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:17  kernel: [ 1344.704023] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:29  kernel: [ 1356.704023] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:36  kernel: [ 1363.712025] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:43  kernel: [ 1370.704024] sky2 0000:02:00.0: eth0: tx timeout
Oct  6 20:22:50  kernel: [ 1377.712040] sky2 0000:02:00.0: eth0: tx timeout



Here the hardware and module-related info :
Code:

3.2.29 #2 SMP Mon Sep 17 14:19:22 CDT 2012 x86_64 Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz GenuineIntel GNU/Linux

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
        Subsystem: ASUSTeK Computer Inc. Device 81f8
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 46
        Region 0: Memory at feafc000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at d800 [size=256]
        Expansion ROM at feac0000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
                Product Name: Marvell Yukon 88E8056 Gigabit Ethernet Controller
                Read-only fields:
                        [PN] Part number: Yukon 88E8056
                        [EC] Engineering changes: Rev. 1.2
                        [MN] Manufacture ID: 4d 61 72 76 65 6c 6c
                        [SN] Serial number: AbCdEfG6B049F
                        [CP] Extended capability: 01 10 cc 03
                        [RV] Reserved: checksum good, 9 byte(s) reserved
                Read/write fields:
                        [RW] Read-write area: 121 byte(s) free
                End
        Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee0f00c  Data: 41a1
        Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
                DevCap:        MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl:        Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta:        CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
                LnkCap:        Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 unlimited
                        ClockPM+ Surprise- LLActRep- BwNot-
                LnkCtl:        ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta:        Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:        DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:        DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt:        DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:        RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                CEMsk:        RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap:        First Error Pointer: 1f, GenCap- CGenEn- ChkCap- ChkEn-
        Kernel driver in use: sky2


What I have tried until now :
- bringing the interface up/down
- unloading, reloading the module with and without /etc/rc.d/rc.inet1 eth0 restart
- ethtool -A eth0 autoneg off rx on tx on
- ethtool -s eth0 speed 100 duplex half autoneg off
- ethtool -s eth0 speed 100 duplex full
- ethtool -K eth0 rx off tx off
- rmmod sky 2 && modprobe sky2 disable_msi=1


Nothing helps :(


The issue with this sky2-driver has been known and around since 2006, with various distros.
How come this happens again, just at once, and with no obvious reason ?

I do hope it would not start smelling like a hardware fault of some sort
and will greatly appreciate any help in resolving this !


Thank you all in advance,

Best regards

Unix76 10-07-2012 08:53 AM

Here excerpts from the kernel log in Debian Wheezy,
with the difference that the call trace also "mentions" the conntrack module :
Code:

Oct  1 19:39:07  kernel: [  922.177676] sky2 0000:02:00.0: error interrupt status=0x80000000
Oct  1 19:39:07  kernel: [  922.177684] sky2 0000:02:00.0: PCI hardware error (0x2010)
Oct  1 19:39:14  kernel: [  928.816029] ------------[ cut here ]------------
Oct  1 19:39:14  kernel: [  928.816038] WARNING: at /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/net/sched/sch_generic.c:255 dev_watchdog+0xe9/0x148()
Oct  1 19:39:14  kernel: [  928.816040] Hardware name: P5Q3 DELUXE
Oct  1 19:39:14  kernel: [  928.816042] NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
Oct  1 19:39:14  kernel: [  928.816044] Modules linked in: nls_utf8 isofs udf crc_itu_t ip6table_filter ip6_tables ebtable_nat ebtables cpufreq_powersave cpufreq_conservative cpufreq_stats cpufreq_userspace pci_stub vboxpci(O) vboxnetadp(O) binfmt_misc vboxnetflt(O) vboxdrv(O) xt_limit xt_recent xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport xt_conntrack nf_conntrack iptable_filter ip_tables x_tables jfs loop kvm_intel kvm nvidia(P) snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq i2c_i801 i2c_core acpi_cpufreq hid_a4tech snd_seq_device iTCO_wdt iTCO_vendor_support evdev psmouse coretemp asus_atk0110 pcspkr serio_raw mperf snd_timer snd button processor soundcore thermal_sys ext4 crc16 jbd2 mbcache dm_mod sg sd_mod crc_t10dif sr_mod cdrom ata_generic hid_apple usbhid hid ahci libahci uhci_hcd pata_jmicron sky2 libata scsi_mod ehci_hcd usbcore usb_common [last unloaded: scsi_wait_scan]
Oct  1 19:39:14  kernel: [  928.816114] Pid: 0, comm: swapper/1 Tainted: P          O 3.2.0-3-amd64 #1
Oct  1 19:39:14  kernel: [  928.816117] Call Trace:
Oct  1 19:39:14  kernel: [  928.816118]  <IRQ>  [<ffffffff81046901>] ? warn_slowpath_common+0x78/0x8c
Oct  1 19:39:14  kernel: [  928.816127]  [<ffffffff810469ad>] ? warn_slowpath_fmt+0x45/0x4a
Oct  1 19:39:14  kernel: [  928.816130]  [<ffffffff812a3559>] ? netif_tx_lock+0x40/0x72
Oct  1 19:39:14  kernel: [  928.816136]  [<ffffffff812a36ba>] ? dev_watchdog+0xe9/0x148
Oct  1 19:39:14  kernel: [  928.816139]  [<ffffffff81051f74>] ? run_timer_softirq+0x19a/0x261
Oct  1 19:39:14  kernel: [  928.816143]  [<ffffffff812a35d1>] ? netif_tx_unlock+0x46/0x46
Oct  1 19:39:14  kernel: [  928.816147]  [<ffffffff81065ad7>] ? timekeeping_get_ns+0xd/0x2a
Oct  1 19:39:14  kernel: [  928.816151]  [<ffffffff8104bee8>] ? __do_softirq+0xb9/0x177
Oct  1 19:39:14  kernel: [  928.816155]  [<ffffffff81351eec>] ? call_softirq+0x1c/0x30
Oct  1 19:39:14  kernel: [  928.816160]  [<ffffffff8100f8e5>] ? do_softirq+0x3c/0x7b
Oct  1 19:39:14  kernel: [  928.816163]  [<ffffffff8104c150>] ? irq_exit+0x3c/0x9a
Oct  1 19:39:14  kernel: [  928.816167]  [<ffffffff81024208>] ? smp_apic_timer_interrupt+0x74/0x82
Oct  1 19:39:14  kernel: [  928.816170]  [<ffffffff8135075e>] ? apic_timer_interrupt+0x6e/0x80
Oct  1 19:39:14  kernel: [  928.816172]  <EOI>  [<ffffffffa00f4398>] ? arch_local_irq_enable+0x4/0x8 [processor]
Oct  1 19:39:14  kernel: [  928.816184]  [<ffffffffa00f4f18>] ? acpi_idle_enter_bm+0x220/0x262 [processor]
Oct  1 19:39:14  kernel: [  928.816191]  [<ffffffff8126cbff>] ? cpuidle_idle_call+0xec/0x179
Oct  1 19:39:14  kernel: [  928.816194]  [<ffffffff8100d248>] ? cpu_idle+0xa5/0xf2
Oct  1 19:39:14  kernel: [  928.816198]  [<ffffffff8107070e>] ? arch_local_irq_restore+0x2/0x8
Oct  1 19:39:14  kernel: [  928.816202]  [<ffffffff8133d11a>] ? start_secondary+0x1d5/0x1db
Oct  1 19:39:14  kernel: [  928.816204] ---[ end trace 2ae499571589eee4 ]---
Oct  1 19:39:14  kernel: [  928.816208] sky2 0000:02:00.0: eth0: tx timeout
Oct  1 19:39:14  kernel: [  928.816214] sky2 0000:02:00.0: eth0: transmit ring 27 .. 52 report=27 done=27
Oct  1 19:39:16  kernel: [  930.577238] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  1 19:39:21  kernel: [  935.808040] sky2 0000:02:00.0: eth0: tx timeout
Oct  1 19:39:21  kernel: [  935.808048] sky2 0000:02:00.0: eth0: transmit ring 3 .. 26 report=3 done=3
Oct  1 19:39:23  kernel: [  937.532358] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  1 19:39:28  kernel: [  942.816030] sky2 0000:02:00.0: eth0: tx timeout
Oct  1 19:39:28  kernel: [  942.816038] sky2 0000:02:00.0: eth0: transmit ring 3 .. 24 report=3 done=3
Oct  1 19:39:30  kernel: [  944.503606] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Oct  1 19:39:35  kernel: [  949.808038] sky2 0000:02:00.0: eth0: tx timeout

Code:

Oct  1 19:56:08  kernel: [  110.736684]  <IRQ>  [<ffffffff8128aedf>] ? netdev_rx_csum_fault+0x29/0x31
Oct  1 19:56:08  kernel: [  110.736697]  [<ffffffff812854f4>] ? __skb_checksum_complete_head+0x41/0x53
Oct  1 19:56:08  kernel: [  110.736710]  [<ffffffffa0d765fd>] ? tcp_error+0x100/0x1ab [nf_conntrack]
Oct  1 19:56:08  kernel: [  110.736714]  [<ffffffff812c732d>] ? tcp_cwnd_test+0x2c/0x41
Oct  1 19:56:08  kernel: [  110.736717]  [<ffffffff812c93e4>] ? tcp_write_xmit+0x460/0x7a1
Oct  1 19:56:08  kernel: [  110.736724]  [<ffffffffa0d73673>] ? nf_conntrack_in+0xfa/0x607 [nf_conntrack]
Oct  1 19:56:08  kernel: [  110.736727]  [<ffffffff812c37dc>] ? tcp_data_snd_check+0x38/0xfb
Oct  1 19:56:08  kernel: [  110.736730]  [<ffffffff812c7075>] ? tcp_rcv_established+0x4f0/0x549
Oct  1 19:56:08  kernel: [  110.736735]  [<ffffffff812ad765>] ? nf_iterate+0x41/0x77
Oct  1 19:56:08  kernel: [  110.736739]  [<ffffffff812b3278>] ? inet_del_protocol+0x27/0x27
Oct  1 19:56:08  kernel: [  110.736742]  [<ffffffff812ad803>] ? nf_hook_slow+0x68/0x101
Oct  1 19:56:08  kernel: [  110.736745]  [<ffffffff812b3278>] ? inet_del_protocol+0x27/0x27
Oct  1 19:56:08  kernel: [  110.736748]  [<ffffffff812b3278>] ? inet_del_protocol+0x27/0x27
Oct  1 19:56:08  kernel: [  110.736751]  [<ffffffff812b3585>] ? NF_HOOK.constprop.9+0x3c/0x56
Oct  1 19:56:08  kernel: [  110.736755]  [<ffffffff8128aa0b>] ? __netif_receive_skb+0x3d9/0x41f
Oct  1 19:56:08  kernel: [  110.736758]  [<ffffffff8128c3b1>] ? netif_receive_skb+0x63/0x69
Oct  1 19:56:08  kernel: [  110.736761]  [<ffffffff8128c883>] ? napi_gro_receive+0x1d/0x2b
Oct  1 19:56:08  kernel: [  110.736764]  [<ffffffff8128c42d>] ? napi_skb_finish+0x1c/0x31
Oct  1 19:56:08  kernel: [  110.736781]  [<ffffffffa0159603>] ? sky2_poll+0x79c/0x9c6 [sky2]
Oct  1 19:56:08  kernel: [  110.736786]  [<ffffffff81065ed9>] ? ktime_get+0x50/0x86
Oct  1 19:56:08  kernel: [  110.736789]  [<ffffffff8128c9a1>] ? net_rx_action+0xa1/0x1af
Oct  1 19:56:08  kernel: [  110.736793]  [<ffffffff8104bee8>] ? __do_softirq+0xb9/0x177
Oct  1 19:56:08  kernel: [  110.736797]  [<ffffffff81065ad7>] ? timekeeping_get_ns+0xd/0x2a
Oct  1 19:56:08  kernel: [  110.736801]  [<ffffffff81351eec>] ? call_softirq+0x1c/0x30
Oct  1 19:56:08  kernel: [  110.736806]  [<ffffffff8100f8e5>] ? do_softirq+0x3c/0x7b
Oct  1 19:56:08  kernel: [  110.736809]  [<ffffffff8104c150>] ? irq_exit+0x3c/0x9a
Oct  1 19:56:08  kernel: [  110.736812]  [<ffffffff8100f615>] ? do_IRQ+0x82/0x98
Oct  1 19:56:08  kernel: [  110.736816]  [<ffffffff8134afae>] ? common_interrupt+0x6e/0x6e
Oct  1 19:56:08  kernel: [  110.736818]  <EOI>  [<ffffffffa01b9398>] ? arch_local_irq_enable+0x4/0x8 [processor]
Oct  1 19:56:08  kernel: [  110.736831]  [<ffffffffa01ba020>] ? acpi_idle_enter_simple+0xc6/0x102 [processor]
Oct  1 19:56:08  kernel: [  110.736837]  [<ffffffffa01b9ddb>] ? acpi_idle_enter_bm+0xe3/0x262 [processor]
Oct  1 19:56:08  kernel: [  110.736844]  [<ffffffff8126cbff>] ? cpuidle_idle_call+0xec/0x179
Oct  1 19:56:08  kernel: [  110.736847]  [<ffffffff8100d248>] ? cpu_idle+0xa5/0xf2
Oct  1 19:56:08  kernel: [  110.736851]  [<ffffffff816aab33>] ? start_kernel+0x3b3/0x3be
Oct  1 19:56:08  kernel: [  110.736854]  [<ffffffff816aa140>] ? early_idt_handlers+0x140/0x140
Oct  1 19:56:08  kernel: [  110.736857]  [<ffffffff816aa3c4>] ? x86_64_start_kernel+0x104/0x111
Oct  1 19:56:10  kernel: [  113.144116] eth0: hw csum failure.
Oct  1 19:56:10  kernel: [  113.144121] Pid: 0, comm: swapper/1 Tainted: P          O 3.2.0-3-amd64 #1


I use same iptables ruleset in both Debian and Slackware64, as the connection tracking is concerned.

Unix76 10-10-2012 07:59 AM

Well, after some testing, it does seem to be a hardware-fault, after all.
I took the other port, which is Marvell 88E8001 and uses the skge-driver
and now networking seems ok.


All times are GMT -5. The time now is 09:34 PM.