only critical trip point 104C

Bug #130907 reported by rax_m
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Hi.
I've got a Toshiba Satellite P100. I've been running Ubuntu Feisty for a while now (couple of months?) and it seems fine, except for the acpi temp. On investigation, I found that the /proc/acpi/fan directory is empty and that the /proc/acpi/thermal_zone/THRM/trip_points contain the following:
critical (S5): 104 C
passive: 104 C: tc1=2 tc2=3 tsp=40 devices=0xdf8559c8

To me that seems way too high, and may explain why my laptop got up to 90C the other day when playing a game. Most days it will get to about 75 if I'm doing something intensive, but the fans normally kick in. Since, I've been paying much more attention and noticed that some days the fan will kick in quite regularly, and other days not. I always power down the laptop (i.e. do not suspend or hibernate).

NB. I have compile my own DSDT for this laptop in order to get sound working.

Thanks
Rax

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thanks for submitting this report.

Could you please check if this issue is still occurring in the newest hardy release?

Thanks

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
rax_m (rax-m) wrote : Re: [Bug 130907] Re: only critical trip point 104C

Hi. Unfortunately I'm running Gutsy at the moment and can't afford to upgrade to an unstable release. Once I get a copy of Hardy stable I will test.

Thanks
Rax

----- Original Message ----
From: Ralph Janke <email address hidden>
To: <email address hidden>
Sent: Thursday, 6 March, 2008 6:49:57 PM
Subject: [Bug 130907] Re: only critical trip point 104C

Thanks for submitting this report.

Could you please check if this issue is still occurring in the newest
hardy release?

Thanks

** Changed in: linux-source-2.6.20 (Ubuntu)
       Status: New => Incomplete

--
only critical trip point 104C
https://bugs.launchpad.net/bugs/130907
You received this bug notification because you are a direct subscriber
of the bug.

      __________________________________________________________
Sent from Yahoo! Mail.
The World's Favourite Email http://uk.docs.yahoo.com/nowyoucan.html

Revision history for this message
Ralph Janke (txwikinger) wrote :

Do you run the newest kernel in gutsy? Does the problem still exist on it?

Thank

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.