[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac41c761-27c9-48c3-bd80-d94d4db291e8@leemhuis.info>
Date: Tue, 7 May 2024 07:04:14 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: David Wang <00107082@....com>
Cc: airlied@...il.com, airlied@...hat.com, daniel@...ll.ch,
dreaming.about.electric.sheep@...il.com, dri-devel@...ts.freedesktop.org,
kraxel@...hat.com, linux-kernel@...r.kernel.org,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
regressions@...ts.linux.dev, spice-devel@...ts.freedesktop.org,
tzimmermann@...e.de, virtualization@...ts.linux.dev
Subject: Re: [Regression] 6.9.0: WARNING: workqueue: WQ_MEM_RECLAIM
ttm:ttm_bo_delayed_delete [ttm] is flushing !WQ_MEM_RECLAIM
events:qxl_gc_work [qxl]
On 06.05.24 16:30, David Wang wrote:
>> On 30.04.24 08:13, David Wang wrote:
>> And confirmed that the warning is caused by
>> 07ed11afb68d94eadd4ffc082b97c2331307c5ea and reverting it can fix.
>
> The kernel warning still shows up in 6.9.0-rc7.
> (I think 4 high load processes on a 2-Core VM could easily trigger the kernel warning.)
Thx for the report. Linus just reverted the commit 07ed11afb68 you
mentioned in your initial mail (I put that quote in again, see above):
3628e0383dd349 ("Reapply "drm/qxl: simplify qxl_fence_wait"")
https://git.kernel.org/torvalds/c/3628e0383dd349f02f882e612ab6184e4bb3dc10
So this hopefully should be history now.
Ciao, Thorsten
Powered by blists - more mailing lists