Re: Automated report: NetBSD-current/i386 test failure (l2tp)

2020-10-25 Thread Roy Marples

On 23/10/2020 08:25, Andreas Gustafsson wrote:

Roy Marples wrote:

This is rump crashing and I don't know why.


If the rump kernel crashes in the test, that likely means the real
kernel will crash in actual use.


I can't get a backtrace to tell me where the problem is.


I managed to get one this way:

   sysctl -w kern.defcorename="/tmp/%n.core"
   cd /usr/tests/net/if_l2tp
   ./t_l2tp l2tp_basic_ipv4overipv4
   gdb rump_server /tmp/rump_server.core

It looks like this:


Thanks for that, it should now be fixed.

Roy


Re: Automated report: NetBSD-current/i386 test failure (l2tp)

2020-10-23 Thread Andreas Gustafsson
Roy Marples wrote:
> This is rump crashing and I don't know why.

If the rump kernel crashes in the test, that likely means the real
kernel will crash in actual use.

> I can't get a backtrace to tell me where the problem is.

I managed to get one this way:

  sysctl -w kern.defcorename="/tmp/%n.core"
  cd /usr/tests/net/if_l2tp
  ./t_l2tp l2tp_basic_ipv4overipv4
  gdb rump_server /tmp/rump_server.core

It looks like this:

  (gdb) bt
  #0  0x752206d751ea in _lwp_kill () from /usr/lib/libc.so.12
  #1  0x752206d756e5 in abort ()
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/libc/stdlib/abort.c:74
  #2  0x7522076088bf in rumpuser_exit (rv=rv@entry=-1)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librumpuser/rumpuser.c:236
  #3  0x7522082c2b74 in cpu_reboot (howto=, 
  bootstr=)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librump/../../sys/rump/librump/rumpkern/emul.c:429
  #4  0x75220827b08d in kern_reboot (howto=4, bootstr=0x0)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librump/../../sys/rump/../kern/kern_reboot.c:73
  #5  0x752208279efe in vpanic (
  fmt=0x752205ea5428 "kernel %sassertion \"%s\" failed: file \"%s\", line 
%d ", ap=0x75220319fc88)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librump/../../sys/rump/../kern/subr_prf.c:290
  #6  0x75220825f298 in kern_assert (fmt=)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librump/../../sys/rump/../lib/libkern/kern_assert.c:51
  #7  0x752205e9fa7d in if_percpuq_enqueue (ipq=0x0, m=0x752208061650)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/sys/rump/net/lib/libnet/../../../../net/if.c:911
  #8  0x752204a03801 in in_l2tp_input (eparg=, 
  proto=, off=20, m=0x752208061858)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/sys/rump/net/lib/libl2tp/../../../../netinet/in_l2tp.c:349
  #9  in_l2tp_input (m=0x752208061858, off=20, proto=, 
  eparg=)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/sys/rump/net/lib/libl2tp/../../../../netinet/in_l2tp.c:249
  #10 0x752205e75097 in encap4_input (m=0x752208061858, off=20, proto=115)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/sys/rump/net/lib/libnet/../../../../netinet/ip_encap.c:357
  #11 0x752205e7d465 in ip_input (ifp=, m=)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/sys/rump/net/lib/libnet/../../../../netinet/ip_input.c:821
  #12 ipintr (arg=)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/sys/rump/net/lib/libnet/../../../../netinet/ip_input.c:412
  #13 0x7522082c265c in sithread (arg=)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librump/../../sys/rump/librump/rumpkern/intr.c:180
  #14 0x7522082bf52e in threadbouncer (arg=0x75220883bac0)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/librump/../../sys/rump/librump/rumpkern/threads.c:90
  #15 0x75220720bf7e in pthread__create_tramp (cookie=0x7522085a4800)
  at 
/tmp/build/2020.10.22.11.21.42-amd64-debug/src/lib/libpthread/pthread.c:560
  #16 0x752206c91dc0 in ?? () from /usr/lib/libc.so.12

-- 
Andreas Gustafsson, g...@gson.org


Re: Automated report: NetBSD-current/i386 test failure (l2tp)

2020-10-22 Thread Roy Marples

Hi Andreas

On 22/10/2020 09:00, Andreas Gustafsson wrote:

Hi Roy,

On Oct 16, the NetBSD Test Fixture wrote:

The newly failing test cases are:

 net/if_l2tp/t_l2tp:l2tp_basic_ipv4overipv4
 net/if_l2tp/t_l2tp:l2tp_basic_ipv4overipv6
 net/if_l2tp/t_l2tp:l2tp_basic_ipv6overipv4
 net/if_l2tp/t_l2tp:l2tp_basic_ipv6overipv6
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_ah_hmacsha512
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_ah_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_esp_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_esp_rijndaelcbc
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_ah_hmacsha512
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_ah_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_esp_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_esp_rijndaelcbc
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_ah_hmacsha512
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_ah_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_esp_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_esp_rijndaelcbc
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_ah_hmacsha512
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_ah_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_esp_null
 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_esp_rijndaelcbc


These are still failing as of 2020.10.21.15.12.15, and the commit that
triggered the failures has now been identified:

   2020.10.15.02.54.10 roy src/sys/net/if_l2tp.c 1.44

For logs, see

   
http://www.gson.org/netbsd/bugs/build/amd64/commits-2020.10.html#2020.10.15.02.54.10


This is rump crashing and I don't know why.
I can't get a backtrace to tell me where the problem is.

Roy


Re: Automated report: NetBSD-current/i386 test failure (l2tp)

2020-10-22 Thread Andreas Gustafsson
Hi Roy,

On Oct 16, the NetBSD Test Fixture wrote:
> The newly failing test cases are:
> 
> net/if_l2tp/t_l2tp:l2tp_basic_ipv4overipv4
> net/if_l2tp/t_l2tp:l2tp_basic_ipv4overipv6
> net/if_l2tp/t_l2tp:l2tp_basic_ipv6overipv4
> net/if_l2tp/t_l2tp:l2tp_basic_ipv6overipv6
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_ah_hmacsha512
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_ah_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_esp_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_esp_rijndaelcbc
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_ah_hmacsha512
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_ah_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_esp_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_tunnel_esp_rijndaelcbc
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_ah_hmacsha512
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_ah_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_esp_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_transport_esp_rijndaelcbc
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_ah_hmacsha512
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_ah_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_esp_null
> net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv6_tunnel_esp_rijndaelcbc

These are still failing as of 2020.10.21.15.12.15, and the commit that
triggered the failures has now been identified:

  2020.10.15.02.54.10 roy src/sys/net/if_l2tp.c 1.44

For logs, see

  
http://www.gson.org/netbsd/bugs/build/amd64/commits-2020.10.html#2020.10.15.02.54.10

-- 
Andreas Gustafsson, g...@gson.org