All y'all referring to a whole separate kernel module, hangcheck-timer.ko? If so, it appears that you can set the timeouts (there is more than one) via kernel parameters. I found this, which has a long comment at the top explaining what it does: https://github.com/spotify/linux/blob/master/drivers/char/hangcheck-timer.c Here's the comment (reformatted): The hangcheck-timer driver uses the TSC to catch delays that jiffies does not notice. A timer is set. When the timer fires, it checks whether it was delayed and if that delay exceeds a given margin of error. The hangcheck_tick module parameter takes the timer duration in seconds. The hangcheck_margin parameter defines the margin of error, in seconds. The defaults are 60 seconds for the timer and 180 seconds for the margin of error. IOW, a timer is set for 60 seconds. When the timer fires, the callback checks the actual duration that the timer waited. If the duration exceeds the alloted time and margin (here 60 + 180, or 240 seconds), the machine is restarted. A healthy machine will have the duration match the expected timeout very closely. There are four parameters to this kernel module: MODULE_PARM_DESC(hangcheck_tick, "Timer delay."); MODULE_PARM_DESC(hangcheck_margin, "If the hangcheck timer has been delayed more than hangcheck_margin seconds, the driver will fire."); MODULE_PARM_DESC(hangcheck_reboot, "If nonzero, the machine will reboot when the timer margin is exceeded."); MODULE_PARM_DESC(hangcheck_dump_tasks, "If nonzero, the machine will dump the system task state when the timer margin is exceeded."); The first two are times measured in seconds. hangcheck_tick defaults to 180 seconds and hangcheck_margin defaults to 60 seconds, at least in the Spotify kernel version I found on github. Eddie -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
