Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755301AbZITSFd (ORCPT ); Sun, 20 Sep 2009 14:05:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754682AbZITSFb (ORCPT ); Sun, 20 Sep 2009 14:05:31 -0400 Received: from mail.vyatta.com ([76.74.103.46]:33608 "EHLO mail.vyatta.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754069AbZITSFa (ORCPT ); Sun, 20 Sep 2009 14:05:30 -0400 Date: Sun, 20 Sep 2009 11:05:27 -0700 From: Stephen Hemminger To: Andrew Morton Cc: Grozdan , linux-kernel@vger.kernel.org, Stephen Hemminger , netdev@vger.kernel.org Subject: Re: sky2 rx length errors Message-ID: <20090920110527.39fd7af5@s6510> In-Reply-To: <20090919233536.f5fb700c.akpm@linux-foundation.org> References: <20090919233536.f5fb700c.akpm@linux-foundation.org> Organization: Vyatta X-Mailer: Claws Mail 3.6.1 (GTK+ 2.16.1; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2555 Lines: 54 On Sat, 19 Sep 2009 23:35:36 -0700 Andrew Morton wrote: > (added cc's from the MAINTAINERS file) > > On Fri, 18 Sep 2009 15:41:45 +0200 Grozdan wrote: > > > Hi, > > > > I have a Marvell onboard NIC (88E8053) and I've been noticing for a > > while now a bit weird behavior with the sky2 driver. This mostly > > occurs with newer kernels (2.6.30, 2.6.31) and my older distro kernel > > (2.6.27.21) does not seem to have the same problem. Basically, the > > sky2 driver will randomly and unpredictably spew rx length error > > messages and reboot itself. I also noticed in dmesg that this mostly > > occurs after "martian destination" messages. After this message, sky2 > > starts spewing messages as shown below and then reboots itself. It is > > not really a big problem for me, but since I'm virtually always logged > > in in IRC, the client always loses connection, waits for a few minutes > > to get a response from the server and then relogs me again. I do not > > think it's a HW problem as the Marvell NIC otherwise works perfectly > > and I've checked my cable modem too which operates without a problem. > > Any ideas? > > > > PS: please cc me as I'm not subscribed to the mailing list > > > > sky2 driver version 1.23 > > sky2 0000:05:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 > > sky2 0000:05:00.0: setting latency timer to 64 > > sky2 0000:05:00.0: PCI: Disallowing DAC for device > > sky2 0000:05:00.0: Yukon-2 EC chip revision 2 > > sky2 0000:05:00.0: irq 53 for MSI/MSI-X > > sky2 0000:05:00.0: No interrupt generated using MSI, switching to INTx mode. > > sky2 eth0: addr 00:11:d8:a1:5b:0e > > sky2 eth0: enabling interface > > sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx > > ..... > > ..... > > martian destination 0.0.0.0 from 172.23.204.1, dev eth0 > > sky2 eth0: rx length error: status 0x4420100 length 598 > > sky2 eth0: rx length error: status 0x5ea0100 length 598 This error status occurs if the length reported by the PHY does not match the len reported by the DMA engine. The error status is: 0x4420100 = length 1090 + broadcast packet... No idea what is on your network, but perhaps there is some MTU confusion? Since martian destination seems related, knowing more about that packet might help. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/