Bug #1783

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

Added by ftigeot about 5 years ago. Updated 8 months ago.

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

0%

Category:Kernel
Target version:4.2.x

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.


Related issues

Related to Bug #1361: panic: message could only be dropped in the same thread a... Closed

History

#1 Updated by tuxillo 8 months ago

  • Related to Bug #1361: panic: message could only be dropped in the same thread as the message port thread added

#2 Updated by tuxillo 8 months ago

  • Description updated (diff)
  • Category set to Kernel
  • Status changed from New to Feedback
  • Assignee deleted (0)
  • Target version set to 4.2.x

Hi,

The issue you are referring to is in status closed, can you still reproduce this panic?

Cheers,
Antonio Huete

#3 Updated by ftigeot 8 months ago

  • Status changed from Feedback to Closed

I haven't seen this panic in years. Closing.

Also available in: Atom PDF