On Thu, 24 Feb 2022 17:34:54 +0100,
Kai Vehmanen wrote:
>
> Hi,
>
> On Thu, 24 Feb 2022, Ramalingam C wrote:
>
> > Split the wait for component binding from i915 in multiples of
> > sysctl_hung_task_timeout_secs. This helps to avoid the possible kworker
> > thread hung detection given below.
>
On Thu, Feb 24, 2022 at 01:22:03AM +0530, Ramalingam C wrote:
Split the wait for component binding from i915 in multiples of
sysctl_hung_task_timeout_secs. This helps to avoid the possible kworker
thread hung detection given below.
<3>[ 60.946316] INFO: task kworker/11:1:104 blocked for more
Hi,
On Thu, 24 Feb 2022, Ramalingam C wrote:
> Split the wait for component binding from i915 in multiples of
> sysctl_hung_task_timeout_secs. This helps to avoid the possible kworker
> thread hung detection given below.
while I understand the problem, I'm not sure whether a simpler option
Split the wait for component binding from i915 in multiples of
sysctl_hung_task_timeout_secs. This helps to avoid the possible kworker
thread hung detection given below.
<3>[ 60.946316] INFO: task kworker/11:1:104 blocked for more than 30
seconds.
<3>[ 60.946479] Tainted: GW
