Hi Ying,
Thank you very much for letting me know.Do we suspect any related ioctl()
patches?. could you please point me to link where we can review the TIPC
patches that went in the kernel.?.
Much appreciate the help.
thanks & regardsMahesh kumar.L
On Monday, 15 July, 2019, 02:56:32 am GMT-7, Ying Xue
<ying....@windriver.com> wrote:
On 7/13/19 11:58 AM, Mahesh Kumar via tipc-discussion wrote:
> Tipc Team,
>
> Greetings!.
> I have been using TIPC for about a year without any issueHowever the TIPC
> tool is bailing out when I tried to set address, bearer
>
>
> / # tipc node set addr 1.1.100
>
> error: Operation not permitted
>
> / # tipc bearer enable media eth dev ieobc
>
> error: Invalid argument
>
> / #
>
> I am using the new kernel now;
> uname -aLinux 2c3f0b001900_1_RP_0 4.4.180 #1 SMP Tue Jun 25 15:36:10 PDT
> 2019 x86_64 x86_64 x86_64 GNU/Linux
> dmesg output ; grep -i TIPC d.txt[ 29.436599] tipc: Activated (version
> 2.0.0)[ 29.436768] tipc: Started in single node mode
Suspected some TIPC patches integrated through 4.4.180 release
introduced regression. The most simplest method to identify the issue is
to revert some TIPC patches to identify which ones caused the regression.
>
> [2c3f0b001900_1_RP_0:/]$ tipc-config -ntType Lower Upper Port
> Identity Publication Scope0 16781313 16781313
> <1.1.1:0> 16781313 zone1 1 1
> <1.1.1:483390874> 483390875 node1 88 88
> <1.1.1:2870943326> 2870943327 zone15003 5 5
> <1.1.1:3556781096> 3556781097 zone[2c3f0b001900_1_RP_0:/]$
>
> please let me know if any issue.
> thanks & regardsMahesh kumar.L
>
>
> _______________________________________________
> tipc-discussion mailing list
> tipc-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
