broken re(4)

[Gerrit Kühn]

On Thu, 29 May 2008 23:03:01 +1000 "Dewayne Geraghty"
<dewayne.geraghty at heuristicsystems.com.au> wrote about RE: broken re(4):

DG> You might try, after rebooting, to physically unplug and replug your
DG> networking cables.

I already did try that one or twice, without any success.

DG> I have a few EN-15000 and SN-18000 motherboards attached to different
DG> types of switches. With the SN-18000 on FreeBSD 7.0R-p1 to make the
DG> vge NIC function even after rebooting I need to unplug the NIC's.
DG> Doesn't matter what switch, or even using a crossover cable, the card
DG> needs to reinitialise itself.  This may be similar the problem that
DG> you're experiencing.  And as Pyon YongHyeon mentions there is a lot of
DG> variety with rl and re cards, I also use re in my ITX motherboards,
DG> without experiencing your issues.

Sounds like I should play around with the cabeling some more. Thanks for
the hint.

DG> Also, after rebooting your machines try performing tcpdump -vv on the
DG> interface that isn't working while (ie before & after) you try the
DG> unplug/plug sequence.  (vge's since 6.1R experience a lot of incorrect
DG> checksums.)  I'm suggesting these steps as they might also assist
DG> others with clues to assist diagnoses with your re's)

I ran tcpdump on the dead interface and remember seeing at least broadcast
packages and such arriving from other machines. If I see an interface
in this state again I will do some more debugging. Maybe it just cannot
send packets, and is receiving just fine?


cu
  Gerrit