[PATCH][v3] hung_task: Panic after fixed number of hung tasks
Randy Dunlap
rdunlap at infradead.org
Tue Oct 14 12:37:30 AEDT 2025
Hi--
On 10/12/25 4:50 AM, lirongqing wrote:
> From: Li RongQing <lirongqing at baidu.com>
>
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index a51ab46..7d9a8ee 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -1992,14 +1992,20 @@
> the added memory block itself do not be affected.
>
> hung_task_panic=
> - [KNL] Should the hung task detector generate panics.
> - Format: 0 | 1
> + [KNL] Number of hung tasks to trigger kernel panic.
> + Format: <int>
> +
> + Set this to the number of hung tasks that must be
> + detected before triggering a kernel panic.
> +
> + 0: don't panic
> + 1: panic immediately on first hung task
> + N: panic after N hung tasks are detect
are detected
>
> - A value of 1 instructs the kernel to panic when a
> - hung task is detected. The default value is controlled
> - by the CONFIG_BOOTPARAM_HUNG_TASK_PANIC build-time
> - option. The value selected by this boot parameter can
> - be changed later by the kernel.hung_task_panic sysctl.
> + The default value is controlled by the
> + CONFIG_BOOTPARAM_HUNG_TASK_PANIC build-time option. The value
> + selected by this boot parameter can be changed later by the
> + kernel.hung_task_panic sysctl.
>
> hvc_iucv= [S390] Number of z/VM IUCV hypervisor console (HVC)
> terminal devices. Valid values: 0..8
--
~Randy
More information about the Linux-aspeed
mailing list