Is this possible to reproduce using thermald built from
https://github.com/intel/thermal_daemon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036135
Title:
thermald assert failure: *** stack smash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
There is no powerlimit via RAPL also here. Prochot can be generated by some
device on the system. We don't know the source.
If some old kernel works it is possible that newer kernel activated some new
device which is causing issue.
It is also possible that some device is now malfunctioning on the
Also monitor
# cat /proc/interrupts | grep Thermal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
To manage notifications ab
As Doug correctly described, there is a active prochot situation on the system,
so processor frequency is limited.
Can you dump:
#grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
Also if you are able to boot the system without being stuck at 800MHz, can you
try
#echo 1 > /sys/devices/system
With the increase in power limit by 2W from the thermal tables results
in increase power for CPU driving to higher frequency may be saturating
GPU.
It will take some time to come up with some algorithm. May be part of
another power sharing daemon.
--
You received this bug notification because yo
Looks like some game mode daemon or program, which is changing parameters for
cpu frequency.
Like energy performance preference was changed to balance_power.
Need to find out what is that program, may be some tuning can be done there as
it knows game is going to be played.
Also this will be help
balance_power is not a kernel default, so something on the system
running which is changing cpufreq parameters. "balamce_performance" is
the default.
Anyway thermald is setting the package power limit as per thermal
tables. There is no power sharing info in the tables.
We have this power sharing
Thanks. I can buy, I don't have gaming skills!
You already indicated that limiting cpu frequency or removing turbo boost helps.
I want to see if the energy_performance_preference or workload_request works.
"workload_request" will be the best as this is one setting for all CPUs.
If this works then
It will also be great if you can specify how to download and play the
game to get to this condition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944389
Title:
Thermald 1.9.1-1ubuntu0.6 keeps Tige
In your current 5.10 kernel try this setting:
#for i in {0..7}; do echo balance_power >
/sys/devices/system/cpu/cpufreq/policy$i/energy_performance_preference;
done
confirm with
for i in {0..7}; do cat
/sys/devices/system/cpu/cpufreq/policy$i/energy_performance_preference; done
balance_power
bal
I have the same XPS 9310 with
5.11.0-34-generic #36-Ubuntu SMP Thu Aug 26 19:22:09 UTC 2021 x86_64 x86_64
x86_64 GNU/Linux
# tree /sys/bus/pci/devices/\:00\:04.0
/sys/bus/pci/devices/:00:04.0
...
...
├── uevent
├── vendor
└── workload_request
├── workload_available_types
└── work
This is just long term package power limit after reaching 53C
"/sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/device/intel-rapl-mmio\:0/constraint_0_power_limit_uw".
Doesn't include off package limit.
You need 5.11 kernel atleast for those workload controls. Tiger lake
controls patches ar
I can give you some other knob, please try that whether this improves
while playing this game.
#cd /sys/bus/pci/devices/:00:04.0/workload_request
#echo idle > workload_type
or
# echo bursty > workload_type
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Data from /sys/class/thermal are usually stale. They are left from previous
platforms. The actual limits comes from adaptive tables based on the condition
match. This is what OEM defined for the system.
Also without adaptive power limits are insane here.
Thermal doesn't reduce GPU frequency. It
There is a temperature sensor "THP" which has a limit of 53C. This
temperature exceeded which calls for thermal throttling to limit to 15W
by thermal tables on this system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Run the github version
#systemctl disable thermald
#thermald --no-daemon --loglevel=info --adaptive
Attach the log. It is possible that skin temperature a limit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Try the upstream version
https://github.com/intel/thermal_daemon
May be missing some backports.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944389
Title:
Thermald 1.9.1-1ubuntu0.6 keeps Tigerlak
Try these steps.
First disable thermald
#systemctl disable thermald
reboot
Then run the script
https://github.com/intel/thermal_daemon/blob/master/test/thermal-debug-dump-ubuntu.sh
It will generate a tar file. Upload that.
Also continue to use the system after the test and see if you see the sam
I wish fan control worked.
I release v2.4.6 with the changes. This is in master branch with tag v2.4.6.
There are three commits on top of v2.4.5 to address this issue.
Please try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Thanks for the comment.
I would like to know something more about this system?
- Is this a desktop?
- Do you see any entry where /sys/class/thermal/cooling_device*/type = fan?
If you see can you control fan speed via
/sys/class/thermal/cooling_device*/cur_state
I will cleanup the change and uploa
Please try this version
https://github.com/intel/thermal_daemon/tree/ubuntu-bug-1930422
checkout branch ubuntu-bug-1930422.
Then repeat comments at #11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
I see that this system doesn't have all expected table and has one
default table which has just one entry. So need some special
implementation. I will implement and send a branch to test.
But keep in mind that limit is set at 71C. So I know there will be complaints
that there is too much throttl
Again I don't see any throttling.
With the version from
https://github.com/intel/thermal_daemon
Can you do
#systemctl disable thermald
reboot
from a command line
#thermald --no-daemon --loglevel=debug --adaptive
Attach the output
Alternatively you can just add --loglevel=debug instead of logl
Both logs looks same. I don't see any throttling.
This is a backported version of thermald in Ubuntu.
Can you run with upstream version of thermald
https://github.com/intel/thermal_daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Edit /usr/lib/systemd/system/thermald.service to add option --loglevel=info.
Basically
/usr/sbin/thermald --systemd --dbus-enable --adaptive
changes to
/usr/sbin/thermald --systemd --dbus-enable --adaptive --loglevel=info
Then reboot and when you see the condition attach the output of
journalctl
If possible please try to build from
https://github.com/intel/thermal_daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769236
Title:
CPU frequency stuck at minimum value
To manage notification
Please attach logs as suggested in comment #14 and comment #16.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800446
Title:
kidle_inject constantly running
To manage notifications about this bug g
There is a patch in discussion to avoid thermal shutdown from kernel
Re: [PATCH 1/3] thermal: core: Add indication for userspace usage
from Kai-Heng Feng .
If that gets merged then we can disable int340x thermal shutdowns from
the kernel and let thermald manage shutdown. This gives opportunity f
As per commeent #32, thermald helps here. But it is better to avoid kernel
shutdown for one bad temperarure sample instead of some running average. We
should have "mode" attribute so that we can avoid this by disabling the zone.
I will see what can be done to add "mode" attribute for these zones.
# dpkg -l thermald | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-==
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance workaround for Dell 739
Used version
#apt list | grep thermald
thermald/now 1.9.1-1ubuntu0.2 amd64 [installed,local]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance workaround for Dell 7390 2-in-1
The attached file contains two screen shots:
- power_limit_before.png (old version thermald/now 1.9.1-1ubuntu0.1 amd64)
- power_limit_after.png (new version thermald/now 1.9.1-1ubuntu0.2 amd64)
Under "stress" workload, the max power consumed is capped below 9W. With
the new version it is maintaini
What else is needed here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance workaround for Dell 7390 2-in-1 Ice Lake
To manage notifications about this bug go to:
https://bug
To reproduce this:
Boot Ubuntu 20.04 LTS (Focal Fossa)with 5.4 kernel.
Open two terminals:
-In the first terminal run the following command "turbostat --show PkgWatt"
-In the second terminal run some all CPU busy workload, like stress-ng or mprime
After few seconds turbostat will show that power
Anything more is required this to be applied?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance workaround for Dell 7390 2-in-1 Ice Lake
To manage notifications about this bu
I am not sure what is the thinkpad issue. Is it something new or old
which should have been fixed with dptfxtract and thermald?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performan
Power limits from this platform:
abuser@labuser-XPS-13-7390-2-in-1:/$ grep -r .
sys/bus/pci/devices/\:00\:04.0/power_limits/*
sys/bus/pci/devices/:00:04.0/power_limits/power_limit_0_max_uw:900
sys/bus/pci/devices/:00:04.0/power_limits/power_limit_0_min_uw:250
sys/bus/pci/device
Please change this to "Confirmed".
As you can see the power limits, it will limit performance from what you can
get at 15W.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance
** Description changed:
As reported here:
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream
This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switc
Public bug reported:
As reported here:
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream
This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4
It is not really used in the relationship file. So other OS may not be
using this so probably never validated the critical trips. Better to
disable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187308
On Thu, 2020-04-16 at 20:54 +, Anton Keks wrote:
> No, normally it's below 60C.
>
> I can get it to 80C (and shutdown) when the AC is plugged in and
> charging the battery and I load my CPU a lot at the same time.
>
> Usually it means a video conference with several people and charging
> at
>
On Thu, 2020-04-16 at 20:18 +, Anton Keks wrote:
> I have traced it to int3403_thermal module.
> If I do rmmod int3403_thermal - the thermal_zone3 goes away an no
> thermal shutdown is happening.
> I can use it as a workaround - but is it dangerous for the HW?
>
> https://github.com/torvalds/l
On Thu, 2020-04-16 at 07:22 +, Anton Keks wrote:
> 20.04 includes thermald 1.9.1, but it is not running by default.
>
> $ systemctl status thermald
> ● thermald.service - Thermal Daemon Service
> Loaded: loaded (/lib/systemd/system/thermald.service; disabled;
> vendor preset: enabled)
>
On Sat, 2019-08-17 at 05:24 +, Anthony Wong wrote:
> On Sat, Aug 17, 2019 at 1:05 AM Srinivas Pandruvada <
> srinivas.pandruv...@linux.intel.com> wrote:
>
> > The patch for changing TCC offset can only be in for 5.4 kernel.
> > Then
> > there will be no
The patch for changing TCC offset can only be in for 5.4 kernel. Then there
will be no MSR access.
So the option is to take out of mainline kernel patch to avoid this or avoid
workaround option.
I don't know if there are any other options.
--
You received this bug notification because you are a
Correct.
I think you are using with 5.3 kernel or using workaround option.
Without dptfxtract output or user manually created thermal-conf.xml or
using aurogenerated, this is risky to play with power as the skin will
hit limit.
Thanks,
Srinivas
On Thu, 2019-08-15 at 16:28 +, Anthony Wong wrot
Hi,
Is this issue reproducible in the latest thermald 1.9 release? If yes, I want
to fix ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811730
Title:
Thermald does not set max CPU after reset
Please use the latest dptfxtract tool version 1.4.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838590
Title:
Update thermald to 1.9 release
To manage notifications about this bug go to:
https:
Rui submitted a patch to change to dev_notice()
https://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git/commit
/?h=next&id=3c7110fab805766450c5d2eac1c994d4c8c230d3
But with default log level in Ubuntu, I think dev_notice will be dumped
to dmesg. Is it correct?
I submitted another patch
This is not a thermald bug. Linux doesn't have ABI to change PL1 limit
set via MMIO I/F as suggested in the link, so thermald can't us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815214
Title:
This is not related to thermald and thermald may not fix this.
Rui is submitting a kernel patch to downgrade message level.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal
You marked this for thermald bug.
Can you try this?
#systemctl disable thermald
reboot
then try to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815214
Title:
Lenovo T480: throttling CP
Also can you attach acpi.out by issuing the following command
#acpidump > acpi.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800446
Title:
kidle_inject constantly running
To manage notificati
Do we still have this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800446
Title:
kidle_inject constantly running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
I suggest, disable thermald service first.
#systemctl diable thermald
then reboot
Then on a window
#thermald --loglevel=info --no-daemon
And do your regular work,
When you experience slow down, copy paste output of the thermald and
attach.
--
You received this bug notification because you are
These are kernel bugs, so better to file in kernel bugzilla.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
To manage noti
dimahetman (dimahetman),
please also try as described in #18.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797802
Title:
Erratic behavior of CPU frequency control under load
To manage notificatio
try running thermald in a window from command line.
systemctl stop thermald
#thermald --no-daemon --loglevel=info
Then do what triggers this, and attach the output of the above command.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Good observation. We need to update man page.
I am looking for volunteer for updating man page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799389
Title:
not use /etc/thermald/thermal-conf.xml by
Glen:
Thanks for good suggestions. I will consider for next revision.
But problem in this bugzilla is addressed. This system has buggy
temperature threshold. OEM didn't find because Windows will not use any
more.
So with the change we really look if Windows would have used this
threshold based on
I have pushed workaround for this. Please try the latest thermald
https://github.com/intel/thermal_daemon/tree/v1.7.2-test
This should show version 1.7.2 when you do thermald --version.
Please test and let me know if the problem is fixed. Reboot your system
to try new version, so that it will not
If /var/run points to tmpfs then you can't change. Let me update a new
version of thermald by working around this issue. But you have to build
it yourself and try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Thanks for providing the dump. Unfortunately the Spectre system has bad
thermal table values (Since Windows 10 is using more advanced tables,
manufacturer didn't notice bad values impact.). So there may be more
systems like this. So I want to implement some workaroud. Can you give
me dump of
# cat
/var/run/thermald/thermal-conf.xml.auto will not be regenerated, if
present, so you can edit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769236
Title:
CPU frequency stuck at minimum value
To ma
Can you also attach output of acpidump?
#acpidump > acpi.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769236
Title:
CPU frequency stuck at minimum value
To manage notifications about this bu
Thanks for providing detailed logs. I see in the log:
"
cthd_sysfs_zone::read_cdev_trip_points: ZONE bound to CDEV status 0
Sorted trip dump zone index:5 type:B0D4:
index 2: type:passive temp:4 hyst:1000 zone id:5 sensor id:5 cdev size:0
"
So this is a problem in configuration of the system.
This seems to have wrong temperature threshold issue. 64C is too low threshold.
What is the dump of the following:
#grep -r . /sys/class/thermal/*
Meanwhile you can edit the file thermal-conf.xml.auto and change
*
to
95000
to make system usable.
--
You received this bug notification because you
On Tue, 2018-04-17 at 11:56 +, Colin Ian King wrote:
> Ah, I'm mistaken, that gets loaded later. Do you mind supplying the
> list of modules loaded on your machine so I can see if I can find the
> driver that is failing on the thermal zone 4. Can you run:
>
> lsmod
>
I am thinking wifi. If
Please try 1.6 version. If still have problem then
# sudo systemctl stop thermald
# sudo thermald --no-daemon --loglevel=debug
and send logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661384
Tit
Thanks Mike.
I would like to help to close the other issues pointed here on macbook and
others. But need debug logs like you provided. Also
grep -r . /sys/class/thermal/*
Also if there are some sysfs entries for fan control /sys/devices/platform or
others.
Looks like there is a way to control fa
Mike, for your issue 2 I have uploaded a change.
https://github.com/01org/thermal_daemon/commits/master
In systems like yours which runs close to critical the auto max adjustment
needs some better algorithm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Colin,
Do you have some auto builder which can make a test package for Mike? I added
one commit on my branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600599
Title:
Thermald is totally broken
Embedded controller controls fan and on many systems it will not allow
OS to control Fans. So thermald can't control unless user manually
configured to do (In that case he has some means to control speed from
sysfs).
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Mike,
For issue 2 please enter a new bug, I will explain in that what I see and
possible fix to try.
Let's not mix with fan speed control. thermald can control Fan speed if there
is a way to control Fan speed (namely called ACPI Fan or some proprietary
control like in thinkpad). man therma-conf
I see that your load is bringing up temperature to 97C, which is one
less than critical temp 98C of your system. So whatever cooling of your
device without thermald is pretty bad. So your device can reboot any
time. Also your BIOS locked good power control method, so can't use.
Let me see if I can
Jérôme,
Thermald didn't even start on your system.
"Unsupported cpu model, use thermal-conf.xml file or run with
--ignore-cpuid-check
THD engine start failed"
I don't know how this can be cause of you slow down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
You can always increase the throttling temp as described in"man
thermald"
# dbus-send --system --dest=org.freedesktop.thermald
/org/freedesktop/thermald
org.freedesktop.thermald.SetUserPassiveTemperature string:cpu
uint32:9
Also before you do that
# stop thermald
# thermald --no-daemon --logl
@Graham,
I see you attached kernel log, but doesn't have boot time log. Can you
just boot the system and
# dmesg | grep "locked by BIOS"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656528
Title:
Can you do the following and run your loads:
# sudo systemctl stop thermald
# sudo thermald --no-daemon --loglevel=debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661384
Title:
default setting
#!16
Kasper Peeters (kasper-peeters), atleast you can provide logs, by doing
the following and run whatever workloads yo do on macbook
#systemctl stop thermald
#thermald --no-daemon --loglevel=debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
To really debug this, need logs. There may be number of causes if the
temperature is not really high.
There may be wrong powerlimits configured in RAPL registers. So it is better to
debug for good.
#systemctl stop thermald
#thermald --no-daemon --loglevel=debug
--
You received this bug notific
On Thu, 2016-11-10 at 10:10 +, Jean-Pierre van Riel wrote:
> @SunBear
>
> I'm also having issues with these apparent errors:
>
> thermald[1309]: 13 CPUID levels; family:model:stepping 0x6:3c:3
> (6:60:3)
> thermald[1309]: Polling mode is enabled: 4
> thermald[1309]: sysfs write failed enable
I ran on 4.8, I don't see those errors. Can you run on command line?
# sudo systemctl stop thermald
# sudo thermald --no-daemon --loglevel=debug
I want to see which sysfs write is causing issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
sysfs paths can't change, so need to look at the kernel. I didn't add
any new stuff between 4.4 to 4.8 in kernel. I will look into this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625741
Title:
Basically sysfs writes are failing with 4.8 kernel, so all those errors
in http://paste.ubuntu.com/23207813/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625741
Title:
thermald doesn't seem to wo
This is upto you what you want to do with your system. Don't judge
system heat with Fan speed. If you want debug, provide logs with log
level suggested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
I am interested in seeing run with loglevel=debug. They are kicked at 10C below
TJMAX and you can be shutdown by kernel any moment as the temperature can swing
5-10C immediately.
If someone don't care about life of the system or shutdowns they can increase
this setting by setting one time dbus m
_TRT and _ART are optional. If not the algorithm falls to default to do
CPU passive control. The thermald controls are complimentary to was BIOS
is doing. If for any reason of the BIOS controls or fan is not able to
bring temperature down thermald will act, it will work as this will
reduce the cpu
As Colin suggested about the three errors related to _TRT and _ART, they
will appear once during startup. I see many folks confused about this,
so I downgraded this error in my tree.
https://github.com/01org/thermal_daemon/commit/8280fd7ec6cff6db6463c8a1b01d2e427e418226
--
You received this bug
@heynnema,
I think you just wanted to lower your temperature threshold. If that's
what you want, then you can just send
dbus-send --system --dest=org.freedesktop.thermald
/org/freedesktop/thermald
org.freedesktop.thermald.SetUserPassiveTemperature string:cpu
uint32:59000
This setting is saved, s
P.
commit 4a890d7e173678644882e6b863f3650e30d33052
Author: Srinivas Pandruvada
Date: Thu Feb 18 11:33:50 2016 -0800
Regression for default config file
f99f2b59fbbca04a13cad3f7d2dbc985bc7ee0cd caused regression
where for Android the default path is changed to TDRUNDIR.
This will caus
This is not a bug as not all platforms have these tables. We need to
downgrade the severity of these log messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568123
Title:
error messages about /
0x2d, 0x3e, and 0x3f are Xeon parts, where we don't want thermald to
start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480349
Title:
thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1
@Colin
I want to see if there is a race condition, by changing runlevel to 5 without
any other change. What do we need to change in systemd service file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I up still not sure about the root cause. Can anybody help on collecting
startup logs (journalctl -b)?
Can we just change runlevel to 5 and see if the problem is fixed.If there is a
race condition in loading then this should address this.
@Colin, What changes are required to run at run level 5? a
Currently systemd runlevels are [2345], can we try just [5]
In the systemd service file. thermald.conf
change
start on runlevel [2345] and started dbus
to
start on runlevel [5] and started dbus
If thermald is loading too early, then this will delay till run level 5.
--
You received this bug no
I think it has to do with the starting of thermald too early while driver
modules are not ready.
@Chris:
Can you attach thermald logs (when started by systemd) and also by disabling
and started by command line?
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
1 - 100 of 124 matches
Mail list logo
