Bug 1035043 - Fan goes to maximum speed on Toshiba Portege R830-1C8
Summary: Fan goes to maximum speed on Toshiba Portege R830-1C8
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 23:09 UTC by Thomas Kashofer
Modified: 2015-01-07 13:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-07 13:34:33 UTC
Type: Bug


Attachments (Terms of Use)
lspci output / dmidecode output / /proc/cpuinfo (5.82 KB, application/gzip)
2013-11-26 23:09 UTC, Thomas Kashofer
no flags Details
dmesg output / lsmod output (17.01 KB, application/gzip)
2013-12-03 00:11 UTC, Thomas Kashofer
no flags Details

Description Thomas Kashofer 2013-11-26 23:09:17 UTC
Created attachment 829525 [details]
lspci output / dmidecode output / /proc/cpuinfo

Description of problem:
Right from the beginning, after I installed Fedora 19 x86_64 (Kubuntu) from scratch, the fan of my laptop went crazy.
During some point of the startup process (somewhere after the blue Fedora logo appears in the middle of the screen, if that helps) the fan just goes up to maximum speed AND STAYS THERE.
I tested it and even after a complete day it stays at maximum speed (really annoying also for the people around you). This has nothing to do with components overheating, since KSensors tells me that CPUs and board are comfortably within the middle of the green area.

Additional Information:
This did not happen with a 32bit Fedora 17 (Kubuntu) I was running before on the identical hardware.

Version-Release number of selected component (if applicable):
3.11.8-200
but it also existed with older kernels in Fedora 19

How reproducible:
Always, no exception.

Steps to Reproduce:
1. Just do a complete boot up (this means no recovery from "suspend to RAM" or "suspend to disk") of the machine.

Actual results:
Fan runs at maximum speed and does not slow down.

Expected results:
Speed up at the end of the boot process, then slow down again.

Additional info:
The workaround that I found goes like this:
1. Boot up the machine --> fan at maximum
2. Put it back to sleep with "Suspend to RAM"
3. Hit powerON again --> fan at low
Maybe that helps to track the down the settings that make the fan go crazy.

Comment 1 Michele Baldessari 2013-11-27 21:25:28 UTC
Hi Thomas,

does it happen if you boot with 'acpi=off'. Can you also attach dmesg output and lsmod output to this bz.

thanks,
Michele

Comment 2 Thomas Kashofer 2013-12-03 00:10:15 UTC
Hi Michelle,

thanks for the quick reply.
Yes it also happens if I boot with "acpi=off". I have attached the outputs from dmesg and lsmod as requested.

If you need anything else, just let me know.

Bye,
Thomas

Comment 3 Thomas Kashofer 2013-12-03 00:11:08 UTC
Created attachment 831843 [details]
dmesg output / lsmod output

Comment 4 Thomas Kashofer 2013-12-03 00:13:26 UTC
Additiona information:
Yesterday I upgraded to kernel 3.11.9-200, the issue is still the same.

Comment 5 Thomas Kashofer 2013-12-25 08:17:36 UTC
Updated to kernel 3.11.10, the issue is still the same.

Comment 6 Thomas Kashofer 2013-12-25 08:18:13 UTC
Updated to kernel 3.12.5, the issue is still the same.

Comment 7 Michele Baldessari 2014-01-04 13:30:50 UTC
Potentially related: https://bugzilla.redhat.com/show_bug.cgi?id=714278

Comment 8 Thomas Kashofer 2014-01-18 07:14:38 UTC
Updated to kernel 3.12.6, the issue is still the same.

Comment 9 Thomas Kashofer 2014-01-18 07:14:55 UTC
Updated to kernel 3.12.7, the issue is still the same.

Comment 10 Thomas Kashofer 2014-01-18 07:19:40 UTC
Just in case you want to compare my sensor values to the ones from bug  https://bugzilla.redhat.com/show_bug.cgi?id=714278

Those are the values without(!) the fan speeding at full throttle.

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +56.0°C  (crit = +102.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +57.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:         +56.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:         +54.0°C  (high = +86.0°C, crit = +100.0°C)

pkg-temp-0-virtual-0
Adapter: Virtual device
temp1:        +56.0°C

Comment 11 Thomas Kashofer 2014-02-18 07:52:12 UTC
Updated to kernel 3.12.8, the issue is still the same.

Comment 12 Thomas Kashofer 2014-02-18 07:52:30 UTC
Updated to kernel 3.12.9, the issue is still the same.

Comment 13 Thomas Kashofer 2014-02-18 08:27:39 UTC
Updated to kernel 3.12.11, the issue is still the same.

Comment 14 Thomas Kashofer 2014-03-04 22:51:29 UTC
Updated to kernel 3.13.5, the issue is still the same.

Comment 15 Justin M. Forbes 2014-03-10 14:48:59 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.13.5-100.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 16 Justin M. Forbes 2014-05-21 19:31:28 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.14.4-100.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 17 Justin M. Forbes 2014-06-23 14:41:39 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 18 Thomas Kashofer 2014-08-23 03:46:33 UTC
Updated to kernel 3.14.8, the issue is still the same.

Comment 19 Thomas Kashofer 2014-08-23 03:47:02 UTC
Updated to kernel 3.14.15, the issue is still the same.

Comment 20 Thomas Kashofer 2014-08-23 03:47:42 UTC
Updated to kernel 3.14.17, the issue is still the same.

Comment 21 Thomas Kashofer 2014-08-23 03:48:18 UTC
Please let me know, if I can provide any more data to help resolve that issue.

Comment 22 Thomas Kashofer 2015-01-07 13:34:33 UTC
I switched to a new laptop (DELL) so I do not have this issue anymore.
And in the meantime FC19 has reached EOL.
Issue can be closed.


Note You need to log in before you can comment on or make changes to this bug.