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 tuxillo almost 10 years ago
- Related to Bug #1361: panic: message could only be dropped in the same thread as the message port thread added
Updated by tuxillo almost 10 years ago
- Description updated (diff)
- Category set to Kernel
- Status changed from New to Feedback
- Assignee deleted (
0) - Target version set to 4.2
Hi,
The issue you are referring to is in status closed, can you still reproduce this panic?
Cheers,
Antonio Huete
Updated by ftigeot almost 10 years ago
- Status changed from Feedback to Closed
I haven't seen this panic in years. Closing.
Actions