public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Brian Lazara <blazara@nvidia.com>
Cc: linux-kernel@vger.kernel.org,
	Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Subject: [PATCH 2.6.7 and 2.4.27-pre6] new device support for forcedeth.c
Date: Sun, 27 Jun 2004 22:33:17 +0200	[thread overview]
Message-ID: <40DF2F0D.6030804@colorfullife.com> (raw)

Hi Brian,

could you check the full duplex handling? I'm testing my new nforce-250
Gb (epox 8KDA3J) with a normal 100 MBit autonegotiation link partner and
I'm getting bad performance (30 kB/sec) when sending. Half duplex works.
The nic reports late collisions:

nv_tx_done: looking at packet 233, Flags 0x28200.
	-> packet not yet completed
nv_tx_done: looking at packet 233, Flags 0x1a810.
	bits 16, 15, 13, 11, 4
	error, lastpacket, late collision, deferred, retryerror.
nv_tx_done: looking at packet 234, Flags 0x8000.
	-> successful
nv_tx_done: looking at packet 235, Flags 0x28200.
	-> not yet completed.

Autonegotiation seems to work correctly: np->linkspeed is set to 65636, 
np->duplex to 1.
lspci reports:

00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2)
        Subsystem: Unknown device 1695:100c
        Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11
        Memory at ec000000 (32-bit, non-prefetchable)
        I/O ports at b400 [size=8]
        Capabilities: [44] Power Management version 2
00: de 10 df 00 07 00 b0 00 a2 00 80 06 00 00 00 00
10: 00 00 00 ec 01 b4 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 95 16 0c 10
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 01 14

Could you give me a hint what's wrong? If you need further register 
values, just ask.

Thanks,
--
	Manfred

             reply	other threads:[~2004-06-27 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 20:33 Manfred Spraul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30  0:10 [PATCH 2.6.7 and 2.4.27-pre6] new device support for forcedeth.c Ayaz Abdulla
2004-06-28 15:38 Brian Lazara
2004-06-19  7:13 Brian Lazara
2004-06-19  8:42 ` Kalin KOZHUHAROV
2004-06-19 10:07 ` Christoph Hellwig

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=40DF2F0D.6030804@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=blazara@nvidia.com \
    --cc=c-d.hailfinger.kernel.2004@gmx.net \
    --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