From: Paul Larson <plars@linuxtestproject.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Brian Somers <brian.somers@sun.com>,
Michael.Waychison@sun.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: TG3 doesn't work in kernel 2.4.27 (David S. Miller)
Date: Fri, 03 Sep 2004 14:12:58 -0500 [thread overview]
Message-ID: <1094238777.9913.278.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <20040830161126.585a6b62.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
I tried this patch alone on top of 2.6.9-rc1 and tg3 is still broken for
me on JS20 blades. Was there another patch I should have applied in
conjunction with this?
Thanks,
Paul Larson
On Mon, 2004-08-30 at 18:11, David S. Miller wrote:
> Michael Chan at Broadcom spotted the bug.
>
> Things are totally broken if the switch/hub does not support
> autonegotiation. Checking for the MAC_STATUS_SIGNAL_DET bit
> in the tg3 polling timer fixes the problem.
>
> This is probably why it worked for you and doesn't with the
> IBM blades as blades are more likely to be connected to
> non-autoneg'ing devices.
>
> ===== drivers/net/tg3.c 1.199 vs edited =====
> --- 1.199/drivers/net/tg3.c 2004-08-18 19:52:35 -07:00
> +++ edited/drivers/net/tg3.c 2004-08-30 15:08:07 -07:00
> @@ -5602,7 +5602,8 @@
> need_setup = 1;
> }
> if (! netif_carrier_ok(tp->dev) &&
> - (mac_stat & MAC_STATUS_PCS_SYNCED)) {
> + (mac_stat & (MAC_STATUS_PCS_SYNCED |
> + MAC_STATUS_SIGNAL_DET))) {
> need_setup = 1;
> }
> if (need_setup) {
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-03 19:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040816110000.1120.31256.Mailman@lists.us.dell.com>
2004-08-16 11:51 ` Tetsuo Handa
2004-08-16 21:38 ` David S. Miller
2004-08-25 17:48 ` Mike Waychison
2004-08-25 19:08 ` David S. Miller
2004-08-25 20:04 ` Mike Waychison
2004-08-26 0:58 ` David S. Miller
2004-08-26 10:49 ` Brian Somers
2004-08-26 19:37 ` David S. Miller
2004-08-29 9:56 ` Pekka Pietikainen
2004-09-10 12:35 ` Brian Somers
2004-09-10 19:40 ` Roland Dreier
2004-09-10 20:53 ` David S. Miller
2004-09-10 21:05 ` Roland Dreier
2004-09-10 21:45 ` David S. Miller
2004-09-10 22:14 ` Brian Somers
2004-08-30 23:11 ` David S. Miller
2004-09-03 19:12 ` Paul Larson [this message]
2004-09-03 19:19 ` Mike Waychison
2004-09-03 20:18 ` Roland Dreier
2004-09-03 20:30 ` David S. Miller
2004-09-03 20:40 ` Roland Dreier
2004-09-03 23:24 ` Roland Dreier
2004-09-07 18:33 ` Jake Moilanen
2004-09-07 19:52 ` Roland Dreier
2004-09-08 12:34 ` Jake Moilanen
2004-09-08 13:07 ` Anton Blanchard
2004-09-13 22:48 ` David S. Miller
2004-09-14 22:20 ` Mike Waychison
2004-09-14 22:36 ` David S. Miller
2004-09-14 22:58 ` Jake Moilanen
2004-09-15 0:34 ` Roland Dreier
2004-09-08 13:55 ` Paul Larson
2004-09-10 16:00 ` Paul Larson
2004-09-03 20:08 ` David S. Miller
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=1094238777.9913.278.camel@plars.austin.ibm.com \
--to=plars@linuxtestproject.org \
--cc=Michael.Waychison@sun.com \
--cc=brian.somers@sun.com \
--cc=davem@davemloft.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
all inboxes | Powered by JetHome®