Date: Tue, 29 Dec 2009 21:08:22 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: Alan Cox <alan@linux.intel.com>, linux-kernel@vger.kernel.org,
       Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [Regression, bisected] Receive failure in et131x.
Message-ID: <20091229210822.2a6a5f80@lxorguk.ukuu.org.uk>
In-Reply-To: <20091229180005.GA23030@emergent.ellipticsemi.com>
References: <20091229180005.GA23030@emergent.ellipticsemi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1221
Lines: 24

On Tue, 29 Dec 2009 13:00:05 -0500
Nick Bowler <nbowler@elliptictech.com> wrote:

> Continuing the theme from the last release cycle -- my PCI-express
> et131x card (which works in 2.6.32) fails in the latest Linus git.  The
> card works at first (DHCP and NFS mounts during bootup are OK) but
> quickly fails once any reasonable traffic is put through it.  Transmit
> seems to continue to work after a failure, but receive is mostly dead
> forever -- the occasional frame appears to make it through.  The kernel
> log contains many messages of the following form:
> 
> et131x 0000:02:00.0: NICRxPkts PSR Entry 1546 indicates length of 12920 and/or bad bi(614)
> et131x 0000:02:00.0: NICRxPkts PSR Entry 1547 indicates length of 27745 and/or bad bi(92)
> et131x 0000:02:00.0: NICRxPkts PSR Entry 1548 indicates length of 30064 and/or bad bi(116)

Thanks - I'll beat that one over the head Jan 2nd and get it back into
order. What setup are you using and at what speed ?

Alan
--
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/