[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1177756242.15104.14.camel@lasse>
Date: Sat, 28 Apr 2007 12:30:42 +0200
From: Håkan Lindqvist <lindqvist@...star.se>
To: linux-kernel@...r.kernel.org
Subject: 2.6.21: sky2 "hw csum failure" problem
I have a machine with an onboard sky2 NIC:
0000:03:00.0 0200: 11ab:4343 (rev 14)
0000:03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8062
PCI-E IPMI Gigabit Ethernet Controller (rev 14)
Subsystem: ASUSTeK Computer Inc.: Unknown device 81da
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 0x04 (16 bytes)
Interrupt: pin A routed to IRQ 219
Region 0: Memory at ff7fc000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at b800 [size=256]
Expansion ROM at ff7c0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot
+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1
Enable+
Address: 00000000fee0100c Data: 414a
Capabilities: [e0] #10 [0011]
Detected as:
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
sky2 0000:03:00.0: v1.14 addr 0xff7fc000 irq 16 Yukon-XL (0xb3) rev 1
sky2 eth0: addr 00:15:f2:d3:62:e9
sky2 eth1: addr 00:15:f2:d3:62:ea
sky2 eth0: enabling interface
sky2 eth0: ram buffer 96K
sky2 eth1: enabling interface
sky2 eth1: ram buffer 96K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
It works normally to start with, but after some random time (presumably
when network traffic rises), no further traffic gets through.
In dmesg there are, at that point, lots of "eth0: hw csum failure."
messages with stack traces. (Log attached, unfortunately this is the
last part of the log, not including when the problem first appeared.)
I don't think this problem is actually new in 2.6.21, but what I do know
is that 2.6.16.1 is a known working kernel on this machine.
Regards,
Håkan Lindqvist
(I am not subscribed to the list, so I would appreciate if you CC:ed me
on any replies.)
View attachment "sky2-2.6.21.log" of type "text/x-log" (11951 bytes)
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (3165 bytes)
Powered by blists - more mailing lists