netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Craig Small <csmall@enc.com.au>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
	netdev@vger.kernel.org
Subject: Re: r8169 won't transmit with 3.12
Date: Wed, 22 Jan 2014 15:00:52 +1100	[thread overview]
Message-ID: <20140122040052.GA2310@enc.com.au> (raw)
In-Reply-To: <20140121233630.GA3214@electric-eye.fr.zoreil.com>

If it helps, I know the tx_dropped is happening on line 5837 of r8169.c

			rtl8169_unmap_tx_skb(&tp->pci_dev->dev, tx_skb,
					     tp->TxDescArray + entry);
			if (skb) {
				tp->dev->stats.tx_dropped++;
				dev_kfree_skb(skb);
				tx_skb->skb = NULL;
			}


On Wed, Jan 22, 2014 at 12:36:30AM +0100, Francois Romieu wrote:
> Craig Small <csmall@enc.com.au> :
> [...]
> > It's a new setup so it might of never worked. It's not likely to be a
> > hardware problem as its three different devices.
> 
> You may check that the onboard nic device does not even work when the
> extra PCI-e card aren't plugged.
> 
> > I've sent what I think you might need for starters, but if there
> > is extra stuff you'd like to see, let me know.
> 
> A complete dmesg including the XID lines that the r8169 driver prints
> would be welcome.
> 
> > The problem shows up the same, the TX dropped counter increments.
> > I'm not sure why 42 packets made it out (or even if they really did)
> > Receive works fine, I can even start up wireshark and see packets
> > pass by.
> > 
> > eth0      Link encap:Ethernet  HWaddr 00:e0:4c:80:66:57  
> >           inet addr:192.168.1.222  Bcast:192.168.1.255  Mask:255.255.255.0
> >           inet6 addr: fe80::2e0:4cff:fe80:6657/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:8252 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:42 errors:0 dropped:8029 overruns:0 carrier:0
> 
> There are very few places where the r8169 driver modifies tx_dropped.
> 
> Please increase the driver verbosity with the 'msglvl' option of ethtool.
> 
> [...]
> > ethtool -S shows a similar story, not sure if the rx_missed counter
> > is another problem:
> 
> It seems safe to ignore as long as it does not change after startup.
> 
> -- 
> Ueimor

-- 
Craig Small (@smallsees)   http://enc.com.au/       csmall at : enc.com.au
Debian GNU/Linux           http://www.debian.org/   csmall at : debian.org
GPG fingerprint:        5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

      parent reply	other threads:[~2014-01-22  4:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21  0:06 r8169 won't transmit with 3.12 Craig Small
2014-01-21 23:36 ` Francois Romieu
2014-01-22  0:41   ` Craig Small
2014-01-22 23:31     ` Francois Romieu
2014-01-23  7:57       ` Craig Small
2014-01-24  0:25         ` Francois Romieu
2014-01-25  0:59           ` Craig Small
2014-01-22  4:00   ` Craig Small [this message]

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=20140122040052.GA2310@enc.com.au \
    --to=csmall@enc.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).