From: Gergely Madarasz <gorgo@broadband.hu>
To: Paul Schulz <pschulz@foursticks.com>
Cc: linux-net@vger.kernel.org, Neil Horman <nhorman@redhat.com>,
bridge@lists.osdl.org
Subject: Re: [Bridge] Re: tg3 bridge problems
Date: Tue, 11 Jan 2005 09:52:16 +0100 [thread overview]
Message-ID: <20050111085216.GA10074@thunderchild.debian.net> (raw)
In-Reply-To: <1105416406.4923.8.camel@localhost.localdomain>
On Tue, Jan 11, 2005 at 02:36:46PM +1030, Paul Schulz wrote:
> Greetings,
>
> This may be the problem that I have seen (and reported) previously...
> http://oss.sgi.com/projects/netdev/archive/2004-02/msg00442.html
>
> One suggestion.. do a packet dump on an outgoing bridge port, and a
> dump from a transmitting machine connected to the bridge. Compare the
> MD5 checksums.
Thanks for the idea, but it doesn't seem to help. I've modified the patch
to apply to my chipset revision (and added a debugging printk to make sure
I've hit the right chipset :)), but nothing really changed. I didn't
expect it to either, because this is not a transmit problem, but a
promiscuous receive problem of the driver/card.
Greg
next prev parent reply other threads:[~2005-01-11 8:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 14:06 [Bridge] tg3 bridge problems Gergely Madarasz
2005-01-10 15:05 ` [Bridge] " Neil Horman
2005-01-10 15:45 ` Gergely Madarasz
2005-01-10 16:04 ` Neil Horman
2005-01-10 16:18 ` Gergely Madarasz
2005-01-10 17:40 ` Neil Horman
2005-01-10 19:11 ` Gergely Madarasz
2005-01-10 19:41 ` Neil Horman
2005-01-10 19:49 ` Gergely Madarasz
2005-01-10 19:53 ` Neil Horman
2005-01-10 20:09 ` Gergely Madarasz
2005-01-10 20:43 ` Neil Horman
2005-01-11 9:16 ` Gergely Madarasz
2005-01-11 4:06 ` Paul Schulz
2005-01-11 8:52 ` Gergely Madarasz [this message]
2005-01-11 12:36 ` Neil Horman
2005-01-11 12:58 ` Gergely Madarasz
2005-01-11 13:12 ` Neil Horman
2005-01-11 14:07 ` Gergely Madarasz
2005-01-11 20:19 ` dave
2005-01-12 9:21 ` Gergely Madarasz
2005-01-10 19:34 ` Stephen Hemminger
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=20050111085216.GA10074@thunderchild.debian.net \
--to=gorgo@broadband.hu \
--cc=bridge@lists.osdl.org \
--cc=linux-net@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=pschulz@foursticks.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 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.