the sysem panics when using several ppp (tunx) tunnels using ppp over tcp. the crash files are on http://www.k1.com.br/crash the trace can be found on: http://www.k1.com.br/crash/core.txt.8 seems that a problem on detach the ppp interface... if I stop all the ppp process, the system does not panics.... This machine is a pppoi server that holds serveral ppp connections
Created attachment 203059 [details] backtrace
--- trap 0xc, eip = 0x1053069, esp = 0x1c3b08f4, ebp = 0x1c3b091c --- in_pcbpurgeif0(8757068,8e44400,8e44400,8e44400,8e4440c,...) at in_pcbpurgeif0+0xf9/frame 0x1c3b091c in_ifdetach(8e44400,8e444e8,10,f261b0,2,...) at in_ifdetach+0x6b/frame 0x1c3b0938 if_detach_internal(0,8f2d380,1e54f780,1c3b09d0,fd80bf,...) at if_detach_internal+0x844/frame 0x1c3b0990 if_detach(8e44400,8e99e1c,8e99e00,0,84182a0,...) at if_detach+0x30/frame 0x1c3b09a4 tun_destroy(8f2d380,8f2d380,8f2d380,84182a0,1c3b0a10,...) at tun_destroy+0xaf/frame 0x1c3b09d0 tun_clone_destroy(879a180,8e44400,2,879a1b0,84182a0,...) at tun_clone_destroy+0x6a/frame 0x1c3b09e8 if_clone_destroyif(879a180,8e44400,1eb52c30,1c3b0a38,eb255e,...) at if_clone_destroyif+0xfd/frame 0x1c3b0a10 if_clone_destroy(1c3b0b50,19c,1ebe6240,1c3b0ab0,ffbfe6e4,...) at if_clone_destroy+0x18f/frame 0x1c3b0a38 ifioctl(1eb52c30,80206979,1c3b0b50,8f2d380,2,...) at ifioctl+0x5a8/frame 0x1c3b0ac8 soo_ioctl(1ebfea80,80206979,1c3b0b50,1ec97500,8f2d380,...) at soo_ioctl+0x1be/frame 0x1c3b0af4 kern_ioctl(8f2d380,1,80206979,1c3b0b50,8757078,...) at kern_ioctl+0x234/frame 0x1c3b0b30 sys_ioctl(8f2d380,8f2d604,0,0,602,...) at sys_ioctl+0x120/frame 0x1c3b0be8 syscall(1c3b0ce8,3b,3b,3b,1,...) at syscall+0x3e5/frame 0x1c3b0cdc Xint0x80_syscall() at PTDpde+0x43bf/frame 0x1c3b0cdc --- syscall (54, FreeBSD ELF32, sys_ioctl), eip = 0x285125ef, esp = 0xffbfe650, ebp = 0xffbfe678 ---
Upgrading, I noticed freebsd-update says it is going to 12.0-RELEASE-p4 but I think I was still on p1 and never received any update notices for p2 or p3. In any case, my laptop updated just fine but my VPS server on a Linux VM panics with vm_fault_hold: fault on nofault entry, addr: 0 I understand this bug report is for STABLE but it appears to be the same issue. I don't know where to go from here.
(In reply to Rob Belics from comment #3) I was able to do "freebsd-update rollback" and I am now on RELEASE-p3. I guess I mis-remember upgrading from p1 to p3 but, in any case, my system is now up and running. However, I do not know how to proceed with this upgrade to p4.
^Triage: mfc-stable12 is now OBE. To submitter: was this problem ever resolved?
^Triage: feedback timeout (> 3 months).