From: Mario Limonciello <superm1@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "David Airlie" <airlied@gmail.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
"Daniel Dadap" <ddadap@nvidia.com>
Subject: Re: [PATCH v10 2/4] PCI/VGA: Replace vga_is_firmware_default() with a screen info check
Date: Sun, 12 Oct 2025 14:06:56 -0500 [thread overview]
Message-ID: <65c24236-044c-4b65-baaa-dc0011ea69d8@kernel.org> (raw)
In-Reply-To: <20251012184717.GB3412@sol>
On 10/12/25 1:47 PM, Eric Biggers wrote:
> On Sun, Oct 12, 2025 at 01:37:33PM -0500, Mario Limonciello wrote:
>>
>>
>> On 10/12/25 1:23 PM, Eric Biggers wrote:
>>> Hi,
>>>
>>> On Mon, Aug 11, 2025 at 11:26:04AM -0500, Mario Limonciello (AMD) wrote:
>>>> vga_is_firmware_default() checks firmware resources to find the owner
>>>> framebuffer resources to find the firmware PCI device. This is an
>>>> open coded implementation of screen_info_pci_dev(). Switch to using
>>>> screen_info_pci_dev() instead.
>>>>
>>>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>>>> Suggested-by: Thomas Zimmermann <tzimmermann@suse.de>
>>>> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
>>>
>>> I'm getting a black screen on boot on mainline, and it bisected to this
>>> commit. Reverting this commit fixed it.
>>>
>>> Please revert.
>>>
>>> - Eric
>>
>> Can you please share more information about your issue before we jump
>> straight into a revert? What kind of hardware do you have? Perhaps a
>> kernel log from mainline and another from mainline with the revert could
>> help identify what's going on?
>>
>> A revert might be the right solution, but I would rather fix the issue if
>> it's plausible to do so.
>
> Relevant hardware is:
> AMD Ryzen 9 9950X 16-Core Processor
> Radeon RX 9070
>
> The following message appears in the good log but not the bad log:
>
> fbcon: amdgpudrmfb (fb0) is primary device
>
> I don't have CONFIG_SCREEN_INFO enabled, so the commit changed
> vga_is_firmware_default() to always return false.
Thanks, that definitely explains it.
>
> If DRM_AMDGPU depends on SCREEN_INFO now, it needs to select it.
>
> - Eric
Well the question now is which driver should actually select it.
Although it manifested for you in amdgpu, I don't think this is going to
be an amdgpu unique issue.
Maybe this:
diff --git a/drivers/video/fbdev/core/Kconfig
b/drivers/video/fbdev/core/Kconfig
index 006638eefa41..ce2544924b0e 100644
--- a/drivers/video/fbdev/core/Kconfig
+++ b/drivers/video/fbdev/core/Kconfig
@@ -5,6 +5,7 @@
config FB_CORE
select VIDEO
+ select SCREEN_INFO
tristate
config FB_NOTIFY
next prev parent reply other threads:[~2025-10-12 19:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 16:26 [PATCH v10 0/4] Adjust fbcon console device detection Mario Limonciello (AMD)
2025-08-11 16:26 ` [PATCH v10 1/4] Fix access to video_is_primary_device() when compiled without CONFIG_VIDEO Mario Limonciello (AMD)
2025-08-11 16:26 ` [PATCH v10 2/4] PCI/VGA: Replace vga_is_firmware_default() with a screen info check Mario Limonciello (AMD)
2025-09-10 14:33 ` Thomas Zimmermann
2025-10-12 18:23 ` Eric Biggers
2025-10-12 18:37 ` Mario Limonciello
2025-10-12 18:47 ` Eric Biggers
2025-10-12 19:06 ` Mario Limonciello [this message]
2025-10-13 7:04 ` Thomas Zimmermann
2025-10-13 20:55 ` Bjorn Helgaas
2025-10-28 22:50 ` Bjorn Helgaas
2025-08-11 16:26 ` [PATCH v10 3/4] fbcon: Use screen info to find primary device Mario Limonciello (AMD)
2025-09-04 20:42 ` Bjorn Helgaas
2025-10-28 10:16 ` Aaron Erhardt
2025-10-28 13:15 ` Mario Limonciello
2025-10-28 16:50 ` Thomas Zimmermann
2025-10-28 21:25 ` Mario Limonciello
2025-08-11 16:26 ` [PATCH v10 4/4] DRM: Add a new 'boot_display' attribute Mario Limonciello (AMD)
2025-09-10 14:28 ` Thomas Zimmermann
2025-09-03 4:42 ` [PATCH v10 0/4] Adjust fbcon console device detection Mario Limonciello
2025-09-04 22:36 ` Mario Limonciello
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=65c24236-044c-4b65-baaa-dc0011ea69d8@kernel.org \
--to=superm1@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=ddadap@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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