panic: assertion: msg->ms_flags & MSGF_INTRANSIT

Peter Avalos pavalos at theshell.com
Fri Jun 29 18:40:27 PDT 2007


On Fri, Jun 29, 2007 at 06:19:00PM -0700, Matthew Dillon wrote:
> 
> :Head sources from the 22nd, I received this panic.  No core dump.
> :
> :panic: assertion: msg->ms_flags & MSGF_INTRANSIT in
> :lwkt_thread_replyport_remote
> :mp_lock = 00000000; cpuid = 1; Trace beginning at frame 0xd9e7bc88
> :panic(c0303d72,1,c02fdd2a,d9e7bcbc,d9e7bcbc) at panic+0x16d
> :panic(c02fdd2a,c03171e8,c02f2675,d9e7bd00,c3b280d0) at panic+0x16d
> :lwkt_thread_replyport_remote(e8962c28,0,d9e7bd38,c03300f4,286) at
> :...
> 
>     Shoot.  There isn't enough info to track it down.  The only
>     thing that can cause this is if a message is replied twice in
>     quick succession, or if the message flags are corrupted, or
>     the message is freed too early.  We'd need to know where the
>     message came from, which requires a core dump.
> 

Sucks.  Well regarding the dump...Did it not dump because of the panic,
or was it some other bug?  Normally I don't have problems getting core
dumps.

--Peter
Attachment:
pgp00012.pgp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgp00012.pgp
Type: application/octet-stream
Size: 189 bytes
Desc: "Description: PGP signature"
URL: <http://lists.dragonflybsd.org/pipermail/bugs/attachments/20070629/9e1fdd45/attachment-0017.obj>


More information about the Bugs mailing list