Den 2023-09-26 kl. 03:10, skrev Yu Kuai:
It'll be much helper for developers to collect kernel stack for all stuck thread(and it'll be much better to use add2line).Presuming I can re-create the problem, let me know what I should do to collect that information for you. I'm very much a newbie in that area.You can use following cmd:for pid in `ps -elf | grep " D " | awk '{print $4}'`; do ps $pid; cat /proc/$pid/stack; doneThanks, Kuai
for pid in `ps -elf | grep " D " | awk '{print $4}'`; do ps $pid; cat /proc/$pid/stack; done
PID TTY STAT TIME COMMAND 4017 tty1 D+ 0:00 e2fsck /dev/md126 [<0>] md_write_start+0x191/0x310 [<0>] raid5_make_request+0x90/0x1230 [raid456] [<0>] md_handle_request+0x129/0x210 [<0>] __submit_bio+0x7f/0x110 [<0>] submit_bio_noacct_nocheck+0x150/0x360 [<0>] __block_write_full_folio+0x1d8/0x3f0 [<0>] writepage_cb+0x11/0x70 [<0>] write_cache_pages+0x13a/0x390 [<0>] do_writepages+0x15b/0x1e0 [<0>] filemap_fdatawrite_wbc+0x5a/0x80 [<0>] __filemap_fdatawrite_range+0x53/0x80 [<0>] filemap_write_and_wait_range+0x3a/0xa0 [<0>] blkdev_put+0x116/0x1c0 [<0>] blkdev_release+0x22/0x30 [<0>] __fput+0xe5/0x290 [<0>] task_work_run+0x51/0x80 [<0>] exit_to_user_mode_prepare+0x132/0x140 [<0>] syscall_exit_to_user_mode+0x1d/0x50 [<0>] do_syscall_64+0x46/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 PID TTY STAT TIME COMMAND cat: /proc/5266/stack: Filen eller katalogen finns inte -- --------------------------------------------------------------- - Joel Parthemore - philosopher - academic proofreader -------- - English teacher - technology instructor - editor ------------ - "We are all in the gutter, but some of us are looking at the- - "stars." - Oscar Wilde -------------------------------------- ---------------------------------------------------------------
<<attachment: smime.p7s>>
