Issue #1361 has been updated by tuxillo. Related to Bug #1783: panic: message could only be dropped in the same thread as the message port thread added
---------------------------------------- Bug #1361: panic: message could only be dropped in the same thread as the message port thread http://bugs.dragonflybsd.org/issues/1361#change-12531 * Author: ftigeot * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- System is Opteron-170, 2GB RAM, em0 NIC. DragonFly-2.2.0 Messages copied by hand, may be inaccurate. Here goes the panic message, without function arguments : --- panic: message could only be dropped in the same thread as the message port thread mp_lock = 00000000; cpuid = 0 Trace beginning at frame 0xda8cc890 panic panic lwkt_thread_dropmsg tcp_destroy_timermsg tcp_close tcp_drop tcp_notify in6_pcbnotify tcp6_ctlinput netmsg_pru_ctlinput netmsg_put_port lwkt_domsg so_pre_ctlinput icmp6_input ip6_input netisr_run ether_demux_oncpu ether_input_oncpu ether_input_handler netmsg_service netmsg_service_loop lwkt_exit Debugger("panic") --- -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
