[LU-15650] sanity-lnet: test_102 Timeout occurred, last suite running was sanity-lnet Created: 14/Mar/22  Updated: 29/Mar/22  Resolved: 23/Mar/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates LU-15616 sanity-lnet test_226: Timeout occurre... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Artem Blagodarenko <artem.blagodarenko@hpe.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/7fcc16a2-7808-4ded-9a59-4fce9996149f

INFO: task socknal_sd00_01:952398 blocked for more than 120 seconds.
[Sun Mar 13 13:26:59 2022] Tainted: G W OE --------- - - 4.18.0-240.22.1.el8_3.x86_64 #1
[Sun Mar 13 13:26:59 2022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Sun Mar 13 13:26:59 2022] socknal_sd00_01 D 0 952398 2 0x80004080
[Sun Mar 13 13:26:59 2022] Call Trace:
[Sun Mar 13 13:26:59 2022] __schedule+0x2c4/0x700
[Sun Mar 13 13:26:59 2022] schedule+0x38/0xa0
[Sun Mar 13 13:26:59 2022] schedule_preempt_disabled+0xa/0x10
[Sun Mar 13 13:26:59 2022] __mutex_lock.isra.5+0x2d0/0x4a0
[Sun Mar 13 13:26:59 2022] lnet_peerni_by_nid_locked+0x53/0x130 [lnet]
[Sun Mar 13 13:26:59 2022] ? cfs_percpt_lock+0x16/0xf0 [libcfs]
[Sun Mar 13 13:26:59 2022] lnet_parse+0x6f3/0x1430 [lnet]
[Sun Mar 13 13:26:59 2022] ksocknal_process_receive+0x4d8/0xdb0 [ksocklnd]
[Sun Mar 13 13:26:59 2022] ksocknal_scheduler+0x188/0x17d0 [ksocklnd]
[Sun Mar 13 13:26:59 2022] ? __schedule+0x2cc/0x700
[Sun Mar 13 13:26:59 2022] ? finish_wait+0x80/0x80
[Sun Mar 13 13:26:59 2022] ? ksocknal_recv+0x290/0x290 [ksocklnd]
[Sun Mar 13 13:26:59 2022] kthread+0x112/0x130
[Sun Mar 13 13:26:59 2022] ? kthread_flush_work_fn+0x10/0x10
[Sun Mar 13 13:26:59 2022] ret_from_fork+0x35/0x40



 Comments   
Comment by Chris Horn [ 23/Mar/22 ]

It's a different stack trace, but same issue as LU-15616 . The patch there will resolve this issue.

Comment by Chris Horn [ 23/Mar/22 ]

Duplicates LU-15616

Generated at Sat Feb 10 03:20:09 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.