Date: Fri, 03 Dec 2010 13:40:23 +0600 From: Eugene Grosbein <egrosbein@rdtc.ru> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: Problem with igb(4) updated to version 2.0.7 Message-ID: <4CF89EE7.8020807@rdtc.ru> In-Reply-To: <4CF73A2C.7000802@rdtc.ru> References: <AANLkTimWVJhtu8LrZ_tn0Tdr-vs9PmPnW9SjebT7jnyM@mail.gmail.com> <AANLkTik%2B4Ag1HYXDWJvn2fTx6M%2Bpa9o29-A8j6qVRhZ_@mail.gmail.com> <AANLkTikwcRW%2BdqY=NTSbJsr3daEd-8usPo0Rw%2BhA_D-8@mail.gmail.com> <AANLkTin3%2BbCaXoPxTQsvzmqgtpA1zSY8f17Qh-nqymPw@mail.gmail.com> <201011270946271408828@yahoo.com.cn> <AANLkTikG8RJQw%2Bh1SHZPs1cHGrM%2B3LfniZrdLqVoPVtr@mail.gmail.com> <AANLkTi=YjG40%2BDj7471wyv3aeXGJgoL1GC33iNaypsrW@mail.gmail.com> <AANLkTi=LgejYxRXnxLtkvB-Qfp2u%2BtySdriWHfGWPQjL@mail.gmail.com> <20101128081617.GA90332@zibbi.meraka.csir.co.za> <AANLkTinF1fovumkeXxWgaKi_bNiUCnqgWAtdaCaXELzO@mail.gmail.com> <4CF73A2C.7000802@rdtc.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02.12.2010 12:18, Eugene Grosbein wrote: > Hi! > > I'm building new router using 8.2-PRERELEASE containing new igb(4) driver. > I use SuperMicro SuperServer 5016T-MTFB based on X8STi-F motherboard > with add-on Intel Gigabit ET Dual Port Server Adapter in PCIe slot. > > pciconf -lv shows: > > igb0@pci0:3:0:0: class=0x020000 card=0xa03c8086 chip=0x10c98086 rev=0x01 hdr=0x00 > class = network > subclass = ethernet > igb1@pci0:3:0:1: class=0x020000 card=0xa03c8086 chip=0x10c98086 rev=0x01 hdr=0x00 > class = network > subclass = ethernet > > I connect both ports to Cisco 7606 core router and they link > after "ifconfig ibg1 up" command. > > But "ifconfig igb1 down" does NOT bring link down: > - ifconfig igb still shows "status: active" (but not UP nor RUNNING); > - LEDs are on (both SuperServer's and Cisco's) > - Cisco also shows interfaces in "up" state. > > That's bad as I plan to use EtherChannel/lagg configuration > and need working up/down management. > This SuperServer box has two built-in em(4) ports that have not this problem. Really em(4) does have this probem too. How do I lock link down using em/igb NICs? Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CF89EE7.8020807>