Package: intel-microcode
Version: 3.20191115.1
Severity: important

Hi.

With the most recent upgrade, the CPU seems to run at considerably
higher temperatures.


Shortly after a fresh boot, but long enough so that everything has
started up, and the system being basically idle it looks like this:

microcode updated early to revision 0xca, date = 2019-09-26

iwlwifi-virtual-0
Adapter: Virtual device
temp1:            N/A  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +58.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +57.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +57.0°C  (high = +100.0°C, crit = +100.0°C)

CMB1-acpi-0
Adapter: ACPI interface
in0:          16.60 V  
curr1:         0.00 A  




And with the same kernel but older microcode:

microcode updated early to revision 0xc6, date = 2019-08-14

iwlwifi-virtual-0
Adapter: Virtual device
temp1:            N/A  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +55.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +53.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +54.0°C  (high = +100.0°C, crit = +100.0°C)

CMB1-acpi-0
Adapter: ACPI interface
in0:          16.60 V  
curr1:         0.00 A  



top shows basically no CPU utilisation (in both cases) but the fan
goes up and the CPU is constantly notacibly hot, which both wasn't
the case previously when the system was idle.




Now another strange thing:
With the NEW microcode, once some load was put on the system, even when
this is gone and the CPU back to basically no utilisation, the temperatures
are at a *much* higher level and stay there, for whichever reason:

iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +34.0°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +76.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +69.0°C  (high = +100.0°C, crit = +100.0°C)

CMB1-acpi-0
Adapter: ACPI interface
in0:          16.59 V  
curr1:         0.00 A  



Is this a problem with the microcode or a kinda expected side-effect
of the security workarounds?



Cheers,
Chris.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages intel-microcode depends on:
ii  iucode-tool  2.3.1-1

Versions of packages intel-microcode recommends:
ii  initramfs-tools  0.135

intel-microcode suggests no packages.

-- no debconf information

Reply via email to