[Bug 221146] [LAGG] Problem with second laggport

2017-11-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #19 from Sean Bruno  ---
I'm having a heck of a time reproducing this bug, as it seems like a race in
the attach startup.

If you are seeing this problem on Current or Stable/11, I've attached an
attempt to fix this, please report back if it helps or does nothing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-11-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #18 from Sean Bruno  ---
Created attachment 187912
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187912&action=edit
Move hardware notification of driver readiness to end of attach. Stable/11.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-11-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #17 from Sean Bruno  ---
Created attachment 187911
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187911&action=edit
Move hardware notification of driver readiness to end of attach.  Current.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Jeff Pieper  changed:

   What|Removed |Added

 CC||jeffrey.e.pie...@intel.com

--- Comment #16 from Jeff Pieper  ---
We are unable to reproduce this over 10 reboots:

FreeBSD u1015 11.1-STABLE FreeBSD 11.1-STABLE #0 d89b4f5935a(stable/11): Sat
Nov  4 04:15:08 UTC 2017

[root@u1015 ~]# sysctl dev.ix|grep Version
dev.ix.1.%desc: Intel(R) PRO/10GbE PCI-Express Network Driver, Version -
3.2.12-k
dev.ix.0.%desc: Intel(R) PRO/10GbE PCI-Express Network Driver, Version -
3.2.12-k

Relevant rc.conf entries:

ifconfig_ix0="up"
ifconfig_ix1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport ix0 laggport ix1 190.2.10.15 netmask
255.255.0.0"

[root@u1015 ~]# ifconfig - lagg0
lagg0: flags=8843 metric 0 mtu 1500
   
options=e407bb
ether 90:e2:ba:d5:bf:40
inet 190.2.10.15 netmask 0x broadcast 190.2.255.255
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg
laggproto lacp lagghash l2,l3,l4
lagg options:
flags=11
flowid_shift: 16
lagg statistics:
active ports: 2
flapping: 0
lag id: [(8000,90-E2-BA-D5-BF-40,00D2,,),
 (,00-04-96-9B-9B-35,03E9,,)]
laggport: ix0 flags=1c
state=3d
[(8000,90-E2-BA-D5-BF-40,00D2,8000,0003),
 (,00-04-96-9B-9B-35,03E9,,03E9)]
laggport: ix1 flags=1c
state=3d
[(8000,90-E2-BA-D5-BF-40,00D2,8000,0004),
 (,00-04-96-9B-9B-35,03E9,,03EA)]
[root@u1015 ~]# ifconfig -v ix1
ix1: flags=8843 metric 0 mtu 1500
   
options=e407bb
ether 90:e2:ba:d5:bf:40
hwaddr 90:e2:ba:d5:bf:41
nd6 options=29
media: Ethernet autoselect (10Gbase-LR )
status: active
plugged: SFP/SFP+/SFP28 10G Base-LR (LC)
vendor: Intel Corp PN: FTLX1471D3BCV-I3 SN: ATS0LVZ DATE: 2015-07-06
module temperature: 42.12 C Voltage: 3.30 Volts
RX: 0.43 mW (-3.64 dBm) TX: 0.76 mW (-1.17 dBm)

SFF8472 DUMP (0xA0 0..127 range):
03 04 07 20 00 00 02 00 00 00 00 06 67 02 0A 64
00 00 00 00 49 6E 74 65 6C 20 43 6F 72 70 20 20
20 20 20 20 00 00 1B 21 46 54 4C 58 31 34 37 31
44 33 42 43 56 2D 49 33 41 20 20 20 05 1E 00 83
00 3A 00 00 41 54 53 30 4C 56 5A 20 20 20 20 20
20 20 20 20 31 35 30 37 30 36 20 20 68 FA 02 45
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[root@u1015 ~]# ifconfig -v ix0
ix0: flags=8843 metric 0 mtu 1500
   
options=e407bb
ether 90:e2:ba:d5:bf:40
hwaddr 90:e2:ba:d5:bf:40
nd6 options=29
media: Ethernet autoselect (10Gbase-LR )
status: active
plugged: SFP/SFP+/SFP28 10G Base-LR (LC)
vendor: Intel Corp PN: FTLX1471D3BCV-I3 SN: AU20U3K DATE: 2015-07-15
module temperature: 41.68 C Voltage: 3.30 Volts
RX: 0.34 mW (-4.64 dBm) TX: 0.72 mW (-1.37 dBm)

SFF8472 DUMP (0xA0 0..127 range):
03 04 07 20 00 00 02 00 00 00 00 06 67 02 0A 64
00 00 00 00 49 6E 74 65 6C 20 43 6F 72 70 20 20
20 20 20 20 00 00 1B 21 46 54 4C 58 31 34 37 31
44 33 42 43 56 2D 49 33 41 20 20 20 05 1E 00 83
00 3A 00 00 41 55 32 30 55 33 4B 20 20 20 20 20
20 20 20 20 31 35 30 37 31 35 20 20 68 FA 02 FC
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Can you give us the ifconfig -v output for each ix interface?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #15 from Kevin Bowling  ---
Our cxgbe issue was not related and has been fixed by the vendor.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #14 from Cassiano Peixoto  ---
(In reply to Sean Bruno from comment #13)
Dear Sean,

I've just opened a PR 221317 regarding ixgbe driver update and netmap issue.

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Sean Bruno  changed:

   What|Removed |Added

 Status|Open|In Progress
 CC||sbr...@freebsd.org

--- Comment #13 from Sean Bruno  ---
(In reply to Cassiano Peixoto from comment #8)
For NetMap, yes.  That would be a different issue.  Which driver?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Matt Joras  changed:

   What|Removed |Added

 CC||mjo...@freebsd.org

--- Comment #12 from Matt Joras  ---
Does this only happen with LACP or does it happen with any lagg type (e.g.
failover)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #11 from Konrad  ---
Yes, its reproducible. I change lagg configuration in rc.conf and reboot
machine.

if lagg0 will start with "ix1 flags=0" ix1 will have always "no carrier" even
if I remove from laggport. Manually removed ix1 and netif restart does no fix
the problem (ix1 still has "no carrier"), only reboot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #10 from Andrey V. Elsukov  ---
(In reply to Konrad from comment #9)
> I set LAGG on igb0 and igb1 and seems to be ok:
> but when ix's ports are configured as lagg1, all laggports work properly.
> When I  switch ix's ports as lagg0 and first in cloned_interfaces the
> problem appears:

Is it reproducible? Are you doing this in runtime manually without reboot?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #9 from Konrad  ---
I set LAGG on igb0 and igb1 and seems to be ok:

lagg0: flags=8843 metric 0 mtu 1500
   
options=6403bb
ether 00:1e:67:27:1d:5e
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: igb0 flags=1c
laggport: igb1 flags=1c
lagg1: flags=8843 metric 0 mtu 1500
   
options=e400bb
ether 0c:c4:7a:bd:65:58
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: ix0 flags=1c
laggport: ix1 flags=1c




but when ix's ports are configured as lagg1, all laggports work properly. When
I  switch ix's ports as lagg0 and first in cloned_interfaces the problem
appears:



lagg0: flags=8843 metric 0 mtu 1500
   
options=e400bb
ether 0c:c4:7a:bd:65:58
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: ix0 flags=1c
laggport: ix1 flags=0<>
lagg1: flags=8843 metric 0 mtu 1500
   
options=6403bb
ether 00:1e:67:27:1d:5e
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: igb0 flags=1c
laggport: igb1 flags=1c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #8 from Cassiano Peixoto  ---
(In reply to Eric Joyner from comment #7)
So should i open a new PR related to driver update problem and netmap?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #7 from Eric Joyner  ---
Do we know who to assign this to, then? If it is actually a lagg problem and
not a driver-specific one.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Kevin Bowling  changed:

   What|Removed |Added

 CC||kbowl...@freebsd.org

--- Comment #6 from Kevin Bowling  ---
We're seeing this on cxgbe(4) as well, so I think it's related to if_lagg
locking changes and the LACP init code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||mfc-stable11?
   Keywords||regression
 Status|New |Open

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #5 from Cassiano Peixoto  ---
Hi guys,

It's a bug after commit r320897.

I have the same issue running an ix interface in netmap mode after this commit.
I had to downgrade ixgbe drivers to make it works again.

Looks like a bug after driver update to 3.2.12-k.

I'm copying the author of commit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #4 from veg...@tuxpowered.net ---
Sorry, I meant ixl-1.7.12 from Intel.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

veg...@tuxpowered.net changed:

   What|Removed |Added

 CC||veg...@tuxpowered.net

--- Comment #3 from veg...@tuxpowered.net ---
I have some Intel xl710 running failover lagg and I had an issue not totally
unlike this one. One of ports in lagg (and always the same one, unless they
were added in different order, then both would always work) would only send
frames but never receive them, so the router would become master on carp on
vlans on this lagg, never seeing carp advertisements of the primary router.
That was on FreeBSD 11.0, though. I used ixgbe-2.5.15 from Intel instead of the
one coming with Kernel and the issue was gone.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Cassiano Peixoto  changed:

   What|Removed |Added

 CC||freebsd-stable@FreeBSD.org,
   ||peixoto.cassi...@gmail.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"