ubuntu 15.04 overheats

[Renardo]

On 2015-04-26 I upgraded to Ubuntu 15.04 (from 14.10). Since then, my notebook (HP envy dv6) fan is nearly always on, and the notebook switched off several times, probably due to overheating. Each time I was working with Firefox; watching the "livestream" of www.tagesschau.de seems to be a good way of reproducing the problem.

Going back to the 3.16.0-31 kernel (still offered by grub) seems to circumvent the problem. When I boot 3.16 the fan runs only occasionally. My first 15.04 kernel was 3.19.0-15, today I got -16 but the problem is the same.

Before the machine switches off (it does not shut down Linux but just goes out) "top" shows me eight instances of "kidle_inject", obviously desperately but hopelessly trying to keep processor load down. Under the 3.19 kernel the "plugin-container" process goes to loads of more than 100 % (on a four-core box), under 3.16 it never goes beyond 60 %. Note that between the "overheat" and the "normal" scenario I change only the kernel in the boot menu, all other binaries are the same (15.04). Especially, it's the same firefox.

I fear that within a couple of weeks more kernel versions will arrive at my system and eventually push the working 3.16 kernel out of my grub menu, and then I shall have no way left of running my system for more than 20 or 30 minutes.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: kernel-common (not installed)
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 6 20:57:39 2015
InstallationDate: Installed on 2014-06-09 (331 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: kernel-package
UpgradeStatus: Upgraded to vivid on 2015-04-24 (12 days ago)
---
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: refo 2055 F.... pulseaudio
 /dev/snd/seq: timidity 984 F.... timidity
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=5dff5ccc-0b4d-436e-968d-bce0419cc3cd
InstallationDate: Installed on 2014-06-09 (369 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=eo.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=89e69c26-b493-4882-a796-976d1d8a09b5 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-34-generic N/A
 linux-backports-modules-3.16.0-34-generic N/A
 linux-firmware 1.143.1
Tags: vivid
Uname: Linux 3.16.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/03/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 181B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 52.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.12:bd09/03/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A110000305920000620100:rvnHewlett-Packard:rn181B:rvr52.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY dv6 Notebook PC
dmi.product.version: 088A110000305920000620100
dmi.sys.vendor: Hewlett-Packard

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc3-vivid/

[Renardo (renardo)]

If I get it right then the kernel versions proposed by Brad and Joseph are different. I first thried Brad's proposal, doing "apt-get update" and "apt-get dist-upgrade". This left me with the 3.19.0-16 kernel I already had. As I mentioned it does not fix the problem.

Then I tried to download the mainline kernel suggested by Jospeh but his URL (.../v4.1-rc3-vivid/) gives me a "not found on this server". There is, however, an rc2 rather than rc3 kernel (rc3 is "unstable"). I will try that one.

I haven't yet learned how to add a "tag" to a bug but will try to find out.

[Renardo (renardo)]

I have found how to add tags ("edit description" opens a text line with tags).

I have installed the 4.1 rc2 kernel, and find it in my grub menu. Unfortunately I cannot test with it; when I try to boot it I get a message box saying "the system is running in low graphics mode", and when I confirm it the screen flickers between graphics mode (login screen) and console mode so fast that I cannot log in. Ctrl-Alt-F1 does not work, and I need graphics mode to reproduce the problem anyway. Sorry.

[Joseph Salisbury (jsalisbury)]

It looks like the link to the mainline kernel changed. It can be downloaded from:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc4-unstable/

[Renardo (renardo)]

Thanks. I found and downloaded the rc4 kernel but have the same problem as with the rc2 kernel: The login screen remains visible only for a fraction of a second, then a console screen appears (displaying messages from system startup) and then a new login screen appears. I think it is a new one as it does not display the one or two password character bullets I managed to type into the previous one.

So I cannot log in, and without logging in I cannot start Firefox to check whether my problem persists.

[Renardo (renardo)]

I tried several things to get the system up under the rc4 kernel. I now can boot to a console screen but as soon as I try to start graphics mode I get the problem that the login screen remains only for a fraction of a second. So my questions are:

(1) Can I try anything else to start the system in graphics mode under the rc4 kernel?
(2) Can I provide any useful log data from the problem under the 3.19.0-16 kernel?

Thanks for any suggestions.

[Joseph Salisbury (jsalisbury)]

Can you give the latest 3.19 upstream stable kernel a test? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/

[Renardo (renardo)]

Thanks for the hint. I did that today and after a few minutes of video streaming (www.tagesschau.de) "top" showed me the now well-known "kidle_inject" processes but the box held out for a bit over ten minutes, which is more but not significantly more than before. Then it switched off. I booted the 3.16 kernel, reloaded the same video stream (it is available for two hours), and it played the full 15 minutes without any kidle_injects appearing. And without powering off the machine, of course.

This time "top" (under 3.19) never showed me any processes (firefox, plugin-container) going anywhere near 100% of CPU load; everything remained under 50% most of the time, more or less as with the old kernel. And still those kidle_inject processes come up. Could it be a false alarm (despite the very warm air coming from the fan slots)? I know that kidle_inject generates no CPU load, just blocks other processes from taking a CPU. Could it still have influence on the temperature sensor and the fan?

[Joseph Salisbury (jsalisbury)]

We would like to collect some additional information about your system. From a terminal, please run the following:

apport-collect 1452421

[Guy Steels (freeman-v)]

I experience similar issues since I upgraded to Ubuntu 15.04 on my Dell XPS 13 Developer Edition (second gen). My laptop does not overheat (and shuts down) but kidle_inject processes kick in and my GUI starts lagging as soon as I eg. watch a HTML or Flash video in Chrome or Firefox, visit a website with a lot of animations, ... I have the impression it's limited to graphic instensive stuff inside a browser. I use the latest stable kernel (3.19.0-18-generic).

[Piotr Kowalczyk (nicon-5)]

I'm having same issue.
Using kernel: 4.1.0-040100rc6-generic
Sensors are showing huge temperature, even though load is around 0.15.

root@localhost:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +75.0°C (crit = +97.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +74.0°C (high = +84.0°C, crit = +100.0°C)
Core 0: +74.0°C (high = +84.0°C, crit = +100.0°C)
Core 1: +72.0°C (high = +84.0°C, crit = +100.0°C)
Core 2: +72.0°C (high = +84.0°C, crit = +100.0°C)
Core 3: +70.0°C (high = +84.0°C, crit = +100.0°C)

root@localhost:~# w
 17:11:10 up 6 days, 15:47, 2 users, load average: 0,15, 0,16, 0,17
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
nicon pts/0 :0 07cze15 6days 0.00s 3.82s /usr/bin/kwrited
nicon pts/1 :0 pią23 2.00s 0.05s 0.00s /bin/bash

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

apport information

[Renardo (renardo)]

I notice that this bug is still in "Incomplete" state. What else can I provide?

[Renardo (renardo)]

Today my Ubuntu kernel updated to 3.19.8-031908. I tried my usual www.tagesschau.de video, and it held out the full fifteen minutes. "top" showed me the usual eight kidle-inject processes, and responsiveness was slow but the system did not power off. It looks like progress… but it could be due to the lower outside temperature today. I will try again.

[Renardo (renardo)]

Recently there was an update to thermald, and I did a new test but the problem persists.

Again, what can I do about the "imcomplete status" of this bug?

[Launchpad Janitor (janitor)]

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

[Renardo (renardo)]

As the problem seemed to be related to the kernel -- booting a 3.16 kernel made it disappear -- I tested every new kernel that was installed since then, and the problem was always there, even after upgrading to Ubuntu 15.10 (Wily or so). A couple of days ago I received the 4.2.0-18 kernel, and the problem seems gone. Sensor temperatures do not go anywhere near the critical values, the fan is silent most of the time, and no kidle_inject processes start.

Of course I have no idea what might have made this difference but I truly appreciate it.

[Renardo (renardo)]

Sorry, I stand corrected… must have booted 3.16 yesterday. Today with the 4.2.0 kernel the core temperatures rose again, only not so much as half a year ago. Outside -- and consequently room -- temperatures here in the Northern Hemisphere have dropped somewhat, that might account for it. So my notebook did not switch off but came into considerable neighbourhood (proximity? sorry, poor English) of the critical temperatures.
I will stay with the 3.16 kernel.