I have MSI GE702PC with gtx 850m nvidia graphic card with ,linux mint 17.3 18.1 18.2, nvidia-384.69(tried almost all releases that is lower than this). Everything works fine until waking up from suspend. Normally gpu clock is set to be max via /etc/X11/xorg.conf with
Option “RegistryDwords” “PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefaultAC=0x1”.
But after waking up from suspend the clock is fixed to 33Mhz(fps drops from around 3800 to around 78) and i cant change it. My kernel version is 10 (lower versions causes flickering.) and i tried with 4.4… 4.8… nothing changed.
When i went deeper i saw that, this is a throttling problem. Before suspending my system everything works great and my throttle parameters are:
Clocks Throttle Reasons
Idle : Not Active
Applications Clocks Setting : Not Active
SW Power Cap : Not Active
HW Slowdown : Not Active
Sync Boost : Not Active
Unknown : Not Active
But after suspend it becomes:
Clocks Throttle Reasons
Idle : Active
Applications Clocks Setting : Not Active
SW Power Cap : Not Active
HW Slowdown : Active
Sync Boost : Not Active
Unknown : Not Active
I know there is no problem with my hardware, i switched my operating system from windows to linux like 3 years ago and this problem started with this OS movement.
I don’t think someone will offer officially to play with nvidia bios. But i’m brave and open to all suggestions.
UPDATE
*This problem occurs also when i unplug the power cable. When i switch from AC to battery it also suddenly goes to 33Mhz and same throttle issue. And stays there even after re-plugging the AC cable.
*Its all okay with open source driver and intel graphics card. But i don’t get smooth experience with open source driver, that is why im insist on nvidia driver.
Clocks Throttle Reasons
Idle : Not Active
Applications Clocks Setting : Not Active
SW Power Cap : Active
HW Slowdown : Active
Sync Boost : Not Active
SW Thermal Slowdown : Not Active
Its interesting :). now we have same problem after suspend. But when i unplug the cable and plug again it seems better but not the optimal. unplugged frequency 215Mhz plugged 238Mhz. The bug file is attached.
Now we have only HW Slowdown throttle active…
I really wonder how did you decide to add this option when you see the bug. Is there a list or experience?.. nvidia-bug-report.log.gz (147 KB)
Obviously, this problem goes a bit deeper.
Now, this might be a bit dangerous, so be sure to know how to boot to safe mode and revert:
In the folder
/etc/modprobe.d
look for the nvidia.conf (or the like) , edit it, find the line
No need to enter those DeviceFile options, those settings are to set the access rights to the device files in /dev. I think Mint/Ubuntu uses udev rules to accomplish that. It differs between distributions.
In your case, the line
options nvidia_384 NVreg_RegisterForACPIEvents=0
at the end of nvidia-graphics-drivers.conf would suffice.
The same attitude after power switching. Adding the bug report.
What we got so far is that:
*We could fix one throttle problem after power switching. Now we have only one throttle activated (Max 238 Mhz).
*But we have same problem (33 Mhz and 2 throttle activated) after waking up from suspend.
/etc/modprobe.d $ cat nvidia-graphics-drivers.conf
# This file was installed by nvidia-384
# Do not edit this file manually
blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-current
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-384-updates
alias nvidia nvidia_384
alias nvidia-uvm nvidia_384_uvm
alias nvidia-modeset nvidia_384_modeset
alias nvidia-drm nvidia_384_drm
alias nouveau off
alias lbm-nouveau off
options nvidia_384_drm modeset=0
options nvidia_384 NVreg_RegisterForACPIEvents=0
I’m noticing something similar for my Dell Precision M3520 w/Quadro M620. pclk is getting stuck at 254 MHz after switching to battery or after sleep/wakeup.
Coud you attach the output of
sudo lspci -vvv
before and after pulling the plug?
You could also try kernel 4.17, it has some acpi fixes that might be relevant.