The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: WangYuli <wangyuli@uniontech.com>,
	alexander.deucher@amd.com, christian.koenig@amd.com,
	Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch,
	lijo.lazar@amd.com, le.ma@amd.com, Jun.Ma2@amd.com,
	hamza.mahfooz@amd.com, andrealmeid@igalia.com,
	wenlunpeng@uniontech.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, guanwentao@uniontech.com,
	zhanjun@uniontech.com
Subject: Re: [PATCH] amdgpu: disable amdgpu_dpm on THTF-SW831-1W-DS25_MB board
Date: Wed, 28 Aug 2024 10:19:48 -0500	[thread overview]
Message-ID: <e3122e5c-a6dd-4228-84ab-04747a3df265@amd.com> (raw)
In-Reply-To: <3EA7C2B9E8C4D00A+20240828105938.37674-1-wangyuli@uniontech.com>

On 8/28/2024 05:59, WangYuli wrote:
> From: wenlunpeng <wenlunpeng@uniontech.com>
> 
> The quirk is for reboot-stability.
> 
> A device reboot stress test has been observed to cause
> random system hangs when amdgpu_dpm is enabled.
> 
> Disabling amdgpu_dpm can fix this.
> 
> However, a boot-param can still overwrite it to enable
> amdgpu_dpm.
> 
> Serial log when error occurs:
> ...
> Console: switching to colour frame buffer device 160x45
> amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
> [drm:amdgpu_device_ip_late_init] *ERROR* late_init of IP block <si_dpm> failed -22
> amdgpu 0000:01:00.0: amdgpu_device_ip_late_init failed
> amdgpu 0000:01:00.0: Fatal error during GPU init
> [drm] amdgpu: finishing device.
> Console: switching to colour dummy device 80x25
> ...

This is production hardware?

Have you already checked whether a BIOS upgrade for the device could 
help this issue?

> 
> Signed-off-by: wenlunpeng <wenlunpeng@uniontech.com>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>

Just to clarify did you guys co-work on this patch, or are you 
submitting on behalf of wenlunpeng?  It right now shows up as you 
submitting on behalf of wenlunpeng.  If you co-worked on it you should 
also use a Co-Developed-by tag.

> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 23 +++++++++++++++++++++++
>   1 file changed, 23 insertions(+)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> index 094498a0964b..81716fcac7cd 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> @@ -32,6 +32,7 @@
>   #include <drm/drm_vblank.h>
>   
>   #include <linux/cc_platform.h>
> +#include <linux/dmi.h>
>   #include <linux/dynamic_debug.h>
>   #include <linux/module.h>
>   #include <linux/mmu_notifier.h>
> @@ -3023,10 +3024,32 @@ static struct pci_driver amdgpu_kms_pci_driver = {
>   	.dev_groups = amdgpu_sysfs_groups,
>   };
>   
> +static int quirk_set_amdgpu_dpm_0(const struct dmi_system_id *dmi)
> +{
> +	amdgpu_dpm = 0;
> +	pr_info("Identified '%s', set amdgpu_dpm to 0.\n", dmi->ident);
> +	return 1;
> +}
> +
> +static const struct dmi_system_id amdgpu_quirklist[] = {
> +	{
> +		.ident = "DS25 Desktop",
> +		.matches = {
> +			DMI_MATCH(DMI_BOARD_NAME, "THTF-SW831-1W-DS25_MB"),

As this is suspected to be a BIOS issue, I would like to better 
understand if the BIOS upgrade fixes it.  If it does but you would still 
like a quirk for the system it should include the BIOS version here.

> +		},
> +		.callback = quirk_set_amdgpu_dpm_0,
> +	},
> +	{}
> +};
> +
>   static int __init amdgpu_init(void)
>   {
>   	int r;
>   
> +	/* quirks for some hardware, applied only when it's untouched */
> +	if (amdgpu_dpm == -1)
> +		dmi_check_system(amdgpu_quirklist);
> +
>   	if (drm_firmware_drivers_only())
>   		return -EINVAL;
>   


  reply	other threads:[~2024-08-28 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 10:59 [PATCH] amdgpu: disable amdgpu_dpm on THTF-SW831-1W-DS25_MB board WangYuli
2024-08-28 15:19 ` Mario Limonciello [this message]
2024-08-28 15:37   ` WangYuli
2024-08-28 15:30 ` Alex Deucher
2024-08-28 15:47   ` WangYuli
2024-08-28 16:14     ` Alex Deucher
2024-08-28 21:31       ` 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=e3122e5c-a6dd-4228-84ab-04747a3df265@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Jun.Ma2@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrealmeid@igalia.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guanwentao@uniontech.com \
    --cc=hamza.mahfooz@amd.com \
    --cc=le.ma@amd.com \
    --cc=lijo.lazar@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangyuli@uniontech.com \
    --cc=wenlunpeng@uniontech.com \
    --cc=zhanjun@uniontech.com \
    /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