Actions
Bug #1783
closed
panic: message could only be dropped in the same thread as the message port thread
Start date:
Due date:
% Done:
0%
Estimated time:
Description
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)
run.
The panic message and stack trace are identical to the ones in issue 1361:
http://bugs.dragonflybsd.org/issue1361
It seems the bug was not resolved after all.
Kernel and vmcore dumps available on request.
Updated by 
Updated by
Actions