After upgrade to Ubuntu 15.04, wrong temperature readings after wake from suspend cause fan to go crazy

[Stannis King]

After I upgraded to Ubuntu 15.04, I started having problems with the fan going crazy after I wake Ubuntu from suspend. At first, this only happened on a few occasions when waking Ubuntu from suspend, but now it seems to happen every time I wake it from suspend.

I'm guessing the fan goes full speed due to the wrong readings of the temperature. "sensors" indicates temp4 as 100°C right after I wake Ubuntu from suspend, but temp4 is usually only around 30-40°C.

The problem goes away when I restart Ubuntu. I had no problems of this kind on previous versions of Ubuntu.

I'm not sure if the package responsible is "linux", but I assume it is because of this: https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: macak 1564 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Apr 25 13:47:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-04-21 (3 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
MachineType: Hewlett-Packard HP Compaq 6910p (RH239AV)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=d68e56a7-69e6-43ce-b25b-20550f5e34bf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago)
dmi.bios.date: 11/04/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MCD Ver. F.17
dmi.board.name: 30C1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 68.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MCDVer.F.17:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6910p(RH239AV):pvrF.17:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6910p (RH239AV)
dmi.product.version: F.17
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Stannis King (stannisking)]

Christopher, before reading your reply, I tried booting Ubuntu by choosing Linux 3.16.0-34 in the advanced boot options. This solved the problem.

Should I proceed with updating BIOS, or is there another way to solve the problem based on the new info?

[Stannis King (stannisking)]

Christopher, I update the BIOS, but the problem remains. After updating the BIOS from Windows, I booted Ubuntu normally. When I close the laptop lid, Ubuntu goes to suspend. When I wake it from suspend -- the fan goes crazy again and the sensors give the above mentioned output.

This is the output of your command:

68MCD Ver. F.19
07/06/2010

I changed the status to "confirmed", as you said.

[Stannis King (stannisking)]

As was the case before the BIOS update, the problem doesn't appear when I boot with Linux 3.16.0-34.

[penalvch (penalvch)]

Stannis King, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Stannis King (stannisking)]

Christopher, I'm not really familiar with any of this, so I want to be really clear on what I'm supposed to do.

I'm supposed to start from v4.1-rc1-vivid/ in here: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

What am I supposed to download and install from there? I'm guessing all of the following from v4.1-rc1-vivid/:

linux-headers-4.1.0-040100rc1-generic_4.1.0-040100rc1.201504270235_i386.deb
linux-headers-4.1.0-040100rc1-lowlatency_4.1.0-040100rc1.201504270235_i386.deb
linux-headers-4.1.0-040100rc1_4.1.0-040100rc1.201504270235_all.deb
linux-image-4.1.0-040100rc1-generic_4.1.0-040100rc1.201504270235_i386.deb
linux-image-4.1.0-040100rc1-lowlatency_4.1.0-040100rc1.201504270235_i386.deb

Correct? Or only the "image" ones?

[penalvch (penalvch)]

Stannis King, please see https://wiki.ubuntu.com/Kernel/MainlineBuilds#Installing_upstream_kernels .

[Stannis King (stannisking)]

Christopher, I've tested all the upstream kernels and the bug appears in all of them. What do I do next? Can I now uninstall upstream kernels?

[penalvch (penalvch)]

Stannis King, feel free to uninstall all the kernels.

Despite this, the next step is to fully commit bisect from kernel 3.16 to 3.19 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Stannis King (stannisking)]

Christopher, I can barely understand what I'm supposed to do.

I followed the steps from your link and somehow got all the way to "Take a look first to see what you can learn" successfully. However, that's where I get stuck, because I can't find the tag for the bug-free kernel I'm using on Vivid. The kernel is 3.16.0-34-generic, but I can't find the tag for it on http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/refs/tags, which is necessary for the "git log --oneline" step.

What do I do?

[penalvch (penalvch)]

Stannis King, version or commit bisecting the Ubuntu kernel is typically most difficult. You would want to switch to bisecting the upstream kernel.

[Stannis King (stannisking)]

Christopher, are you sure? I don't see what would be the point of that. I've already established that all upstream kernels have the bug, as well as the default Vivid kernel, 3.19. I thought I was supposed to bisect between the last known good kernel and first known bad kernel.

[Juan Rada-Vilela (jcrada)]

Hi, I am suffering the same issue in Vivid 64bit on a MacBookPro 11,2. In my case, after a few hours after suspend, the computer gets very hot and the fans go full speed.

[penalvch (penalvch)]

Juan Rada-Vilela, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Reece (reece)]

Same here for the following system upgraded to 15.04 from 14.10 yesterday...

System Information
 Manufacturer: Dell Inc.
 Product Name: XPS L421X
 Version: A04
 Serial Number: JG74GS1
 UUID: 4C4C4544-0047-3710-8034-CAC04F475331
 Wake-up Type: Power Switch
 SKU Number: xxx123x#ABA
 Family: 103C_5335KV

This also seems relevant...

Handle 0x0028, DMI type 27, 14 bytes
Cooling Device
    Temperature Probe Handle: 0x0029
    Type: Fan
    Status: OK
    OEM-specific Information: 0x00000000
    Nominal Speed: 0 rpm # while the fan is audibly running!

Handle 0x0029, DMI type 28, 22 bytes
Temperature Probe
    Description: Temperature Probe
    Location: Processor
    Status: OK
    Maximum Value: Unknown
    Minimum Value: Unknown
    Resolution: Unknown
    Tolerance: Unknown
    Accuracy: Unknown
    OEM-specific Information: 0x00000000
    Nominal Value: 2594.0 deg C

[Reece (reece)]

Perhaps also relevant: Battery life is seems significantly down since 15.04. I don't know whether that might be attributable to fans or something else.

[penalvch (penalvch)]

Reece, unfortunately it's not terribly relevant. However, if you are having an issue in Ubuntu, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Launchpad Janitor (janitor)]

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