From: Olaf Hering <olaf@aepfle.de>
To: Michael Chan <mchan@broadcom.com>
Cc: linuxppc-dev@ozlabs.org, Matt Carlson <mcarlson@broadcom.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: dead network on JS21 with tg3 driver after flowcontrol changes
Date: Fri, 16 May 2008 10:13:30 +0200 [thread overview]
Message-ID: <20080516081330.GA26530@aepfle.de> (raw)
In-Reply-To: <1210881078.22745.9.camel@dell>
On Thu, May 15, Michael Chan wrote:
> Matt, I think that's very likely the problem. If we are trying to
> establish link in parallel detect mode, the flow control settings may
> not match. If we do not enter the if statement to do nothing, we will
> keep autonegotiating forever and never establish link.
Yes, this patch fixes nfsroot for me. Thanks.
mii-tool is not shipped anymore, even in SLES10.
I assume that ethtool is the replacement?
Olaf
WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de>
To: Michael Chan <mchan@broadcom.com>
Cc: Matt Carlson <mcarlson@broadcom.com>,
linuxppc-dev@ozlabs.org, netdev <netdev@vger.kernel.org>
Subject: Re: dead network on JS21 with tg3 driver after flowcontrol changes
Date: Fri, 16 May 2008 10:13:30 +0200 [thread overview]
Message-ID: <20080516081330.GA26530@aepfle.de> (raw)
In-Reply-To: <1210881078.22745.9.camel@dell>
On Thu, May 15, Michael Chan wrote:
> Matt, I think that's very likely the problem. If we are trying to
> establish link in parallel detect mode, the flow control settings may
> not match. If we do not enter the if statement to do nothing, we will
> keep autonegotiating forever and never establish link.
Yes, this patch fixes nfsroot for me. Thanks.
mii-tool is not shipped anymore, even in SLES10.
I assume that ethtool is the replacement?
Olaf
next prev parent reply other threads:[~2008-05-16 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 12:13 dead network on JS21 with tg3 driver after flowcontrol changes Olaf Hering
2008-05-15 15:10 ` Michael Chan
2008-05-15 15:10 ` Michael Chan
2008-05-15 15:49 ` Olaf Hering
2008-05-15 17:37 ` Michael Chan
2008-05-15 17:37 ` Michael Chan
2008-05-15 17:15 ` Matt Carlson
2008-05-15 17:15 ` Matt Carlson
2008-05-15 19:51 ` Michael Chan
2008-05-15 19:51 ` Michael Chan
2008-05-16 8:13 ` Olaf Hering [this message]
2008-05-16 8:13 ` Olaf Hering
2008-05-16 15:09 ` Michael Chan
2008-05-16 15:09 ` Michael Chan
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=20080516081330.GA26530@aepfle.de \
--to=olaf@aepfle.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.