[Bug 240818] igb(4) vlanhwfilter feature generate link UP/DOWN for each new vlan created
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Nov 6 22:51:17 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240818
mike at sentex.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike at sentex.net
--- Comment #25 from mike at sentex.net ---
I have confirmed this behaviour on RELENG_12 (r367411)
e.g
ifconfig vlan6 create 10.6.6.6/28 vlandev igb1 vlan 6
ifconfig vlan7 create 10.7.7.7/28 vlandev igb1 vlan 7
# dmesg | tail -19
vlan5: promiscuous mode enabled
igb1: promiscuous mode disabled
vlan5: promiscuous mode disabled
igb1: promiscuous mode enabled
igb1: promiscuous mode disabled
igb1: link state changed to DOWN
vlan5: link state changed to DOWN
vlan6: link state changed to DOWN
igb1: link state changed to UP
vlan5: link state changed to UP
vlan6: link state changed to UP
igb1: link state changed to DOWN
vlan5: link state changed to DOWN
vlan6: link state changed to DOWN
vlan7: link state changed to DOWN
igb1: link state changed to UP
vlan5: link state changed to UP
vlan6: link state changed to UP
vlan7: link state changed to UP
ie. with each vlan created, igb1 and all the VLANS transition with a full
carrier down/up (confirmed from the switch they are connected to)
Confirmed on 3 different boards
Supermicro X11SSH-F
igb1 at pci0:3:0:0: class=0x020000 card=0x153315d9 chip=0x15338086 rev=0x03
hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0xdf200000, size 524288, enabled
bar [18] = type I/O Port, range 32, base 0xd000, size 32, enabled
bar [1c] = type Memory, range 32, base 0xdf280000, size 16384, enabled
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message, 64 bit, vector masks
cap 11[70] = MSI-X supports 5 messages, enabled
Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR NS
max read 512
link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1)
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0003[140] = Serial 1 ac1f6bffff77ce57
ecap 0017[1a0] = TPH Requester 1
ASRockRack X470D4U
# pciconf -lcvb igb1
igb1 at pci0:36:0:0: class=0x020000 card=0x15331849 chip=0x15338086 rev=0x03
hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0xf7300000, size 524288, enabled
bar [18] = type I/O Port, range 32, base 0xd000, size 32, enabled
bar [1c] = type Memory, range 32, base 0xf7380000, size 16384, enabled
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message, 64 bit, vector masks
cap 11[70] = MSI-X supports 5 messages, enabled
Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR RO NS
max read 512
link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1)
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0003[140] = Serial 1 7085c2fffffde3e8
ecap 0017[1a0] = TPH Requester 1
Supermicro SYS-5019C-M
# pciconf -lvcb igb1
igb1 at pci0:4:0:0: class=0x020000 card=0x153315d9 chip=0x15338086 rev=0x03
hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0x93200000, size 524288, enabled
bar [18] = type I/O Port, range 32, base 0x4000, size 32, enabled
bar [1c] = type Memory, range 32, base 0x93280000, size 16384, enabled
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message, 64 bit, vector masks
cap 11[70] = MSI-X supports 5 messages, enabled
Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR RO NS
max read 512
link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1)
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0003[140] = Serial 1 3cecefffff6d99ab
ecap 0017[1a0] = TPH Requester 1
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-net
mailing list