search for: igb1

...ress: 00:30:48:ca:21:f6 Sep 17 11:25:39 romulus kernel: igb0: Bound queue 0 to cpu 0 Sep 17 11:25:39 romulus kernel: igb0: Bound queue 1 to cpu 1 Sep 17 11:25:39 romulus kernel: igb0: Bound queue 2 to cpu 2 Sep 17 11:25:39 romulus kernel: igb0: Bound queue 3 to cpu 3 Sep 17 11:25:39 romulus kernel: igb1: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x4020-0x403f mem 0xd8580000-0xd859ffff,0xd8560000-0xd857ffff,0xd8504000-0xd8507fff irq 70 at device 0.1 on pci8 Sep 17 11:25:39 romulus kernel: igb1: Using MSIX interrupts with 5 vectors Sep 17 11:25:39 romulus kernel: igb1: Ethern...

Ok, So this is really more of an observation than anything else.? I had a FreeBSD 10.1 server that was running great. Some SSL issue came up, or I upgrade Dovecot in ports - something occurred and the machine started rebooting randomly.? It would run for 2 weeks, then reboot.? It might run for 5 days and then reboot. So I started doing more FreeBSD upgrades, thinking it was a kernel issue. The

Two hosts, A and B. igb0 on A connects to e1000g1 on B. host A # dladm show-link LINK CLASS MTU STATE BRIDGE OVER igb0 phys 1500 unknown -- -- e1000g0 phys 1500 up -- -- e1000g1 phys 1500 up -- -- igb1 phys 1500 up -- -- e1000g1vnic1 vnic 1500 up -- e1000g1 e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 278 inet 10.0.1.132 netmask ffffff00 broadcast 10.0.1.255 ether 0:23:8b:64:da:13 e1000g1vnic1:...

...AST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:25:90:34:c1:12 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:25:90:34:c1:13 inet 172.16.1.6 netmask 0xfffff000 broadcast 172.16.15.255 inet6 fe80::225:90ff:fe34:c113%igb1 pre...