Problem with igb(4) updated to version 2.0.7

Jack Vogel jfvogel at gmail.com
Fri Dec 3 17:49:50 UTC 2010


It has never been the case that 'down'ing an interface brings link down, not
on em
or igb. So this isn't problem with the release.

Jack


On Thu, Dec 2, 2010 at 11:40 PM, Eugene Grosbein <egrosbein at rdtc.ru> wrote:

> 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 at pci0:3:0:0:        class=0x020000 card=0xa03c8086 chip=0x10c98086
> rev=0x01 hdr=0x00
> >     class      = network
> >     subclass   = ethernet
> > igb1 at 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
>


More information about the freebsd-net mailing list