From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: "Nirujogi, Pratap" <pnirujog@amd.com>, rafael@kernel.org
Cc: W_Armin@gmx.de, lenb@kernel.org, Bin Du <bin.du@amd.com>,
benjamin.chan@amd.com, king.li@amd.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] AMDISP failure with kernel v7.0-rc2 due to Commit: 02c057ddefef5
Date: Thu, 5 Mar 2026 18:35:28 -0600 [thread overview]
Message-ID: <23e8f0df-3eec-46e8-b5f1-5f417460e272@kernel.org> (raw)
In-Reply-To: <007e3390-6b2b-457e-83c7-c794c5952018@amd.com>
On 3/5/2026 5:11 PM, Nirujogi, Pratap wrote:
> Hi Rafael,
>
> In kernel version 7.0-rc2, the AMDISP device reports the following
> errors when created via mfd_add_hotplug_devices.
>
> [ 5.236645] ACPI: video: Video Device [GFX0] (multi-head: yes rom:
> no post: no)
> [ 5.236744] input: Video Bus as /devices/
> pci0000:00/0000:00:08.1/0000:c3:00.0/amd_isp_capture.1.auto/input/input21
> [ 5.236779] acpi device:14: Error installing notify handler
> [ 5.236782] acpi device:15: Error installing notify handler
> [ 5.236783] acpi device:16: Error installing notify handler
> [ 5.236784] acpi device:17: Error installing notify handler
> [ 5.236785] acpi device:18: Error installing notify handler
> [ 5.236786] acpi device:19: Error installing notify handler
> [ 5.236786] acpi device:1a: Error installing notify handler
> [ 5.236787] acpi device:1b: Error installing notify handler
> [ 5.236788] acpi device:1c: Error installing notify handler
>
> These failures indicate AMDISP device is incorrectly detected as ACPI
> Video device while it is not.
>
> The seems like a regression caused by the change that converts the ACPI
> video device to a platform device (commit: 02c057ddefef5).
>
> Issue is not observed in 6.19-rc6, and also when this change is reverted
> in 7.0-rc2.
>
> I really appreciate your inputs on addressing this issue and helping us
> make progress on 7.0 rc2.
>
> Steps followed to reproduce the issue:
>
> 1. Apply AMDISP v9 patch series [1] on top of kernel v7.0-rc2
> 2. Add NULL check for “dev->type” in isp_genpd_add_device() [2] (to
> avoid kernel panic found in v7.0-rc2)
> 3. Build kernel with:
> - CONFIG_AMD_ISP_PLATFORM=y
> - CONFIG_VIDEO_AMD_ISP4_CAPTURE=m
> 4. Install kernel on AMDISP supported system (HP ZBook Ultra G1a)
> 5. Boot system to see the failures
>
> [1] https://lore.kernel.org/all/20260302073020.148277-1-Bin.Du@amd.com/
> [2] https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/
> amdgpu/isp_v4_1_1.c#L132
>
> Thanks,
> Pratap
>
>
>
It's a bit weird to see it even probe in this path in the first place.
acpi_video_bus_probe() getting called with the mfd device doesn't seem
right to me.
I wonder if it's because ISP is an MFD device of GPU (and thus LNXVIDEO
ends up matching).
Would a sensible solution be to reject mfd device types in
acpi_video_bus_probe()?
>
next prev parent reply other threads:[~2026-03-06 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 23:11 [REGRESSION] AMDISP failure with kernel v7.0-rc2 due to Commit: 02c057ddefef5 Nirujogi, Pratap
2026-03-06 0:35 ` Mario Limonciello (AMD) (kernel.org) [this message]
2026-03-06 12:01 ` Rafael J. Wysocki
2026-03-06 12:45 ` Mario Limonciello
2026-03-06 13:28 ` Rafael J. Wysocki
2026-03-09 3:52 ` Nirujogi, Pratap
2026-03-09 8:11 ` Du, Bin
2026-03-09 11:58 ` Rafael J. Wysocki
2026-03-09 12:23 ` Rafael J. Wysocki
2026-03-09 16:01 ` [PATCH v1] ACPI: video: Switch over to auxiliary bus type Rafael J. Wysocki
2026-03-09 20:24 ` Nirujogi, Pratap
2026-03-09 20:35 ` Rafael J. Wysocki
2026-03-06 12:10 ` [REGRESSION] AMDISP failure with kernel v7.0-rc2 due to Commit: 02c057ddefef5 Rafael J. Wysocki
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=23e8f0df-3eec-46e8-b5f1-5f417460e272@kernel.org \
--to=superm1@kernel.org \
--cc=W_Armin@gmx.de \
--cc=benjamin.chan@amd.com \
--cc=bin.du@amd.com \
--cc=king.li@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pnirujog@amd.com \
--cc=rafael@kernel.org \
--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