Re: [Tipc-discussion] kernel hang report, and also any way to dump tipc messages?

[Jon M. <jon...@er...>]

Try these two. You had not set the "domain" value
in sockaddr-tipc, which embarassing enough led to a
kernel crash.  After one of my latest changes there
was a missing check for "wild" addresses in the
send code. It is now fixed and checked in.

/Jon

PS: If you try with SOCK_RDM instead of SOCK_DGRAM
you will see your message bounce back with error code
"TIPC_NO_NODE" at such types of user error, instead of just
seeing it disappearing.

Chris Friesen wrote:

> Mark Haverkamp wrote:
>
>> If you have sysrq compiled in you can get a task list dump and a dump of
>> what the current processor is doing (assuming its not really dead).  It
>> may have some clues as to what is going on.
>
>
> Not compiled in currently, but I can add it and see if I can get more 
> info.
>
> Chris