mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.
Date: Tue, 29 Dec 2009 21:08:22 +0000	[thread overview]
Message-ID: <20091229210822.2a6a5f80@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20091229180005.GA23030@emergent.ellipticsemi.com>

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

  reply	other threads:[~2009-12-29 21:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 18:00 Nick Bowler
2009-12-29 21:08 ` Alan Cox [this message]
2009-12-30 14:59   ` Nick Bowler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091229210822.2a6a5f80@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=alan@linux.intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@elliptictech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®