Date: Wed, 16 Jun 2010 03:50:39 +0400 From: Artem Kim <artem_kim@inbox.ru> To: pyunyh@gmail.com Cc: freebsd-stable@freebsd.org, yongari@freebsd.org Subject: Re: Problems with bge (possibly related to r208993) Message-ID: <201006160350.39502.artem_kim@inbox.ru> In-Reply-To: <20100615232108.GM4257@michelle.cdnetworks.com> References: <201006131934.11389.artem_kim@inbox.ru> <201006160257.01213.artem_kim@inbox.ru> <20100615232108.GM4257@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 16 June 2010 03:21:09 Pyun YongHyeon wrote: > Hmm, why you need link0 flag? The link0 flag is used to force the > interface MASTER. Normally this configuration is automatically > done during auto-negotiation such that one is configured as MASTER > and the other is configured as SLAVE. If you manually configure > this setting you should be very careful not to use the same > configuration of MASTER/SLAVE of link partner. If you have to use > link0 option, the link partner should be configured to use SLAVE. > Normally you should always use auto-negotiation on 1000baseT unless > link partner is severely broken to support NWAY. > > It seems link partner does not agree on resolved speed/duplex > configuration of bge1. Check link partner's resolved link > configuration. > In any case, now I do not use the flag link0. Now the master/slave is assigned through auto-negotiation. link0 not been set before the problem occurred. I reset link0 flag on NAS2 when I got a problem the first time. Now x900 port1.0.12 and bge0 configured automatically. >bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active >awplus>show int port1.0.12 status >Port Name Status Vlan Duplex Speed Type >port1.0.12 connected 55 a-full a-1000 1000BASE-T
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006160350.39502.artem_kim>