Project

General

Profile

Actions

Bug #1361

closed

panic: message could only be dropped in the same thread as the message port thread

Added by ftigeot over 15 years ago. Updated over 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

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")
---


Related issues 1 (0 open1 closed)

Related to Bug #1783: panic: message could only be dropped in the same thread as the message port threadClosed

Actions
Actions

Also available in: Atom PDF