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

[Sepherosa Ziehau <sepherosa@xxxxxxxxx>]

On Wed, May 13, 2009 at 3:29 PM, Francois Tigeot <ftigeot@wolfpond.org> wrote:
> System is Opteron-170, 2GB RAM, em0 NIC.
> DragonFly-2.2.0
>
> Messages copied by hand, may be inaccurate.

Please cherry-pick following commits from devel branch on my leaf repo:
e6f59cdaeb525222d0a062f07fe3ae8b1b7e5167
9276e0f0258fd1eb5c68c99ca3abe35634b085c6
e9f8c2a65277b6b55d46a4e8d2dfe3e2fd3c1f7e
8b81bbf63c8b6bf4af3377afa4718752bc45d134

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



-- 
Live Free or Die