Bug 555213 - Weird Sudden Fan Noise after kernel update
Summary: Weird Sudden Fan Noise after kernel update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-14 01:38 UTC by Hicham HAOUARI
Modified: 2010-12-04 00:26 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:26:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hicham HAOUARI 2010-01-14 01:38:12 UTC
Description of problem:
After the update from the release kernel (2.6.31.5-127), the fan suddenly started turning loudly (really very loudly that i have to shutoff the laptop ) and then stops all of a sudden. I believe that this happened between kernel-2.6.31.5 and kernel-2.6.31.6

Version-Release number of selected component (if applicable):
>2.6.31.5-127

How reproducible:
I can't reproduce it till now, but i have it on 2.6.32 too

Comment 1 Luke Hutchison 2010-02-26 04:14:32 UTC
I have the same problem on a Toshiba laptop with a Core 2 Duo CPU and Intel graphics.  The problem started around the same kernel version. Whenever the CPU is under load (e.g. restoring a browser session that crashed, so it has to open lots of tabs), the mouse gets really jumpy, and if it locks up for long enough then the whole system freezes and the fan goes nuts about five seconds later.  I have to run a Fedora-12 kernel on this Rawhide system just to make my machine usable.  (I have another desktop system with a quad Opteron CPU and nVidia graphics, also on Rawhide, and the mouse is not even jumpy on that machine.)

I don't know if it's the KMS part of the Intel graphics driver or the kernel scheduler causing this problem, but for me right now Fedora 13 is unusable with the 2.6.32 or 2.6.33 kernel, because my machine will lock up hard within five minutes of use every time I boot it.

Here's my lspci output:

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567V Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
01:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
05:0b.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
05:0b.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
05:0b.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
05:0b.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev ff)
05:0b.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
05:0b.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

Comment 2 Luke Hutchison 2010-04-27 15:53:46 UTC
I still get hard kernel lockups with a fresh reinstall of Fedora 13 Beta with all updates applied.  Kernel version is kernel-2.6.33.2-57.fc13.x86_64.

Lockups are a bit harder to trigger since kernel-2.6.33.1 or so, but if I leave my computer on overnight it's always locked-up in the morning, and it still frequently locks up under load.

I have to run kernel-2.6.31.5 or earlier on my machine just to avoid lockups.  Please can somebody look into this bug before Fedora 13 is released?  What info do you need to debug this?

Comment 3 Bug Zapper 2010-11-04 01:02:28 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-12-04 00:26:41 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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