if_wg on BeagleBone black
Hey folks,
here is what I get when trying to ping anything else after if_wg is up and running on my BeagleBone Black:
root@beagle:~ # wg show
interface: wg0
public key: <removed>
private key: (hidden)
listening port: 39856
peer: <removed>
preshared key: (hidden)
endpoint: <removed>
allowed ips: 10.11.12.0/24
root@beagle:~ # ping 10.11.12.1
PING 10.11.12.1 (10.11.12.1): 56 data bytes
Fatal kernel mode data abort: 'Translation Fault (L1)' on read
trapframe: 0xd7195be0
FSR=00000005, FAR=00000278, spsr=40000013
r0 =00000000, r1 =00000000, r2 =00000001, r3 =00000000 r4 =d1626a18, r5 =d1626b2c, r6 =0000005c, r7 =00000000 r8 =d159c000, r9 =d1493900, r10=d7cd7aa8, r11=d7195c78 r12=d7b378f8, ssp=d7195c70, slr=d7b14c80, pc =c042f854
panic: Fatal abort
cpuid = 0
time = 1652353064
KDB: stack backtrace:
#0 0xc0355b70 at kdb_backtrace+0x48
#1 0xc02fcb50 at vpanic+0x170
#2 0xc02fc9e0 at vpanic+0
#3 0xc061bc14 at abort_align+0
#4 0xc061b704 at abort_handler+0x2a0
#5 0xc05fac68 at exception_exit+0
#6 0xc042f854 at if_inc_counter+0xc
#7 0xd7b14c80 at wg_softc_handshake_receive+0x8d0
#8 0xc035466c at gtaskqueue_run_locked+0x1b8
#9 0xc0354204 at gtaskqueue_thread_loop+0x1b0
#10 0xc02b4b38 at fork_exit+0xc0
#11 0xc05fabf8 at swi_exit+0
Uptime: 3m23s
Automatic reboot in 15 seconds - press a key on the console to abort
Do you know, what may be the cause?
Some stuff on the path suggests some counters are misaligned.
Regards
Konrad Sewiłło-Jopek
Quoted 45 lines · Konrad Sewillo-Jopek
Hey folks,
here is what I get when trying to ping anything else after
if_wgis up and running on my BeagleBone Black:root@beagle:~ # wg show
interface: wg0
public key: <removed>
private key: (hidden)
listening port: 39856peer: <removed>
preshared key: (hidden)
endpoint: <removed>
allowed ips: 10.11.12.0/24
root@beagle:~ # ping 10.11.12.1
PING 10.11.12.1 (10.11.12.1): 56 data bytes
Fatal kernel mode data abort: 'Translation Fault (L1)' on read
trapframe:0xd7195be0
FSR=00000005, FAR=00000278, spsr=40000013
r0 =00000000, r1 =00000000, r2 =00000001, r3 =00000000 r4 =d1626a18, r5 =d1626b2c, r6 =0000005c, r7 =00000000 r8 =d159c000, r9 =d1493900, r10=d7cd7aa8, r11=d7195c78 r12=d7b378f8, ssp=d7195c70, slr=d7b14c80, pc =c042f854panic: Fatal abort
cpuid = 0
time = 1652353064
KDB: stack backtrace:
#00xc0355b70atkdb_backtrace+0x48
#10xc02fcb50atvpanic+0x170
#20xc02fc9e0at vpanic+0
#30xc061bc14at abort_align+0
#40xc061b704atabort_handler+0x2a0
#50xc05fac68at exception_exit+0
#60xc042f854atif_inc_counter+0xc
#70xd7b14c80atwg_softc_handshake_receive+0x8d0
#80xc035466catgtaskqueue_run_locked+0x1b8
#90xc0354204atgtaskqueue_thread_loop+0x1b0
#100xc02b4b38atfork_exit+0xc0
#110xc05fabf8at swi_exit+0
Uptime: 3m23s
Automatic reboot in 15 seconds - press a key on the console to abort
Quoted 3 lines
Do you know, what may be the cause?
Some stuff on the path suggests some counters are misaligned.
This looks like FreeBSD, which version/branch is this from? If this is 13.1, you'll need to rebuild the kmod -- there was a KBI break somewhere, and it wasn't reported during any of the -BETA/-RC otherwise I would've tried to track it down and mitigate it. :-(
Thanks,
Kyle Evans