Here's the output of fwts fan: Results generated by fwts: Version V17.03.00 (2017-03-16 03:24:38).
Some of this work - Copyright (c) 1999 - 2017, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2017, Canonical. Some of this work - Copyright (c) 2016 - 2017, IBM. Some of this work - Copyright (c) 2017, ARM Ltd. This test run on 12/05/17 at 08:27:40 on host Linux locrian 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64. Command: "fwts fan". Running tests: fan. fan: Simple fan tests. -------------------------------------------------------------------------------- Test 1 of 2: Test fan status. Test how many fans there are in the system. Check for the current status of the fan(s). PASSED: Test 1, Fan cooling_device5 of type iwlwifi has max cooling state 19 and current cooling state 0. PASSED: Test 1, Fan cooling_device3 of type Processor has max cooling state 10 and current cooling state 0. PASSED: Test 1, Fan cooling_device1 of type Processor has max cooling state 10 and current cooling state 0. FAILED [MEDIUM] NoFanCurState: Test 1, Fan present but has no cur_state present. PASSED: Test 1, Fan cooling_device2 of type Processor has max cooling state 10 and current cooling state 0. PASSED: Test 1, Fan cooling_device0 of type Processor has max cooling state 10 and current cooling state 0. Test 2 of 2: Load system, check CPU fan status. Test how many fans there are in the system. Check for the current status of the fan(s). Loading CPUs for 20 seconds to try and get fan speeds to change. Fan cooling_device3 current state did not change from value 0 while CPUs were busy. Fan cooling_device1 current state did not change from value 0 while CPUs were busy. Fan cooling_device2 current state did not change from value 0 while CPUs were busy. Fan cooling_device0 current state did not change from value 0 while CPUs were busy. ADVICE: Did not detect any change in the CPU related thermal cooling device states. It could be that the devices are returning static information back to the driver and/or the fan speed is automatically being controlled by firmware using System Management Mode in which case the kernel interfaces being examined may not work anyway. ================================================================================ 5 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ 5 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: NONE Medium failures: 1 fan: Fan present but has no cur_state present. Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ fan | 5| 1| | | | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 5| 1| 0| 0| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690395 Title: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
