[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a73f04c3-a423-48a6-87b2-3c5d809c6833@oracle.com>
Date: Fri, 19 Apr 2024 20:12:46 +0530
From: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
To: Takashi Iwai <tiwai@...e.de>, patrik.r.jakobsson@...il.com
Cc: Helge Deller <deller@....de>, Nam Cao <namcao@...utronix.de>,
Thomas Zimmermann <tzimmermann@...e.de>,
Daniel Vetter <daniel@...ll.ch>, linux-fbdev@...r.kernel.org,
dri-devel@...ts.freedesktop.org, bigeasy@...utronix.de,
LKML <linux-kernel@...r.kernel.org>,
Vegard Nossum <vegard.nossum@...cle.com>,
George Kennedy <george.kennedy@...cle.com>,
Darren Kenny <darren.kenny@...cle.com>, chuansheng.liu@...el.com
Subject: Re: [bug-report] task info hung problem in fb_deferred_io_work()
Hi Takashi,
On 19/04/24 13:15, Takashi Iwai wrote:
> On Fri, 19 Apr 2024 09:39:09 +0200,
>>> Then later on, the commit 33cd6ea9c067 changed cancel_*() to
>>> flush_delayed_work() blindly, and the known problem resurfaced again.
>>>
>>
>> I have reverted that commit, but still could see some other task hung
>> message as shared here on other reply:
>>
>> https://lore.kernel.org/all/d2485cb9-277d-4b8e-9794-02f1efababc9@oracle.com/
>
> Yes, then it could be a different cause, I suppose.
> The crash with flush_delayed_work() was a real crash, no hanging task,
> IIRC.
>
> Can you reproduce the issue with the latest Linus upstream, too?
>
Yes, this was reproduced on 6.9-rc4 kernel[1], also reverting that
commit 33cd6ea9c067 on upstream still showed another issue[2].
[1]https://lore.kernel.org/all/271372d6-e665-4e7f-b088-dee5f4ab341a@oracle.com/
[2]
https://lore.kernel.org/all/d2485cb9-277d-4b8e-9794-02f1efababc9@oracle.com/
Thanks,
Harshit
>
> thanks,
>
> Takashi
Powered by blists - more mailing lists