[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o7fojcwv.fsf@vps.thesusis.net>
Date: Mon, 20 Nov 2023 17:08:32 -0500
From: Phillip Susi <phill@...susis.net>
To: Christian König
<ckoenig.leichtzumerken@...il.com>,
Dave Airlie <airlied@...il.com>,
Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
Luben Tuikov <luben.tuikov@....com>,
"amd-gfx@...ts.freedesktop.org" <amd-gfx@...ts.freedesktop.org>,
Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>
Subject: Re: Radeon regression in 6.6 kernel
Christian König <ckoenig.leichtzumerken@...il.com> writes:
> Well none of the commits mentioned can affect radeon in any way. Radeon
> simply doesn't use the scheduler.
>
> My suspicion is that the user is actually using amdgpu instead of
> radeon. The switch potentially occurred accidentally, for example by
> compiling amdgpu support for SI/CIK.
Indeed, the lspci I originally posted does indicate amdgpu. What is the
difference and should I switch it? If so, how?
> Those amdgpu problems for older ASIC have already been worked on and
> should be fixed by now.
I just pulled v6.7-rc2 and it's still broken. I'll see if I can revert
those 3 patches.
Powered by blists - more mailing lists