mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@draconx.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: [Regression, bisected] Transmit failure in et131x.
Date: Sun, 11 Oct 2009 23:00:23 +0000 (UTC)	[thread overview]
Message-ID: <loom.20091012T004346-812@post.gmane.org> (raw)
In-Reply-To: <20091009112016.4fb07eb7@lxorguk.ukuu.org.uk>

Alan Cox <alan <at> lxorguk.ukuu.org.uk> writes:
> Please test the following if you would.
> 
> If it doesn't work see if you can tell from the other end and tcpdump
> if the receiver or sender side dies, and let me know if you are using
> 10, 100 or Gbit and if you have the mtu set over 1500.

Thanks a lot for your help.  Alas, this does not resolve the issue.
Using tcpdump indicates that receive continues to work while transmit
fails.

I was using gigabit, but the problem persists when I run at 100mbit.
The MTU setting remains at the default 1500 bytes.

In case it's useful, here's the lspci -nv output for my card:

02:00.0 0200: 11c1:ed00 (rev 02)
        Subsystem: 11c1:ed00
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fd400000 (64-bit, non-prefetchable) [size=2M]
        Expansion ROM at fd7e0000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Express Endpoint, MSI 00
        Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Count=1/1
Enable-
        Capabilities: [100] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq+ ACSVoil-
                UEMsk:  DLP+ SDES- TLP+ FCP+ CmpltTO+ CmpltAbrt+ UnxCmplt+ RxOF+
MalfTLP+ ECRC+ UnsupReq+ ACSVoil-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
MalfTLP+ ECRC- UnsupReq- ACSVoil-
                CESta:  RxErr- BadTLP- BadDLLP+ Rollover- Timeout+ NonFatalErr-
                CESta:  RxErr+ BadTLP+ BadDLLP+ Rollover+ Timeout+ NonFatalErr-
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [130] Virtual Channel <?>
        Capabilities: [14c] Device Serial Number d9-29-03-fe-ff-3b-13-02
        Kernel driver in use: et131x
        Kernel modules: et131x



  reply	other threads:[~2009-10-11 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 14:08 Nick Bowler
2009-10-08 21:32 ` Alan Cox
2009-10-09 10:20 ` Alan Cox
2009-10-11 23:00   ` Nick Bowler [this message]
2009-10-12 10:36     ` Alan Cox
2009-10-12 14:19       ` 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=loom.20091012T004346-812@post.gmane.org \
    --to=nbowler@draconx.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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®