Bug #1361

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

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

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

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

History

#1 Updated by sepherosa over 5 years ago

IPv6 uses netisr0 as TCP working thread; tcp_timer code is not aware of it yet.
I will send you a patch ASAP.

Best Regards,
sephe

#2 Updated by sepherosa over 5 years ago

On Wed, May 13, 2009 at 3:29 PM, Francois Tigeot <> 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
>

#3 Updated by ftigeot over 5 years ago

On Wed, May 13, 2009 at 09:28:48PM +0800, Sepherosa Ziehau wrote:
> On Wed, May 13, 2009 at 3:29 PM, Francois Tigeot <> 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

Due to other issues, I have upgraded to DragonFly-2.3.1.

How can I know if these commits were included in the new sources ?

#4 Updated by sepherosa over 5 years ago

On Mon, May 18, 2009 at 3:26 PM, Francois Tigeot <> wrote:
> On Wed, May 13, 2009 at 09:28:48PM +0800, Sepherosa Ziehau wrote:
>> On Wed, May 13, 2009 at 3:29 PM, Francois Tigeot <> 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
>
> Due to other issues, I have upgraded to DragonFly-2.3.1.

I committed it to HEAD yesterday.
8b81bbf63c8b6bf4af3377afa4718752bc45d134 contains the fix.

Best Regards,
sephe

#5 Updated by luxh over 5 years ago

dragonfly repo, 3db1c8a32e7f0bbaf8f0095e3511f94f6eb8a336

Also available in: Atom PDF