Hi Steven, GDB shows that the vlib_process_get_events function always return ~0, except one time at start and lacp_schedule_periodic_timer is never runs after that. It's looks the same on both sides. I have added some debug info. Please look at the log:
########################### VPP1:9.58 ############################# Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:88: partner.state: 0x1, actor.state: 0x7 Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:89: LACP_START_SLOW_PERIODIC_TIMER Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:85: LACP_START_FAST_PERIODIC_TIMER Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:88: partner.state: 0x1, actor.state: 0x7 Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:89: LACP_START_SLOW_PERIODIC_TIMER Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:54:45 vpp1 vnet[1588]: lacp_schedule_periodic_timer:85: LACP_START_FAST_PERIODIC_TIMER Aug 17 10:54:45 vpp1 vnet[1588]: lacp_process:172: LACP_PROCESS_EVENT_START Aug 17 10:54:45 vpp1 vnet[1588]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:54:45 vpp1 vnet[1588]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:54:45 vpp1 vnet[1588]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:54:45 vpp1 vnet[1588]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:54:45 vpp1 vnet[1588]: lacp_process:169: LACP_PROCESS_TIMEOUT ########################### VPP2:6.155 ############################# Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:88: partner.state: 0x1, actor.state: 0x7 Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:89: LACP_START_SLOW_PERIODIC_TIMER Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:85: LACP_START_FAST_PERIODIC_TIMER Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:88: partner.state: 0x1, actor.state: 0x7 Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:89: LACP_START_SLOW_PERIODIC_TIMER Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:75: BEGIN Aug 17 10:55:09 vpp2 vnet[1722]: lacp_schedule_periodic_timer:85: LACP_START_FAST_PERIODIC_TIMER Aug 17 10:55:09 vpp2 vnet[1722]: lacp_process:172: LACP_PROCESS_EVENT_START Aug 17 10:55:10 vpp2 vnet[1722]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:55:10 vpp2 vnet[1722]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:55:10 vpp2 vnet[1722]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:55:10 vpp2 vnet[1722]: lacp_process:169: LACP_PROCESS_TIMEOUT Aug 17 10:55:10 vpp2 vnet[1722]: lacp_process:169: LACP_PROCESS_TIMEOUT Both of the hosts are bare metal. System information: # uname -a Linux vpp1 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz Stepping: 3 CPU MHz: 3500.000 CPU max MHz: 3500.0000 CPU min MHz: 800.0000 BogoMIPS: 6999.94 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu p ni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline _timer aes xsave avx f16c rdrand lahf_lm abm epb invpcid_single kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi 1 hle avx2 smep bmi2 erms invpcid rtm xsaveopt dtherm arat pln pts # hwinfo --short cpu: Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz Intel(R) Xeon(R) CPU E3-1275 v3 @ 3.50GHz, 3500 MHz keyboard: /dev/input/event0 Logitech Keyboard K120 monitor: Acer AL1916 graphics card: Intel Xeon E3-1200 v3 Processor Integrated Graphics Controller sound: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller storage: Intel 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] network: ens9f2 Intel I350 Gigabit Fiber Network Connection Intel I350 Gigabit Fiber Network Connection ens9f0 Intel I350 Gigabit Fiber Network Connection Intel I350 Gigabit Fiber Network Connection enp17s0 Intel I210 Gigabit Network Connection enp16s0 Intel I210 Gigabit Network Connection ens9f3 Intel I350 Gigabit Fiber Network Connection Intel I350 Gigabit Fiber Network Connection ens9f1 Intel I350 Gigabit Fiber Network Connection Intel I350 Gigabit Fiber Network Connection network interface: enp17s0 Ethernet network interface ens9f2 Ethernet network interface ens9f0 Ethernet network interface enp16s0 Ethernet network interface lo Loopback network interface ens9f3 Ethernet network interface ens9f1 Ethernet network interface disk: /dev/sda ST2000LM007-1R81 partition: /dev/sda1 Partition /dev/sda2 Partition /dev/sda5 Partition usb controller: Intel 8 Series/C220 Series Chipset Family USB EHCI #2 Intel 8 Series/C220 Series Chipset Family USB EHCI #1 Intel 8 Series/C220 Series Chipset Family USB xHCI bios: BIOS bridge: PLX PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch PLX PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA Intel Xeon E3-1200 v3 Processor DRAM Controller PLX PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch PLX PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA Intel Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller PLX PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch PLX PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA PLX PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch PLX PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA PLX PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch Intel 8 Series/C220 Series Chipset Family PCI Express Root Port #5 PLX PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA Intel 8 Series/C220 Series Chipset Family PCI Express Root Port #1 Intel C226 Series Chipset Family Server Advanced SKU LPC Controller Intel Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller PLX PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch Intel 8 Series/C220 Series Chipset Family PCI Express Root Port #6 PLX PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA hub: Intel Hub Linux Foundation 2.0 root hub Linux Foundation 2.0 root hub Linux Foundation 3.0 root hub Intel Hub Linux Foundation 2.0 root hub memory: Main Memory unknown: FPU DMA controller PIC Keyboard controller PS/2 Controller Intel 8 Series/C220 Series Chipset Family SMBus Controller Intel 8 Series Chipset Family Thermal Management Controller Intel 8 Series/C220 Series Chipset Family MEI Controller #1 /dev/ttyS0 16550A /dev/ttyS1 16550A /dev/input/event1 Logitech Keyboard K120 Best Regards, Aleksander On Thu, Aug 16, 2018 at 09:11 PM, steven luong wrote: > > > > Aleksander, > > > > > > > > This problem should be easy to figure out if you can gdb the code. When > the very first slave interface is added to the bonding group via the > command “bond add BondEthernet0 GigabitEthnerneta/0/0/1”, > > > > > > > > - The PTX machine schedules the interface with the periodic timer via > lacp_schedule_periodic_timer(). > > > > - lacp-process is signaled with event_start to enable with periodic timer. > lacp_process() only calls lacp_periodic() if “enabled” is set . > > > > > > > > One of these two things is not happening in your platform/environment and > I cannot explain why with bare eyes. GDB the above two places will solve > the mystery. Of course, it works in my environment all the times and I am > not seeing the problem. What is your working environment? VM or bare > metal? What flavor of linux distro and version? I am running VPP on > Ubuntu-1604 on bare metal. > > > > > > > > Steven > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10195): https://lists.fd.io/g/vpp-dev/message/10195 Mute This Topic: https://lists.fd.io/mt/24525535/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
