public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Rune Jensen <anders@gnulinux.dk>
To: linux-kernel@vger.kernel.org
Subject: Forcedeth: Nvidia NIC goes up and down
Date: Mon, 02 Jul 2007 21:08:44 +0200	[thread overview]
Message-ID: <1183403324.11262.8.camel@localhost> (raw)

Hi

I recently invested in a asus m2n-mx. The motherboard features a nvidia
1gbit NIC (lspci says 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet
(rev a2)). I have it connected to my 1gbit switch together with another
machine. The problem is that very frequently (sometimes several times
each minute), the NIC goes down for a few seconds and then goes up
again. In the dmesg log I can see:

Jul  2 21:01:26 [kernel] eth0: link down.
Jul  2 21:01:28 [kernel] eth0: link up.
Jul  2 21:01:57 [kernel] eth0: link down.
Jul  2 21:01:59 [kernel] eth0: link up.
Jul  2 21:02:34 [kernel] eth0: link down.
Jul  2 21:02:36 [kernel] eth0: link up.
Jul  2 21:03:15 [kernel] eth0: link down.
Jul  2 21:03:18 [kernel] eth0: link up.

I've tried changing the cable and changing the port in the switch
without luck.

Sadly the motherboard only has 2 pci slots, which is already taken, so
adding another NIC is not an option. The wireless interface is working
perfectly fine on the machine so the problem seems related to the NIC.

I've tried fiddling with ethtool but I can't seem to make the NIC run at
100mbit. If I disable autoneg nothing seems to be working. Output from
ethtool:

Settings for eth0:
	Supported ports: [ MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised auto-negotiation: Yes
	Speed: 1000Mb/s
	Duplex: Full
	Port: MII
	PHYAD: 1
	Transceiver: external
	Auto-negotiation: on
	Supports Wake-on: g
	Wake-on: d
	Link detected: yes

Any idea how what I can do to debug this issue further?

Please cc me as I'm not subscribed. Thanks in advance

--
Anders Rune Jensen


             reply	other threads:[~2007-07-02 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 19:08 Anders Rune Jensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-22 20:43 Forcedeth: Nvidia NIC goes up and down jos.huisken
2007-08-24  1:40 ` Anders Rune Jensen

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=1183403324.11262.8.camel@localhost \
    --to=anders@gnulinux.dk \
    --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