Bug #1783

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

Added by ftigeot over 4 years ago.

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


Target version:-


I just got this panic tonight.

The system is a Core 2 Duo running DragonFly 2.6.3/x86-64.
The crash occurred juste a little bit after 3am, during the daily periodic(8)

The panic message and stack trace are identical to the ones in issue 1361:

It seems the bug was not resolved after all.

Kernel and vmcore dumps available on request.

Also available in: Atom PDF