AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to be 1030MHz

[Yassine]

Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

   max_sclk = 75000;

instead of

   max_sclk = 103000;

Why is that? I changed it and rebuilt the kernel, and I can say that there are absolutely no issues when using the 1030MHz clock, which is what it is supposed to be.

Linux Version: 4.13.0-36-generic

---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yassine 3068 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
InstallationDate: Installed on 2016-12-19 (439 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp.
 Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 25a7:0701
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Notebook
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic N/A
 linux-firmware 1.169.3
Tags: artful wayland-session
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 11/24/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.1D
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8136
dmi.board.vendor: HP
dmi.board.version: 31.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1752829

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Yassine (yassine10suno)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4

[Kai-Heng Feng (kaihengfeng)]

I can see that your chip matches this condition:
"rdev->pdev->revision == 0x83"

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/radeon

[Yassine (yassine10suno)]

Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

                          max_sclk = 75000;

  instead of

                          max_sclk = 103000;

Why is that? I changed it and rebuilt the kernel, and I can say that
there are absolutely no issues when using the 1030MHz clock, **which is the default frequency this GPU is designed for**.

[Yassine (yassine10suno)]

Created attachment 142420
root/drivers/gpu/drm/radeon/si_dpm.c with 1 line modified

blob: 8fb60b3af015804d6d5ee3ef5d6f24ba74e2b1d9
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/radeon/si_dpm.c

Line 2985 modified from:
   max_sclk = 75000;
to:
   max_sclk = 103000;

[Alexdeucher (alexdeucher)]

A number of boards had stability issues at the default clocks. Please attach your dmesg output.

[Yassine (yassine10suno)]

Created attachment 142424
dmesg output

[Yassine (yassine10suno)]

Comment on attachment 142424
dmesg output

Note: I have not modified the kernel dmesg was ran under. Core clock is still 750MHz.

[Yassine (yassine10suno)]

Why is the core clock for this GPU (HAINAN) and what seems to have codename OLAND hard-coded anyway? The other GPUs do not have their clocks hard-coded, which allows them to be modified without modifying and rebuilding the module.

[Martin-peres-n (martin-peres-n)]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/846.