netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr>
To: Rick Jones <rick.jones2@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
	Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [Bugme-new] [Bug 11752] New: Extremely low	netperf	UDP_RR	throughput for nvidia MCP65
Date: 11 Dec 2008 21:53:36 +0100	[thread overview]
Message-ID: <wpfxkuo2lr.fsf@heho.snv.jussieu.fr> (raw)
In-Reply-To: <48FCC2C1.5030108@hp.com>


Hello,

Rick Jones <rick.jones2@hp.com> writes:

> >>Clearly something is fubar with the rx side (well duh :).  The next
> >>set of stats I'd try to look at would be ethtool stats for the
> >>interface, eg ethtool -S eth0 and see if it shows someting more
> >>specific for the "RX-ERR" shown by netstat -I eth0.
> > OK, here it is (rx_errors_total: 10049, rx_crc_errors: 10049) :
> 
> Well, that seems to confirm that it is CRC errors.

[ .. stuff deleted .. ]

well, just a quick 'knock knock' in case any of you has something
new on this

I can live with 100Mbps, but would be glad to help further to
get it work at 1gbps (pavillon dv6700).
Looks like a silicon bug to me, but alas; please beep me if
I can test something.

Best regards, Arno

      parent reply	other threads:[~2008-12-11 22:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11752-10286@http.bugzilla.kernel.org/>
2008-10-16 20:49 ` [Bugme-new] [Bug 11752] New: Extremely low netperf UDP_RR throughput for nvidia MCP65 Andrew Morton
2008-10-16 21:07   ` Rick Jones
2008-10-17 14:28     ` Arno J. Klaassen
2008-10-17 20:49     ` Arno J. Klaassen
2008-10-17 21:05       ` Rick Jones
2008-10-18 11:36         ` Arno J. Klaassen
2008-10-20 17:41           ` Rick Jones
2008-10-31 13:07             ` Arno J. Klaassen
2008-12-11 20:53             ` Arno J. Klaassen [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=wpfxkuo2lr.fsf@heho.snv.jussieu.fr \
    --to=arno@heho.snv.jussieu.fr \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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).