Hello, Marius. You wrote 11 января 2011 г., 22:36:44:
>> I've discussed this problem in local (Russian-speaking) FreeBSD >> community, and there are several people in DC 13 who HAVE these >> problems and found different solutions, but all non-technical ones: >> order gigabit connectivity, or pay for moving servers to other (old) >> DCs... > If the latter means that the servers are physically moved as opposed > to a new one being allocated this implies that re(4)/rgephy(4) isn't > the sole factor responsible for this problem. In any case it would be It is known, that DC 13 has new Juniper e3k switches, and older DCs have older Juniper equipment. > helpful to have the corresponding dmesg bits as the Linux counterpart > does some black magic for certain hardware versions when setting the > media manually but re(4) doesn't which might be relevant in this > scenario. Here it is from Rescue FreeBSD system: re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xe800-0xe8ff mem 0xfbeff000-0xfbefffff,0xf8ff0000-0xf8ffffff irq 16 at device 0.0 on pci6 re0: Using 1 MSI messages re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: <MII bus> on re0 rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 6c:62:6d:a7:bb:37 re0: [FILTER] And, please note very strange output from Linux's mii-tool and ethtool in previous my message to list: mismatch between "basic mode" and "link partner". -- // Black Lion AKA Lev Serebryakov <l...@serebryakov.spb.ru> _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
