This bug was fixed in the package thermald - 1.4.3-5ubuntu3
---
thermald (1.4.3-5ubuntu3) wily; urgency=medium
* Fix spamming kermel log (re-do) (LP: #1543046)
- we need upstream commit c2e17ee973c59ca2b0898a147fa059c0c32369f4
("csys_fs::write: return -errno on write failu
Verified this on an x220 which has been heavily loaded with the stress-
ng matrix test - this kicks in the thermal controls and one sees just
the one BIOS locked message and thereafter no more spamming.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bu
Hello Colin, or anyone else affected,
Accepted thermald into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/1.4.3-5ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Try this instead:
sudo add-apt-repository ppa:colin-king/thermald-wily-sru-1543046
sudo apt-get update
sudo apt-get upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spa
> sudo apt-get dist-upgrade
Forgive my ignorance: I always thought that "sudo apt-get dist-upgrade"
was the command-line way of upgrading to the latest release (e.g. from
Wily to Xenial).
I was way off, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> upgrading to Xenial is recommended.
Upgrading to Xenial may leave you with a broken, unbootable,
unrecoverable system.
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
OK, apologies for that bug, I overlooked my original upstream commit
c2e17ee973c59ca2b0898a147fa059c0c32369f4 ("csys_fs::write: return -errno
on write failure") from the Wily backport hence it was not propagating
the sysfs error status up to the RAPL interface. I've prepared a fix
(1.4.3-5ubuntu3)
OK, not sure how that didn't get fixed properly in Wily, I'll look at it
first thing on Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updatin
Mind you, Wily is EOL on the 28th July, so upgrading to Xenial is
recommended.
** Changed in: thermald (Ubuntu Wily)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
This is NOT fixed on wily.
Thanks btw @30 for providing a quick test command which nobody else did
before.
$ grep "powercap intel-rapl:0: package locked by BIOS" /var/log/kern.log
[..]
Jul 7 22:15:11 xxx1 kernel: [ 3027.312178] powercap intel-rapl:0: package
locked by BIOS, monitoring only
Is this supposed to be fixed in 15.10 by now?
$ uname -a
Linux gabor-xps 4.2.0-36-generic #42-Ubuntu SMP Thu May 12 22:05:35 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
$ dpkg -l | grep thermald
ii thermald 1.4.3-5ubuntu2
amd6
This bug was fixed in the package thermald - 1.4.3-5ubuntu2
---
thermald (1.4.3-5ubuntu2) wily; urgency=medium
* Initialise bios_locked; may lead to random behaviour (LP: #1547594)
- bios_locked should be initialised to false so that RAPL is
enabled by default.
* thd_cde
This bug was fixed in the package thermald - 1.4.3-5~14.04.4
---
thermald (1.4.3-5~14.04.4) trusty; urgency=medium
* csys_fs::write: return -errno on write failure (LP: #1543046)
- this detection helps previous fixes to stop BIOS message spamming
thermald (1.4.3-5~14.04.3) trus
I've soak tested thermald with 1.4.3-5~14.04.4 and the bug does not
occur, we don't see any spamming of the log with the "package locked by
BIOS, monitoring only" message. Just one occurrence of the message
occurs, and no more, as one expects with this fix.
** Tags removed: verification-needed
**
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating powercap RAPL powerlimi
1.4.3-5~14.04.4 in trusty -upload queue, waiting for 1.4.3-5~14.04.3 in
updates to be rejected and for 1.4.3-5~14.04.4 to be promoted to
-updates for testing again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
1.4.3-5~14.04.4 fixes it for me, been running now for 2 hours with no
messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating powercap RAPL
I've uploaded thermald 1.4.3-5~14.04.4 for testing in my PPA ppa
:colin-king/thermald-sru
sudo add-apt-repository ppa:colin-king/thermald-sru
sudo apt-get update && sudo apt-get upgrade
I have also tested this out with the --enable-dbus on a few machines and
the latest .4 version seems to fix
OK, seems like commit c2e17ee973c59ca2b0898a147fa059c0c32369f4 may be
required too:
csys_fs::write: return -errno on write failure
sysfs writes can fail for various reasons, and returning -errno is
useful for indicating an error so that the caller can determine
the best strate
Thanks Martin, the --enable-dbus does trigger it for some reason. I
appreciate you finding this and letting me know. I will get around to
fixing this next week
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Colin could I implore you to include --enable-dbus in one more test,
that appears to be the triggering factor for my machine. Without it the
problem does appear to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
OK, I've spent the last 3 hours verifying this manually on 3 different
machines that trigger this issue.
Without 1.4.3-5~14.04.3, I see:
[72761.740827] powercap intel-rapl:0: package locked by BIOS, monitoring only
[73066.21] powercap intel-rapl:0: package locked by BIOS, monitoring only
[730
Colin:
# dpkg -l | grep thermald
ii thermald 1.4.3-5~14.04.3 amd64
Thermal monitoring and controlling daemon
Yes still getting those messages, a new line every 5-10 seconds.
[178055.276188] powercap intel-rapl:0: package locked by BIOS, monitor
Just to re-iterate, this fix stops the spamming messages:
[38458.753468] powercap intel-rapl:0: package locked by BIOS, monitoring only
[38637.993447] powercap intel-rapl:0: package locked by BIOS, monitoring only
[38674.154336] powercap intel-rapl:0: package locked by BIOS, monitoring only
[38691
@Martin can you double check:
dpkg -l | grep thermald
and also what messages are you seeing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating
thermald 1.4.3-5~14.04.3 does not fix this issue for me.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermal
Hello Colin, or anyone else affected,
Accepted thermald into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/1.4.3-5ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Fixes currently waiting in -proposed for Trusty and Wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating powercap RAPL powerlimit
To manage
** Description changed:
- When thermald updates /sys/devices/virtual/powercap/intel-rapl/intel-
- rapl:0/constraint_0_power_limit_uw the kernel is emitting the following
- message:
+ [SRU Justification][Trusty][Wily]
+
+ thermald is triggering the kernel to SPAM the kernel log with frequent
"pac
** Also affects: thermald (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: thermald (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: thermald (Ubuntu Trusty)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: thermald (Ub
FYI I'm running trusty with linux-generic-lts-xenial 4.4.0.18.10,
was getting same thermald spamming until I manually upgraded
to the package as per comment#8 above:
- upgrade thermald:amd64 1.4.3-5~14.04.2 1.4.3-5~14.04.3
, then no more kern.log spamming, thanks!.
--
You received this bug notifi
Just did a fresh install on my XPS 13 9343 with Ubuntu 16.04 Beta 2 and
thermald 1.5-2. No more error messages appear. Before I was running
15.10 and dmesg was spammed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Please try thermald from the following ppa:
sudo add-apt-repository ppa:colin-king/thermald-1564443
sudo apt-get update
sudo apt-get install --reinstall thermald
and let me know if it fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Unfortunately the 1.4.3-5ubuntu1 does not fix this bug for me. I'm using
Ubuntu 16.10 on a Dell XPS 13 9343 machine with Haswell i7-5500U CPU and
still getting this same error spammed in syslog every 4 seconds even
after updating the thermald package from wily-proposed.
--
You received this bug n
** Changed in: thermald (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating powercap RAPL p
Fix committed:
https://github.com/01org/thermal_daemon/commit/f1a77c5f3b936ba8a7a63d587a803641974f8e62,
currently waiting in -proposed
** Changed in: thermald (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: thermald (Ubuntu)
Importance: Medium => High
--
You received this
FYI, I applied the pull request locally and it seems to fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating powercap RAPL powerlim
sorry for the noise, reported as Bug #1543109
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel log when updating powercap RAPL powerlimit
To manage notificatio
Workaround pull request: https://github.com/01org/thermal_daemon/pull/79
I'll see what Intel says about this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543046
Title:
thermald spamming kernel l
@dino99, please file a new bug for that particular issue, I am trying to
get these issues fixed one by one rather than trying to address all the
different issues in one fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This not not the only existing issue, and flooding journalctl.
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
Feb 08 07:16:23 u64 thermald[791]: 10 CPUID levels;
41 matches
Mail list logo
