From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Mark Somerville <mark@qpok.net>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev,
"Alex Deucher" <alexander.deucher@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Christian König" <christian.koenig@amd.com>,
"Xinhui Pan" <Xinhui.Pan@amd.com>
Subject: Re: [REGRESSION] Unable to pass AMD RX 6400 GPU via VFIO
Date: Fri, 20 Mar 2026 08:51:45 -0500 [thread overview]
Message-ID: <87878ae4-dd03-41fb-83bd-eb89809e8e37@kernel.org> (raw)
In-Reply-To: <dab036c7ad0ce6c28fa25b8c30e68cc20ed2a8da@qpok.net>
On 3/20/2026 8:33 AM, Mark Somerville wrote:
> [You don't often get email from mark@qpok.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> March 20, 2026 at 11:42 AM, "Mario Limonciello" <superm1@kernel.org mailto:superm1@kernel.org?to=%22Mario%20Limonciello%22%20%3Csuperm1%40kernel.org%3E > wrote:
>>
>> If you bisected to 8140ac7c55e75093a01c6110a2c4025fe7177c57, try adding f7afda7fcd169a9168695247d07ad94cf7b9798f.
>
> Ah, nice one! Just tried that and can confirm that 8140ac7c + f7afda7f resolves this problem for me.
>
> Also great that it's already in a later release than I have been able to test!
>
> Thanks a lot for the fast resolution and apologies for any noise.
That's great!
Not noise at all, you found a problem and we have a solution that should
be added so others don't hit it.
I think Sasha and Greg just need to pick it up then.
prev parent reply other threads:[~2026-03-20 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 9:28 [REGRESSION] Unable to pass AMD RX 6400 GPU via VFIO Mark Somerville
2026-03-20 11:42 ` Thorsten Leemhuis
2026-03-20 12:34 ` Greg Kroah-Hartman
2026-03-20 11:42 ` Mario Limonciello
2026-03-20 13:33 ` Mark Somerville
2026-03-20 13:51 ` Mario Limonciello (AMD) (kernel.org) [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=87878ae4-dd03-41fb-83bd-eb89809e8e37@kernel.org \
--to=superm1@kernel.org \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=mark@qpok.net \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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