Ubuntu
thermald package

thermald flooding journalctl on unsupported cpu system

Bug #1543109 reported by dino99
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
thermald (Ubuntu)
Fix Released
Medium
Colin Ian King

Bug Description

This is a variant of bug #1543046; so reporting it separately

Looks like thermald does not check for valid cpu model to avoid that spamming: mine is an old intel q9550, and journalctl has logged:

***********
thermald[791]: NO RAPL sysfs present
 10 CPUID levels; family:model:stepping 0x6:17:7 (6:23:7)
 Need Linux PowerCap sysfs
 failed to open /dev/acpi_thermal_rel
 failed to open /dev/acpi_thermal_rel
 TRT/ART read failed
...
...
Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check
THD engine start failed
*************
So thermal-conf.xml might be completed to blacklist some incompatible hardware i suppose.

As the spamming lines were hundreds, i've stopped it with:
 sudo systemctl disable thermald

but this is not enough as shown by the lines above.
---
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
NonfreeKernelModules: nvidia_uvm nvidia
Package: thermald 1.4.3-6
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Tags: xenial
Uname: Linux 4.4.0-4-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
upstart.thermald.override: manual

See original description
Revision history for this message
dino99 (9d9) wrote : Dependencies.txt

apport information

tags: added: bot-stop-nagging xenial
tags: added: apport-collected
description: updated
Revision history for this message
dino99 (9d9) wrote : JournalErrors.txt

apport information

Revision history for this message
dino99 (9d9) wrote : ProcEnviron.txt

apport information

description: updated
dino99 (9d9)
summary: - [xenial] thermald flooding journalctl on unsupported cpu system
+ thermald flooding journalctl on unsupported cpu system
Colin Ian King (colin-king)
Changed in thermald (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Colin Ian King (colin-king) wrote :

Do you mind providing a more complete log containing more of the spamming messages.

Since you have manually stopped thermald, perhaps you could run it from the command line and capture the output so I get more of an idea of what's happening. Use:

sudo thermald --no-daemon | teee thermald.log

and let that run for ~10 minutes. Then attach it to the bug report. Thanks

Revision history for this message
dino99 (9d9) wrote :

here is the requested log thermal.log

note: i've looked to your github changes, and it seems to me they should also resolved that issue. So maybe there is nothing to tweak when unsupported cpu are used.

note2: as the previous thermald spam message had not be saved, i've re-enabled thermald, then rebooted to copy/paste it here, but surprisingly there is nothing logged that time.

systemctl status thermald.service
● thermald.service - Thermal Daemon Service
   Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-02-08 21:29:15 CET; 19min ago
  Process: 696 ExecStart=/usr/sbin/thermald --no-daemon --dbus-enable (code=exited, status=1/FAILURE)
 Main PID: 696 (code=exited, status=1/FAILURE)

Feb 08 21:29:15 u64 thermald[696]: Path:
Feb 08 21:29:15 u64 thermald[696]: Min: 0
Feb 08 21:29:15 u64 thermald[696]: Max: 50
Feb 08 21:29:15 u64 thermald[696]: Step: 10
Feb 08 21:29:15 u64 thermald[696]: AutoDownControl: 0
Feb 08 21:29:15 u64 thermald[696]: PID: Kp 0.001000
Feb 08 21:29:15 u64 thermald[696]: PID: Ki 0.000100
Feb 08 21:29:15 u64 thermald[696]: PID: Kd 0.000100
Feb 08 21:29:15 u64 thermald[696]: Unsupported cpu model, use thermal-conf....ck
Feb 08 21:29:15 u64 thermald[696]: THD engine start failed
Hint: Some lines were ellipsized, use -l to show in full.

Revision history for this message
Colin Ian King (colin-king) wrote :

Hrmmm, this does seem quite now. I'm not able to reproduce the spamming on some equivalent hardware, so perhaps this is now fixed.

If you agree, I'll mark this as fixed.

Revision history for this message
dino99 (9d9) wrote :

That 's also a surprise i got after re-enabling thermald. I can't imagine what change have resolved it : old symlink purged, ..... ? , there is no more spamming, only the **** journalctl ***** info about a not compatible cpu) .

Looks like you can close that report as the problem seems gone.

Colin Ian King (colin-king)
Changed in thermald (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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