Florian C. Smeets wrote: > i can trigger this kind of panic quite easily where running > mldonkey-devel port and downloading something via BitTorrent. > I just triggered this same panic with -CURRENT as of 1430 UTC today. A ping(1) was backed up due to link layer problems; after I manually repatched to a different switch port, CTRL-C'ing the ping process triggered the panic: a--- 192.168.123.ni18 ping statistic:cs --- sbflush_internal: cc 84 || mb 0 || mbcnt 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x3a panic() at panic+0x1d5 sbflush_internal() at sbflush_internal+0x6a sbrelease_internal() at sbrelease_internal+0x1c sofree() at sofree+0x141 soclose() at soclose+0x380 soo_close() at soo_close+0x52 fdrop_locked() at fdrop_locked+0xe6 closef() at closef+0x366 fdfree() at fdfree+0x5ca exit1() at exit1+0x34b sys_exit() at sys_exit+0xe syscall() at syscall+0x264 Xfast_syscall() at Xfast_syscall+0xab --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x80092a79c, rsp = 0x7ffffffee718, rbp = 0x7ffffffee8d0 --- Regards, BMSReceived on Wed Feb 14 2007 - 19:54:30 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:05 UTC