Bug 199979 - amdgpu: changing pwm1_enable from 1 to 2 does not resume automatic fan control
Summary: amdgpu: changing pwm1_enable from 1 to 2 does not resume automatic fan control
Status: RESOLVED ANSWERED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-08 06:12 UTC by Christian Widmer
Modified: 2023-07-14 21:12 UTC (History)
4 users (show)

See Also:
Kernel Version: 4.17.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Christian Widmer 2018-06-08 06:12:36 UTC
When using the hardware monitoring interface to change pwm1_enable to 2 (automatic) from 1 (manual), the automatic fan control does not work as expected. Instead, the pwm1 value keeps jumping around between at least two values and a continuous, persisting, and unpleasantly high-pitched sound can be heard from inside the computer case. The only way to stop those things is writing some valid value to pwm1, which in turn also switches pwm1_enable back to 1. If the system is booted without ever manually changing the pwm1_enable value, which then defaults to 2, automatic fan control does work as intended.

I am using a custom RX 580 (Sapphire Nitro+ Radeon RX 580 8GD5 Special Edition) on a Gentoo x86_64 system and was able to reproduce the issue with the 4.17.0 kernel with Gentoo patches, the Ubuntu kernel on the 18.04 image (should be a 4.15 one) and also with amd-staging-drm-next.
Comment 1 Christian Birchinger 2020-10-06 13:45:07 UTC
This issue is also present on my system with the same card (Sapphire Radeon RX580 Nitro+ Special Edition) on a recent vanilla kernel (5.8.6).

"pwm1_enable" is 2 after a clean boot. Writing "2" to it again makes the fan speed switch between 2 speeds rapidly causing a high pitched annoying noise.
Comment 2 Artem S. Tashkinov 2023-07-14 21:12:52 UTC
Please report here if that's still an issue in 6.4.3.

https://gitlab.freedesktop.org/drm/amd/-/issues

Note You need to log in before you can comment on or make changes to this bug.