Re: sky2 rx error (was: Re: sky2 freezes the system)
On Tue, Jan 31, 2006 at 01:45:18PM -0800, Stephen Hemminger wrote: The driver doesn't handle overlength packets properly. Someone maybe sending you jumbo frames or some other crap. The vendor driver doesn't handle over size frames either; it just resets itself every 5 seconds so you don't notice. Indeed, I just set the MTU to 4000 on the interface with problems and the hangs went away (it's connected to a switch monitor port so doesn't really matter what the MTU is, if it's oversized I definately want to see what it was :-) ). - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sky2 rx error (was: Re: sky2 freezes the system)
On Tue, Jan 24, 2006 at 06:36:29PM +0200, Pekka Pietikainen wrote: On Mon, Jan 23, 2006 at 08:03:15PM +0200, Pekka Pietikainen wrote: The box is a Nexcom NSA 1086 with 4x skge ports and 4x sky2. acpi=off made the driver work apparently, haven't used it with much load yet, though. Ran the box for a while with some load (the sky2 ports on the box are only used for sniffing, really, so no outbound traffic), and after a while the box stopped receiving traffic on one of the interfaces (the one with the most traffic). Tried rmmod/modprobe sky2, that didn't help as well as disabling rx checksums with ethtool. Still happens with 2.6.16-rc1-git4 + sky2-0.15. I did get sky2 eth3: rx error, status 0x7ffc2001 length 72 sky2 eth3: rx error, status 0x7ffc2001 length 72 sky2 eth3: rx error, status 0x7ffc2001 length 112 sky2 eth3: rx error, status 0x7ffc2001 length 108 sky2 eth3: rx error, status 0x7ffc2001 length 104 sky2 eth3: rx error, status 0x7ffc2001 length 80 sky2 eth3: rx error, status 0x7ffc2001 length 108 sky2 eth3: rx error, status 0x7ffc2001 length 112 sky2 eth3: rx error, status 0x7ffc2001 length 104 shortly after booting, then the box (NSA 1086) ran ok for quite some time, several hours. Then it just stopped accepting packets on one of the sky2 interfaces (others continued running). rmmod/modprobe fixed it now. Nothing in the logs, unfortunately. Ethtool showed link was still up... - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sky2 rx error (was: Re: sky2 freezes the system)
On Tue, 31 Jan 2006 22:41:51 +0200 Pekka Pietikainen [EMAIL PROTECTED] wrote: On Tue, Jan 24, 2006 at 06:36:29PM +0200, Pekka Pietikainen wrote: On Mon, Jan 23, 2006 at 08:03:15PM +0200, Pekka Pietikainen wrote: The box is a Nexcom NSA 1086 with 4x skge ports and 4x sky2. acpi=off made the driver work apparently, haven't used it with much load yet, though. Ran the box for a while with some load (the sky2 ports on the box are only used for sniffing, really, so no outbound traffic), and after a while the box stopped receiving traffic on one of the interfaces (the one with the most traffic). Tried rmmod/modprobe sky2, that didn't help as well as disabling rx checksums with ethtool. Still happens with 2.6.16-rc1-git4 + sky2-0.15. I did get sky2 eth3: rx error, status 0x7ffc2001 length 72 sky2 eth3: rx error, status 0x7ffc2001 length 72 sky2 eth3: rx error, status 0x7ffc2001 length 112 sky2 eth3: rx error, status 0x7ffc2001 length 108 sky2 eth3: rx error, status 0x7ffc2001 length 104 sky2 eth3: rx error, status 0x7ffc2001 length 80 sky2 eth3: rx error, status 0x7ffc2001 length 108 sky2 eth3: rx error, status 0x7ffc2001 length 112 sky2 eth3: rx error, status 0x7ffc2001 length 104 shortly after booting, then the box (NSA 1086) ran ok for quite some time, several hours. Then it just stopped accepting packets on one of the sky2 interfaces (others continued running). rmmod/modprobe fixed it now. Nothing in the logs, unfortunately. Ethtool showed link was still up... The driver doesn't handle overlength packets properly. Someone maybe sending you jumbo frames or some other crap. The vendor driver doesn't handle over size frames either; it just resets itself every 5 seconds so you don't notice. -- Stephen Hemminger [EMAIL PROTECTED] OSDL http://developer.osdl.org/~shemminger - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
sky2 rx error (was: Re: sky2 freezes the system)
On Mon, Jan 23, 2006 at 08:03:15PM +0200, Pekka Pietikainen wrote: The box is a Nexcom NSA 1086 with 4x skge ports and 4x sky2. acpi=off made the driver work apparently, haven't used it with much load yet, though. Ran the box for a while with some load (the sky2 ports on the box are only used for sniffing, really, so no outbound traffic), and after a while the box stopped receiving traffic on one of the interfaces (the one with the most traffic). Tried rmmod/modprobe sky2, that didn't help as well as disabling rx checksums with ethtool. Jan 24 11:06:45 localhost kernel: sky2 eth4: enabling interface Jan 24 11:06:46 localhost kernel: sky2 eth3: Link is up at 100 Mbps, full duplex, flow control none Jan 24 11:06:46 localhost kernel: sky2 eth4: Link is up at 100 Mbps, full duplex, flow control none Jan 24 11:06:48 localhost kernel: sky2 eth1: enabling interface Jan 24 11:06:48 localhost kernel: sky2 eth2: enabling interface Jan 24 11:41:30 localhost kernel: sky2 eth3: rx error, status 0x7ffc2001 length 1112 Jan 24 12:05:10 localhost kernel: sky2 eth3: disabling interface Jan 24 12:05:12 localhost kernel: sky2 eth3: enabling interface Jan 24 12:05:12 localhost kernel: sky2 unknown status opcode 0xe3 Jan 24 12:05:12 localhost kernel: sky2 eth3: rx error, status 0x9f6c1703 length 58049 Jan 24 12:05:14 localhost kernel: sky2 eth3: Link is up at 100 Mbps, full duplex, flow control none - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
