On 2019/05/03 5:46, Daniel Vetter wrote: > There's the hung_task_panic sysctl, but that's a bit an extreme measure. > As a fallback taint at least the machine. > > Our CI uses this to decide when a reboot is necessary, plus to figure > out whether the kernel is still happy. Why your CI can't watch for "blocked for more than" message instead of setting the taint flag? How does your CI decide a reboot is necessary? There is no need to set the tainted flag when some task was just blocked for a while. It might be due to memory pressure, it might be due to setting very short timeout (e.g. a few seconds), it might be due to busy CPUs doing something else... _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
