linux-kernel - What methods or tools could be used to investigate the causes of hard or soft lockup?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAAvDm6buDWX1rMp9ncTw9=OQtXTYLPfXZSHg-2w5XEUxUNJEAA@mail.gmail.com>
Date:   Sat, 11 Jul 2020 17:04:21 +0800
From:   孙世龙 sunshilong <sunshilong369@...il.com>
To:     LKML <linux-kernel@...r.kernel.org>
Subject: What methods or tools could be used to investigate the causes of hard
 or soft lockup?

Hi, list

I have frequently faced sort lockups and hard lockups.
Here are some example logs:
1. Watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [cantest:1669]
2. NMI watchdog: Watchdog detected hard LOCKUP on CPU 0

What methods or tools could be used to investigate the causes of hard
or soft lockups?
I have been stuck with such problems for a long time.
I would be grateful if somebody shed some light on this issue.

Any advice on how to proceed?

Thank you for your attention to this matter.
Best regards.