Damjan,
I've been monitoring the build failures on the VPP gerrit queue and
found that the most recent failure for https://gerrit.fd.io/r/#/c/3531/
is due to a SEGV in vppinfra.
This can be seen in the XML output file of the Jenkins job:
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1863/
Selecting the "View" link next to output.xml in the Build Artifacts list
will load the output xml file in your browser:
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1863/artifact/csit/output.xml/*view*
The syslog output (search for "tail -n 100 /var/log/syslog") shows that
VPP is crashing on startup:
Oct 21 14:23:19 vagrant systemd[1]: Starting vector packet
processing engine...
Oct 21 14:23:19 vagrant kernel: [ 30.496420] igb_uio: module
verification failed: signature and/or required key missing -
tainting kernel
Oct 21 14:23:19 vagrant kernel: [ 30.496583] igb_uio: Use MSIX
interrupt by default
Oct 21 14:23:19 vagrant systemd[1]: Started vector packet processing
engine.
Oct 21 14:23:19 vagrant systemd[1]: vpp.service: Main process
exited, code=killed, status=11/SEGV
Oct 21 14:23:19 vagrant kernel: [ 30.505777] traps: vpp[2527]
general protection ip:7fa75dcc0710 sp:7ffe933e4298 error:0 in
libvppinfra.so.0.0.0[7fa75dca2000+76000]
Oct 21 14:23:19 vagrant systemd[1]: vpp.service: Unit entered failed
state.
Oct 21 14:23:19 vagrant systemd[1]: vpp.service: Failed with result
'signal'.
Oct 21 14:23:19 vagrant systemd[1]: vpp.service: Service hold-off
time over, scheduling restart.
Thanks,
-daw-
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev