From: Gergely Madarasz <gorgo@broadband.hu>
To: Neil Horman <nhorman@redhat.com>
Cc: linux-net@vger.kernel.org, bridge@lists.osdl.org
Subject: [Bridge] Re: tg3 bridge problems
Date: Tue, 11 Jan 2005 10:16:42 +0100 [thread overview]
Message-ID: <20050111091642.GB10074@thunderchild.debian.net> (raw)
In-Reply-To: <41E2E90C.7010307@redhat.com>
On Mon, Jan 10, 2005 at 03:43:56PM -0500, Neil Horman wrote:
> Gergely Madarasz wrote:
> >On Mon, Jan 10, 2005 at 02:53:10PM -0500, Neil Horman wrote:
> >
> >>Gergely Madarasz wrote:
> >>
> >>>On Mon, Jan 10, 2005 at 02:41:34PM -0500, Neil Horman wrote:
> >>>>Gergely Madarasz wrote:
> >>>>
> >>>>I've got a tg3 card here. I'll try re-create it as soon as I have
> >>>>time.
> >>>
> >>>
> >>>Sounds great, but I expect it will not occur with a random tg3 card,
> >>>explained above...
> >>>
> >>
> >>Mmmmm....post your lspci -vvv entry for your broken tg3 card?
> >
> >
> >on the ibm x346:
> >
> >0000:05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
> >Gigabit Ethernet PCI Express (rev 01)
> > ...
> >
> >The other one looks the same, just bus 06 instead of 05 and different
> >Region 0 and Address lines.
> >
> >Same problem, other machine (ibm x326):
> >
> >0000:02:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704
> >Gigabit Ethernet (rev 03)
> > ...
> >
> >Greg
>
> Crud, you're right, I've got a completely different tg3 card. I'll
> still try to get a bridge set up to recreate, but it won't tell us much
> if the problem doesn't re-create. Can you put a printk in right before
> netif_receive_skb in tg3_rx to print out the source mac address of any
> received frames, we should be able to search for any MACs ==
> 01-80-C2-00-00-00, and determine for sure if the hardware is eating the
> frame, or something else is dropping it prematurely.
I went for an easier way (couldn't figure printing macs fast enough :),
I'm just printing out if there is a packet received in tg3_rx, and running
tethereal meanwhile. After checking the output for several minutes I'm
sure that every packet received by tg3_rx is accounted for in tethereal,
which means the incoming bpdu's are eaten by the hardware...
Greg
next prev parent reply other threads:[~2005-01-11 9:16 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 [this message]
2005-01-11 4:06 ` Paul Schulz
2005-01-11 8:52 ` Gergely Madarasz
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=20050111091642.GB10074@thunderchild.debian.net \
--to=gorgo@broadband.hu \
--cc=bridge@lists.osdl.org \
--cc=linux-net@vger.kernel.org \
--cc=nhorman@redhat.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.