~~~
*** hanginfo -v ****
ooooooo vmcore (6.4.0-150600.23.38-default) oooooooo
*** UNINTERRUPTIBLE threads, classified ***
================== Waiting in io_schedule ==================
... 3 pids. Youngest,oldest: 379710, 3517456 Ran ms ago: 72949, 1294417525
PID CMD CPU Ran ms ago STATE
-------- ------------ -- ------------- -----
379710 pacemakerd 7 72949 UN
1766947 kworker/41: 41 1220320028 UN
3517456 cp 22 1294417525 UN
Traceback (most recent call last):
File "/home/martin/pykdump-code/Extension/mpykdump.so/progs/hanginfo.py", line 672, in <module>
File "/home/martin/pykdump-code/Extension/mpykdump.so/progs/hanginfo.py", line 549, in classify_UN
File "/home/martin/pykdump-code/Extension/mpykdump.so/progs/hanginfo.py", line 462, in check_kthread_create_list
File "/home/martin/pykdump-code/LinuxDump/Tasks.py", line 1128, in decode_waitq
for l in ListHead(wq.task_list, "struct wait_queue").task_list:
File "/home/martin/pykdump-code/pykdump/highlevel.py", line 355, in __getattr
raise KeyError("<%s> does not have a field <%s>" % \
KeyError: '<struct __wait_queue=""> does not have a field <task_list>'
~~~</task_list></struct></module>
This is different from the hanginfo abort in ticket #9.
Caused by change of completion struct definition to use simple wait queues in kernel 5.7 and later. Fixed in [ad7ebe].
Related
Commit: [ad7ebe]