Hi Azad, Happy to hear you found the solution. This version of TIPC is so old that I just feel relieved if I don't have to troubleshoot it.
///jon > -----Original Message----- > From: Azad N [mailto:[email protected]] > Sent: Monday, March 19, 2018 08:46 > To: [email protected] > Subject: Re: [tipc-discussion] Soft Lock issue in tipc_link_send_proto_msg > > Hi > > I figure out the solution to this issue, I forgot to apply the patch given > below. > After applying this patch the problem goes away. > https://sourceforge.net/p/tipc/mailman/message/31462458/ > > Regards > Azad N > > On Sat, Mar 17, 2018 at 4:56 PM, Azad N <[email protected]> wrote: > > > Hi > > > > We are using RHEL kernel versions (3.10.0-514.41.1, > > 3.10.0-693.el7.x86_64) > > > > On 3.10.0-514 we are getting a "Soft Lock" Issue while using TIPC in > > two node cluster. > > The same issue is not occurring in 3.10.0-693. Information in RHEL > > errata does not seem to specifically address this issue. > > > > Will appreciate if someone can provide any information as to what is > > causing the issue in 3.10.0-514. > > > > Following is the backtrace. > > > > : [<ffffffff8155e724>] ? consume_skb+0x34/0x80 > > : [<ffffffff8156f1f1>] dev_hard_start_xmit+0x171/0x3b0 > > : [<ffffffff81596864>] sch_direct_xmit+0x104/0x200 > > : [<ffffffff81571dec>] __dev_queue_xmit+0x23c/0x570 > > : [<ffffffff81572130>] dev_queue_xmit+0x10/0x20 > > : [<ffffffffa02c1e46>] send_msg+0xc6/0xf0 [tipc] > > : [<ffffffffa02b5d14>] tipc_link_send_proto_msg+0x464/0x500 [tipc] > > : [<ffffffffa02b6330>] ? link_start+0x40/0x40 [tipc] > > : [<ffffffffa02b6104>] link_state_event+0x354/0x540 [tipc] > > : [<ffffffffa02b639d>] link_timeout+0x6d/0x160 [tipc] > > : [<ffffffff81095b46>] call_timer_fn+0x36/0x110 > > : [<ffffffffa02b6330>] ? link_start+0x40/0x40 [tipc] > > : [<ffffffff81098837>] run_timer_softirq+0x237/0x340 > > : [<ffffffff8108f2cf>] __do_softirq+0xef/0x280 > > : [<ffffffff8169849c>] call_softirq+0x1c/0x30 > > : [<ffffffff8102d365>] do_softirq+0x65/0xa0 > > : [<ffffffff8108f665>] irq_exit+0x115/0x120 > > : [<ffffffff81699115>] smp_apic_timer_interrupt+0x45/0x60 > > : [<ffffffff8169765d>] apic_timer_interrupt+0x6d/0x80 : <EOI> > > > > > > # cat /var/log/messages | grep "soft lock" > > kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [t:2802] > > kernel: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 21s! > > [ksoftirqd/1:13] > > kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [t:2802] > > kernel: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 21s! > > [kworker/1:0H:15] > > ... > > > > > > > > > > Regards > > Azad N > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most engaging > tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > tipc-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tipc-discussion ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
