[DragonFlyBSD - Bug #1783] (Closed) panic: message could only be dropped in the same thread as the message port thread
bugtracker-admin at leaf.dragonflybsd.org
bugtracker-admin at leaf.dragonflybsd.org
Tue Jan 20 12:22:43 PST 2015
Issue #1783 has been updated by ftigeot.
Status changed from Feedback to Closed
I haven't seen this panic in years. Closing.
----------------------------------------
Bug #1783: panic: message could only be dropped in the same thread as the message port thread
http://bugs.dragonflybsd.org/issues/1783#change-12554
* Author: ftigeot
* Status: Closed
* Priority: Normal
* Assignee:
* Category: Kernel
* Target version: 4.2.x
----------------------------------------
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.
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs
mailing list