https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082015-01-19T14:02:51ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1783: panic: message could only be dropped in the same thread as the message port threadhttps://bugs.dragonflybsd.org/issues/1783?journal_id=125302015-01-19T14:02:51Ztuxillo
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/1361">Bug #1361</a>: panic: message could only be dropped in the same thread as the message port thread</i> added</li></ul> DragonFlyBSD - Bug #1783: panic: message could only be dropped in the same thread as the message port threadhttps://bugs.dragonflybsd.org/issues/1783?journal_id=125322015-01-19T14:06:52Ztuxillo
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/12532/diff?detail_id=2417">diff</a>)</li><li><strong>Category</strong> set to <i>Kernel</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> deleted (<del><i>0</i></del>)</li><li><strong>Target version</strong> set to <i>4.2</i></li></ul><p>Hi,</p>
<p>The issue you are referring to is in status closed, can you still reproduce this panic?</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #1783: panic: message could only be dropped in the same thread as the message port threadhttps://bugs.dragonflybsd.org/issues/1783?journal_id=125542015-01-20T20:22:43Zftigeot
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>I haven't seen this panic in years. Closing.</p>