ПроцесСЕР зависается на 797.81 MHz

sudo: cpufreq-set: command not found
sweet@sweetbook:~$ sudo cpufreq-set -g ondemand
sudo: cpufreq-set: command not found
sweet@sweetbook:~$ sudo apt install  cpufreq-set
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package cpufreq-set
sweet@sweetbook:~$ 

sweet@sweetbook:~$ sudo cpufreq-set -g ondemand
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
   for example because of hardware which cannot be set to a specific frequency
   or because the userspace governor isn't loaded?
sweet@sweetbook:~$ 

Cpu speed from cpuinfo 2494.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating via tsc
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2494 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.76 MHz

Socket [0] - [physical cores=2, logical cores=4, max online cores ever=2]
  TURBO ENABLED on 2 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 2593.76 MHz (99.76 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  31x/30x/30x/30x
  Real Current Frequency 2052.61 MHz [99.76 x 20.58] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %   C7 %  Temp      VCore
        Core 1 [0]:       1234.60 (12.38x)      2.61    6.07       1    1.09    90.6    50      0.7855
        Core 2 [2]:       2052.61 (20.58x)      5.21    4.45       1       1    89.3    48      0.7870





C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver modes with cores idling)
C3 = Cores running with PLL turned off and core cache turned off
C6, C7 = Everything in C3 + core state saved to last level cache, C7 is deeper than C6
  Above values in table are in percentage over the last 1 sec

Cpu speed from cpuinfo 2491.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating via tsc
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2494 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.76 MHz

Socket [0] - [physical cores=2, logical cores=4, max online cores ever=2]
  TURBO ENABLED on 2 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 2593.76 MHz (99.76 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  31x/30x/30x/30x
  Real Current Frequency 798.13 MHz [99.76 x 8.00] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %   C7 %  Temp      VCore
        Core 1 [0]:       798.08 (8.00x)        8.18     9.7    1.28    1.61    84.8    42      0.6794
        Core 2 [2]:       798.13 (8.00x)          10      16       1       1    78.8    40      0.6818





C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver modes with cores idling)
C3 = Cores running with PLL turned off and core cache turned off
C6, C7 = Everything in C3 + core state saved to last level cache, C7 is deeper than C6
  Above values in table are in percentage over the last 1 sec

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 1.24 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 706 MHz.
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 1.24 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 686 MHz.
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 1.24 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 708 MHz.
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 1.24 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 690 MHz.

sweet@sweetbook:~$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: LENOVO 20238 [Lenovo G510] (laptop)
# Board: LENOVO INVALID
# Kernel: 4.2.0-34-generic x86_64
# Processor: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz (6/60/3)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Lynx Point (PCH)
Module i2c-i801 loaded successfully.

Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: DPDDC-A (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x4a
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Client found at address 0x4b
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `Analog Devices ADT7481'...                     No

Next adapter: Radeon i2c bit bus 0x90 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x91 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x92 (i2c-9)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x93 (i2c-10)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x94 (i2c-11)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x95 (i2c-12)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x96 (i2c-13)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x97 (i2c-14)
Do you want to scan it? (yes/NO/selectively): y


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading i2c-i801... OK
Unloading cpuid... OK

sweet@sweetbook:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +52.0°C  (crit = +127.0°C)

radeon-pci-0100
Adapter: PCI adapter
temp1:            N/A  (crit = +120.0°C, hyst = +90.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +52.0°C  (high = +84.0°C, crit = +100.0°C)
Core 0:         +48.0°C  (high = +84.0°C, crit = +100.0°C)
Core 1:         +44.0°C  (high = +84.0°C, crit = +100.0°C)

sweet@sweetbook:~$ cpupower frequency-info
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 1.24 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 702 MHz.
  boost state support:
    Supported: yes
    Active: yes

hardware limits: 800 MHz - 3.10 GHz

current policy: frequency should be within 800 MHz and 1.24 GHz.

sweet@sweetbook:~$ cpupower frequency-info
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 800 MHz and 1.50 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 1.50 GHz.
  cpufreq stats: 2.50 GHz:1,15%, 2.50 GHz:0,00%, 2.40 GHz:0,06%, 2.30 GHz:0,09%, 2.10 GHz:0,09%, 2.00 GHz:0,24%, 1.90 GHz:0,08%, 1.80 GHz:0,15%, 1.60 GHz:0,18%, 1.50 GHz:82,61%, 1.40 GHz:1,18%, 1.30 GHz:1,26%, 1.20 GHz:2,12%, 1000 MHz:2,74%, 900 MHz:3,14%, 800 MHz:4,90%  (100250)
  boost state support:
    Supported: yes
    Active: yes

sweet@sweetbook:~$ sudo cpupower frequency-set -d 1000000
Setting cpu: 0
Setting cpu: 1
Setting cpu: 2
Setting cpu: 3
sweet@sweetbook:~$ sudo cpupower frequency-set -d 1100000
Setting cpu: 0
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
   for example because of hardware which cannot be set to a specific frequency
   or because the userspace governor isn't loaded?
sweet@sweetbook:~$ 

  current policy: frequency should be within 1000 MHz and 1.00 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz.

sweet@sweetbook:~$ sysbench --test=cpu --cpu-max-prime=2000000 run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1

Doing CPU performance benchmark

Threads started!

Cpu speed from cpuinfo 2493.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2494 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.76 MHz

Socket [0] - [physical cores=2, logical cores=4, max online cores ever=2]
  TURBO ENABLED on 2 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 2593.76 MHz (99.76 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  31x/30x/30x/30x
  Real Current Frequency 3076.36 MHz [99.76 x 30.84] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %
        Core 1 [0]:       2992.82 (30.00x)      10.9    11.1    3.36     1.2
        Core 2 [2]:       3076.36 (30.84x)      99.6       0       0       0

  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 800 MHz and 2.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz.
  cpufreq stats: 2.50 GHz:41,28%, 2.50 GHz:0,00%, 2.40 GHz:0,45%, 2.30 GHz:0,85%, 2.10 GHz:0,72%, 2.00 GHz:0,52%, 1.90 GHz:0,56%, 1.80 GHz:1,19%, 1.60 GHz:0,93%, 1.50 GHz:1,13%, 1.40 GHz:0,51%, 1.30 GHz:1,52%, 1.20 GHz:1,77%, 1000 MHz:3,52%, 900 MHz:10,96%, 800 MHz:34,07%  (1235)