netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Yan Seiner" <yan@seiner.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: mcp55 forcedeth woes
Date: Mon, 13 Apr 2009 16:45:48 -0700	[thread overview]
Message-ID: <20090413164548.f241ec1e.akpm@linux-foundation.org> (raw)
In-Reply-To: <e3e0f4f0ca9fdce35c24b30559d10f31.squirrel@www.datavault.us>

(suitable cc's added)

On Mon, 13 Apr 2009 15:13:05 -0700 (PDT)
"Yan Seiner" <yan@seiner.com> wrote:

> I have a few Asus M2N-SLI deluxe mobos.  These mobos have the MCP55
> chipset and two 1gb ethernet ports.  Occasionally, and for no reason that
> I can figure out, these ports will die.  There are various ways to try and
> fix these; they seem to be about 50% effective, and approach something
> akin to voodoo.
> 
> Based on this discussion here:
> 
> http://patchwork.kernel.org/patch/16212/
> 
> I've gotten the ability to turn the ports on and off somewhat.
> 
> For port 0,
> 
> ethtool -s eth0 autoneg off speed 10 duplex full
> 
> turns on the link, and gets me half-duplex, 10mb/sec. Not much, granted.
> 
> ethtool -s eth0 autoneg off speed 100 duplex full
> 
> causes the link to go up and down on about a 2 second cycle.
> 
> ethtool -s eth0 autoneg on
> 
> causes the link to drop.
> 
> For port 1, the behavior is similar, except that I can get a stable 100
> mbit connection.
> 
> So the problem is in the autoneg code. It's a driver issue as this is
> reported widely to work under windows of various flavors.
> 
> I'm running 2.6.29.1; I'm ok with patching and building kernels, but I'm
> not a kernel hacker.
> 
> What, if anything, can I provide and do to fix this?
> 


       reply	other threads:[~2009-04-13 23:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e3e0f4f0ca9fdce35c24b30559d10f31.squirrel@www.datavault.us>
2009-04-13 23:45 ` Andrew Morton [this message]
2009-04-15 13:54   ` mcp55 forcedeth woes Yan Seiner
     [not found] ` <200904132100.58056.gene.heskett@verizon.net>
     [not found]   ` <49E3EF9F.6090600@seiner.com>
     [not found]     ` <200904132224.13716.gene.heskett@verizon.net>
2009-04-14 14:35       ` Yan Seiner
2009-04-14 16:34         ` John Stoffel
2009-04-14 16:47           ` Yan Seiner
2009-04-14 18:27           ` Gene Heskett

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=20090413164548.f241ec1e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aabdulla@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yan@seiner.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).