Open ngocphamm opened 7 years ago
cc: @strib
Here is the symbolicated backtrace:
panic(cpu 2 caller 0xffffff802dd94512): assertion failed: ifp->if_sndbyte_total >= len, file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.1.46/bsd/netinet/in_pcb.c, line: 3608
Backtrace (CPU 2), Frame : Return Address
0xffffff81377eba10 : 0xffffff802d86d366 handle_debugger_trap (in kernel) (debug.c:940)
0xffffff81377eba50 : 0xffffff802d998494 kdp_i386_trap (in kernel) (kdp_machdep.c:458)
0xffffff81377eba90 : 0xffffff802d98a429 kernel_trap (in kernel) (trap.c:782)
0xffffff81377ebb10 : 0xffffff802d81f190 trap_from_kernel (in kernel) + 38
0xffffff81377ebb30 : 0xffffff802d86cd8c panic_trap_to_debugger (in kernel) (debug.c:649)
0xffffff81377ebc60 : 0xffffff802d86cafc panic (in kernel) (debug.c:0)
0xffffff81377ebcc0 : 0xffffff802dd94512 sbfree (in kernel) (in_pcb.c:3608)
0xffffff81377ebce0 : 0xffffff802dd93f9c sbdrop (in kernel) (uipc_socket2.c:1923)
0xffffff81377ebd30 : 0xffffff802dd938e8 sbflush (in kernel) (uipc_socket2.c:1818)
0xffffff81377ebd70 : 0xffffff802dd8484f sowflush (in kernel) (uipc_socket.c:4478)
0xffffff81377ebd90 : 0xffffff802dd8452a sofreelastref (in kernel) (uipc_socket.c:1204)
0xffffff81377ebdc0 : 0xffffff802dd87262 soclose_locked (in kernel) (uipc_socket.c:1458)
0xffffff81377ebe10 : 0xffffff802dd87613 soclose (in kernel) (uipc_socket.c:1467)
0xffffff81377ebe30 : 0xffffff802dd060b3 closef_locked (in kernel) (kern_descrip.c:5225)
0xffffff81377ebea0 : 0xffffff802dd05d44 close_internal_locked (in kernel) (kern_descrip.c:2887)
0xffffff81377ebf00 : 0xffffff802dd0a644 close_nocancel (in kernel) (kern_descrip.c:2784)
0xffffff81377ebf40 : 0xffffff802de0e548 unix_syscall64 (in kernel) (systemcalls.c:382)
0xffffff81377ebfa0 : 0xffffff802d81f976 hndl_unix_scall64 (in kernel) + 22
It does not contain any kbfuse related functions. Therefore I don't think kbfuse (the Keybase kernel extension) is to blame for the panic. It seems that kbfs (the Keybase user space process), or a library it uses, is closing a network socket, which triggers the panic.
To me this looks like a bug in the High Sierra kernel. kbfs should not be able to make the kernel panic by closing a network socket. It would be best to report the panic to Apple. Have you seen the panic on Sierra, too, or have the panics started after upgrading to High Sierra?
For what it's worth, here's a Stack Overflow post with the same panic:
This person seems to conclude "HoRNDIS" was causing the crash for them -- do you use that?
@bfleischer FYI, the panic only started after upgrading to High Sierra
@cjb I don't use HoRNDIS. Have no idea what it is.
I'm not 100% sure if Keybase is responsible for the panics, but I see this line in all 4 kernel panics I got since late September (process name can be either
kbfs
orkeybase
. The kernel panics happened when I woke the computer up after the nights.BSD process name corresponding to current thread: kbfs
Below is the detail of the latest panic dump