netdev - Problem with sky2 (Yukon-EC)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0806302104141.4958@bizon.gios.gov.pl>
Date:	Mon, 30 Jun 2008 21:28:15 +0200 (CEST)
From:	Krzysztof Oledzki <olel@....pl>
To:	Stephen Hemminger <shemminger@...tta.com>
cc:	netdev@...r.kernel.org
Subject: Problem with sky2 (Yukon-EC)

Hello,

I have several servers with sky2 NIC (bonding + vlan):

sky2 0000:02:00.0: v1.20 addr 0xcfffc000 irq 17 Yukon-EC (0xb6) rev 1

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15)
         Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit Ethernet controller PCIe (Asus)
         Flags: bus master, fast devsel, latency 0, IRQ 221
         Memory at cfffc000 (64-bit, non-prefetchable) [size=16K]
         I/O ports at d800 [size=256]
         Expansion ROM at cffc0000 [disabled] [size=128K]
         Capabilities: [48] Power Management version 2
         Capabilities: [50] Vital Product Data <?>
         Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
         Capabilities: [e0] Express Legacy Endpoint, MSI 00
         Kernel driver in use: sky2

All server suffer the same problem - once about two-three weeks network 
dies completely (log from 2.6.24):

sky2 eth1: hung mac 7:19 fifo 0 (91:101)
sky2 eth1: receiver hang detected
sky2 eth1: disabling interface
sky2 eth1: enabling interface
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: now running without any active interface !
sky2 eth1: Link is up at 100 Mbps, full duplex, flow control both
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
sky2 eth1: rx length error: status 0x402500 length 64
*last message repeated 9 times
kernel: sky2 eth1: rx length error: status 0x402300 length 64
kernel: sky2 eth1: rx length error: status 0x402500 length 64
*last message repeated 7 times
*last message repeated 6 times
kernel: sky2 eth1: rx length error: status 0x402300 length 64
kernel: sky2 eth1: rx length error: status 0x402500 length 64
(...)

Similar log from 2.6.22:
sky2 eth0: tx timeout
sky2 eth0: transmit ring 141 .. 119 report=141 done=141
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 48K
bonding: bond0: link status definitely down for interface eth0, disabling it
bonding: bond0: making interface eth1 the new active one.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x402300 length 64
sky2 eth0: rx error, status 0x8a2100 length 138
sky2 eth0: rx error, status 0x8a2100 length 138
sky2 eth0: rx error, status 0x9a2100 length 154
sky2 eth0: rx error, status 0xba2100 length 186
sky2 eth0: rx error, status 0x5e2100 length 94
sky2 eth0: rx error, status 0xba2100 length 186
sky2 eth0: rx error, status 0xea2100 length 234
sky2 eth0: rx error, status 0x8a2100 length 138
sky2 eth0: rx error, status 0x8a2100 length 138
sky2 eth0: rx error, status 0xea2100 length 234
sky2 eth0: rx error, status 0x8a2100 length 138
(...)

It seems that there is somethig wrong with the receiver hang workaround 
code. After such reset the card is not longer able to receive traffic. 
Maybe it is somehow related to vlans?

This problem exists in 2.6.21/2.6.22/2.6.24. I have not yet tested 
2.6.25/2.6.26, any chances it get fixed there?

Best regards,

 				Krzysztof Olędzki