lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23CC94B2018EE36C+e1d82597-6adf-4bcf-8e63-df788eb81bd0@uniontech.com>
Date: Wed, 28 Aug 2024 23:37:57 +0800
From: WangYuli <wangyuli@...ontech.com>
To: Mario Limonciello <mario.limonciello@....com>, alexander.deucher@....com,
 christian.koenig@....com, Xinhui.Pan@....com, airlied@...il.com,
 daniel@...ll.ch, lijo.lazar@....com, le.ma@....com, Jun.Ma2@....com,
 hamza.mahfooz@....com, andrealmeid@...lia.com, wenlunpeng@...ontech.com
Cc: amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org, guanwentao@...ontech.com, zhanjun@...ontech.com
Subject: Re: [PATCH] amdgpu: disable amdgpu_dpm on THTF-SW831-1W-DS25_MB board


On 2024/8/28 23:19, Mario Limonciello wrote:
> This is production hardware?

Unfortunately, this device was released quite a while back.
>
> Have you already checked whether a BIOS upgrade for the device could 
> help this issue?


Sadly, there's no BIOS update to address this problem. It seems to be a 
persistent issue across all BIOS versions for this motherboard.

>
> 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.


No, the entirety of this bugfix is attributable to wenlunpeng.

>
> 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.
>
>
Unfortunately again. There's not much we as kernel developers can do 
when devices behave unpredictably.

-- 

*WangYuli
*



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ