Fan not running at all on eeepc 1001pxd and 1001ha, system overheats.

Bug #985679 reported by N. Bruce Nelson
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The system fan used to come on and run continually if the computer was booted when warm on 12.04. A recent update now prevents the fan from running at all, even when the machine is booted warm, and the system overheats and shuts down.

The overheating will prevent the computer from using Ubuntu.

The previous behavior on 12.04 was annoying but acceptable, since the computer could be used when rebooted when warm, which would allow the fan to run.

Revision history for this message
N. Bruce Nelson (n-bruce-nelson) wrote :

Update: a new update has apparently returned the fan behavior to continuous running if the computer is rebooted when the temp sensor is hot. While far from ideal, this allows the computer to be usable.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in aptdaemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Xan (dxpublica) wrote :

In eeepc 1001ha I have this problem with 12.04. Before the upgrade to 12.04 all was fine. Now the computer warms until it reaches 88 F and shutdown. Please, solve this problem. How can I fix it temporally?

Thanks,
Xan.

summary: - Fan not running at all on eeepc 1001pxd, system overheats.
+ Fan not running at all on eeepc 1001pxd and 1001ha, system overheats.
Revision history for this message
Xan (dxpublica) wrote :

It only happens with battery.
If I leave battery, all is fine.

Revision history for this message
Xan (dxpublica) wrote :

Confirmed: if I leave battery, the bug is not present. Although I have a "burning" cpu, when I leave battery and I plug laptop to DC, all is fine.

Battery only or Battery with plug to DC "causes" a bug.

Anyone could confirm this with other models?

Can I attach some file for triagging this bug?

Thanks,
Xan.

PS: It's an annoying bug.

Revision history for this message
Xan (dxpublica) wrote :

I regret from above: today I have a reboot **without** battery. So the problem is present always, with and without battery.

Thanks,
Xan.

Revision history for this message
Xan (dxpublica) wrote :

Anything I could do for triaging this bug?

Thanks,

Revision history for this message
N. Bruce Nelson (n-bruce-nelson) wrote : Re: [Bug 985679] Re: Fan not running at all on eeepc 1001pxd and 1001ha, system overheats.

Xan, the behavior quickly reverted, so now if I reboot when the temperature
is elevated, the fan will come on and run continually. I monitor the temp,
and can control the processor speed with this program:

eee-control-tray is a utility for controlling Eee PC hardware, hotkeys and
more through eee-control-daemon.

Netbook Model: ASUSTeK Computer INC. AUTODETECT
eee-control-daemon version: 0.9.6
which can be found at:
http://launchpad.net/eee-control/

I don't know how else to assist. I think that there are developers that
are aware of this problem.

I hope this helps.

Bruce

On Mon, Jul 9, 2012 at 10:19 AM, Xan <email address hidden> wrote:

> Anything I could do for triaging this bug?
>
> Thanks,
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/985679
>
> Title:
> Fan not running at all on eeepc 1001pxd and 1001ha, system overheats.
>
> Status in “aptdaemon” package in Ubuntu:
> Confirmed
>
> Bug description:
> The system fan used to come on and run continually if the computer was
> booted when warm on 12.04. A recent update now prevents the fan from
> running at all, even when the machine is booted warm, and the system
> overheats and shuts down.
>
> The overheating will prevent the computer from using Ubuntu.
>
> The previous behavior on 12.04 was annoying but acceptable, since the
> computer could be used when rebooted when warm, which would allow the
> fan to run.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/985679/+subscriptions
>

--
N. Bruce Nelson
Judith L. Nelson
Alameda, California
http://brucescommentaria.blogspot.com/

Revision history for this message
Xan (dxpublica) wrote :

In my case all is equal. No solution I found.

Gary M (garym)
affects: aptdaemon (Ubuntu) → ubuntu
tags: added: needs-reassignment precise
Revision history for this message
shankao (shankao) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux (kernel).

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
tags: added: kernel-therm
removed: needs-reassignment
Revision history for this message
penalvch (penalvch) wrote :

N. Bruce Nelson, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

tags: added: needs-kernel-logs regression-potential
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.