acpitz-acpi-0 wrong temperature

Bug #1922111 reported by Juno Computers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-0000.

The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue.

Ubuntu 20.04
Kernel 5.8.0-49-generic
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: juno 1510 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-12-09 (111 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201)
MachineType: Notebook NV4XMB,ME,MZ
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-49-generic N/A
 linux-backports-modules-5.8.0-49-generic N/A
 linux-firmware 1.187.10
Tags: focal
Uname: Linux 5.8.0-49-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 11/03/2020
dmi.bios.release: 7.6
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.06
dmi.board.asset.tag: Tag 12345
dmi.board.name: NV4XMB,ME,MZ
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.2
dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: NV4XMB,ME,MZ
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004

description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1922111

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Juno Computers (junocomp) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
Juno Computers (junocomp) wrote : CRDA.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : IwConfig.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : Lspci.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : Lspci-vt.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : Lsusb.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : Lsusb-t.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : Lsusb-v.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : ProcEnviron.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : ProcModules.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : PulseList.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : RfKill.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : UdevDb.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : WifiSyslog.txt

apport information

Revision history for this message
Juno Computers (junocomp) wrote : acpidump.txt

apport information

description: updated
Revision history for this message
Alex Hung (alexhung) wrote :

Data from acpitz (acpi thermalzone) are from BIOS. The peak values you are seeing can be the results of BIOS/EC sampling mechanism, i.e. instantaneous values instead of average values.

The must be fixed in BIOS/EC firmware not in OS; however, you can disable acpitz by kernel parameter "thermal.off=1" (see how @ https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter) if your system has another reliable temperature sensor.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.