link negotiation issues on re(4)/rgephy with new switch

[Jeff Rizzo]

I bought a new (well, used) Netgear GS784T switch, and went to plug my
Xen DOM0 box into it, only to find out the ethernet interface (re(4))
wouldn't come up... it shows "no carrier" when I check ifconfig output.
I tried various things, rebooting, etc., but I couldn't get it to come
up. (the switch port and cable, of course, works fine on other
systems). Thinking there might be an issue with rgephy, I built a
kernel without (xen dom0 doesn't seem to support userconf, so I couldn't
just disable it), and tried that. It fails in very much the same way,
*except* that right after a reboot, it sort-of comes up:

re0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500

capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: bc:ae:c5:de:7f:d4
media: Ethernet autoselect
status: active
inet 10.187.0.31 netmask 0xffff0000 broadcast 10.187.255.255
inet6 fe80::beae:c5ff:fede:7fd4%re0 prefixlen 64 scopeid 0x1

...but it doesn't negotiate 1000baseT full-duplex, as I would expect
(and as it does with the old switch).

Does anyone have any further troubleshooting suggestions?

Thanks,
+j



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Darren Reed]

Post by Jeff Rizzo
...
...but it doesn't negotiate 1000baseT full-duplex, as I would expect
(and as it does with the old switch).

This suggests that the problem is not related to the driver.

Does a new cable help?

You've tried using different ports on the switch?

If you force the interface with "media 100BaseT", does it work?

Darren


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[je]

Post by Jeff Rizzo
I bought a new (well, used) Netgear GS784T switch, and went to plug my
Xen DOM0 box into it, only to find out the ethernet interface (re(4))
wouldn't come up... it shows "no carrier" when I check ifconfig output.
I tried various things, rebooting, etc., but I couldn't get it to come
up. (the switch port and cable, of course, works fine on other
systems). Thinking there might be an issue with rgephy, I built a
kernel without (xen dom0 doesn't seem to support userconf, so I couldn't
just disable it), and tried that. It fails in very much the same way,
re0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: bc:ae:c5:de:7f:d4
media: Ethernet autoselect
status: active
inet 10.187.0.31 netmask 0xffff0000 broadcast 10.187.255.255
inet6 fe80::beae:c5ff:fede:7fd4%re0 prefixlen 64 scopeid 0x1
...but it doesn't negotiate 1000baseT full-duplex, as I would expect
(and as it does with the old switch).
Does anyone have any further troubleshooting suggestions?
Thanks,
+j

The managed Netgear switches I've seen have several power-saving modes,
some related to autodetecting cable length. Perhaps they have been
enabled and are functioning improperly for you?

John

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Jeff Rizzo]

Post by je
The managed Netgear switches I've seen have several power-saving
modes, some related to autodetecting cable length. Perhaps they have
been enabled and are functioning improperly for you?

I suppose it's possible, but I don't see any related options on the
netgear management interface. And, of course, it works with all the
other cards I have.

+j


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de