From: Phillip Susi <phill@thesusis.net>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Dave Airlie" <airlied@gmail.com>,
"Linux regressions mailing list" <regressions@lists.linux.dev>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Luben Tuikov" <luben.tuikov@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: Radeon regression in 6.6 kernel
Date: Mon, 20 Nov 2023 17:08:32 -0500 [thread overview]
Message-ID: <87o7fojcwv.fsf@vps.thesusis.net> (raw)
In-Reply-To: <bdb238b6-60c7-4f26-81d0-9e62cd5dd326@gmail.com>
Christian König <ckoenig.leichtzumerken@gmail.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.
prev parent reply other threads:[~2023-11-20 22:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 0:46 Radeon regression in 6.6 kernel Phillip Susi
2023-11-12 11:12 ` Bagas Sanjaya
2023-11-12 18:42 ` Phillip Susi
2023-11-19 6:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 6:47 ` Dave Airlie
2023-11-19 13:24 ` Bagas Sanjaya
2023-11-19 13:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 13:53 ` Bagas Sanjaya
2023-11-20 15:57 ` Christian König
2023-11-20 16:08 ` Alex Deucher
2023-11-20 16:24 ` Christian König
2023-11-20 17:31 ` Alex Deucher
2023-11-20 22:40 ` Phillip Susi
2023-11-21 14:05 ` Alex Deucher
2023-11-21 22:05 ` Phillip Susi
2023-11-23 1:34 ` Luben Tuikov
2023-11-27 23:24 ` Phillip Susi
2023-11-28 22:13 ` Alex Deucher
2023-11-29 4:44 ` Luben Tuikov
2023-11-29 13:50 ` Alex Deucher
2023-11-29 15:22 ` Alex Deucher
2023-11-29 16:41 ` Luben Tuikov
2023-11-29 18:52 ` Alex Deucher
2023-11-29 20:10 ` Alex Deucher
2023-11-29 20:49 ` Alex Deucher
2023-11-30 3:36 ` Luben Tuikov
2023-11-30 3:47 ` Luben Tuikov
2023-11-30 23:28 ` Alex Deucher
2023-11-30 21:29 ` Alex Deucher
2023-12-01 16:55 ` Alex Deucher
2023-12-03 20:40 ` Phillip Susi
2023-12-04 14:14 ` Alex Deucher
2023-12-11 23:50 ` Phillip Susi
2023-12-12 0:28 ` Phillip Susi
2023-12-12 14:55 ` Alex Deucher
2023-11-29 16:20 ` Luben Tuikov
2023-11-29 18:45 ` Alex Deucher
2023-11-29 20:24 ` Phillip Susi
2023-11-20 22:08 ` Phillip Susi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7fojcwv.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox