fan only works when my acer 5315 is booted then stops

Bug #728733 reported by omondisingh
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: acpi

fan only works when my acer 5315 is booted then stops.i have a acer aspire 5315 laptop. My fan stopped working after installing ubuntu from vista. ive changed it for a new one and still the same problem. no dust aswel. please help

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: acpi 1.5-2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Thu Mar 3 22:18:12 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: acpi

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

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

Changed in acpi (Ubuntu):
status: New → Confirmed
Revision history for this message
Danny Edel (dannyedel) wrote :

Hello everyone,

a friend brought me an Aspire 5315 with an Ubuntu installed, which shows the exact same symptoms as the original poster ("It just turns off after a while and gets really hot, but the fan doesnt work"), so I can confirm this bug still exists in Ubuntu 14.04 LTS.

Since the bug has not been closed I post to this bug, I hope that's allright.

I have spent a lot of time hitting the words "aspire 5315 fan linux" into various search engines and have come up with the following information, which seem accurate:

(1) The Fan on this particular laptop is normally controlled by a (windows only) software called e-fan control.

(2) If the temperature rises too high, the mainboard/BIOS turns off power to save the system from heat death (this works even without the fan-control software running).

(3) A BIOS Update fixes this for some users, although BIOS updates can brick the system, so I have not tried one yet.

(4) There are other bug tickets on Launchpad, but they have been closed invalid:
#182929 #500090 #618209

(5) The bug ticket #579665 has been closed as fix released as of kernel 3.2.0-2-486.
Since the problem still occurs, this may be a regression. If someone can tell me how I should install that kernel version, I will try to verify that.

Now towards my own testing:

1. When you turn on the computer (BIOS splash screen or pressing buttons in BIOS), the fan starts running.
2. It stays on while you're in GRUB.
3. If you load memtest86 from grub, the fan stays on and turns itself up and down, the system ran multiple passes of memtest without issues.
4. While GRUB loads the linux kernel into memory, the fan stays on. (this can be most easily tested by booting from usb, since it only loads with usb1.1 speed and thus takes a loooong time)
5. When the linux kernel takes over, the fan turns off. (This is what makes me believe it is a linux-specific issue, while the board/BIOS might be allright). The system will continue working for a while, until it turns off (Mainboard's safety switch)

I was able to get through an ubuntu 14.04.2 amd64 installtion by not using an internet connection and clicking the default settings as fast as possible to get to the reboot before it went too hot.

With the system installed, I have done the following experiments:

If you boot with the parameter "acpi=off" the linux kernel panics within 1 second or so, but at least the fan stays on : )

If you boot with the parameters "acpi=off nolapic" or "acpi=off noapic" the system correctly boots up, fan works (!) and starts getting faster when a "stress --cpu 3" process gets the coretemp to 69°C.

Only downside of "acpi=off nolapic" is that wifi doesn't work at all when you boot the laptop like that (It works fine booted normally, so I suppose the card is allright)

It would be really nice if the computer could run its fan *and* the wifi card at the same time. If you can tell me anything I can try to help diagnose the problem, I'm happy to try it out. (although I'd like to avoid things that can brick it if it turns off at a bad time, like the bios update). Since the laptop has no user data on it yet, re-installing is no problem either.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 728733

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Colin Ian King (colin-king) wrote :

Just a thought, it may be worth installing thermald to see if this helps.

Revision history for this message
Danny Edel (dannyedel) wrote :

colin-king: I have not yet heard of thermald, will try it out after this comment.

First I have new (and to me, confusing) information.

To run apport-collect, i first booted it *without* "acpi=off nolapic" so it has wi-fi (but no fan). After it finished booting, I put it to suspend to let it cool down a bit (it already passed 70°C after loading X). When I woke it up, the fan worked!

Two reboots confirm this behaviour; If you load it up to X without the fan, press Power button (to get the menu which allows you to suspend), suspend it, and then wake it up, the fan starts and correctly scales with temperature.

A stress --cpu 3 gets it to 69-70 °C, and the fan gets really loud but it keeps the cpu at that temperature. If you CTRL-C the stress, it cools down to around 58°C within one second or so and then the fan slows down.

-----

Now to the apport-collect I was asked to run: It told me that it would be better to spawn a new bug report with apport-bug (maybe marking it as duplicate) instead of sending data to this one. Should I listen to its recommendation?

Revision history for this message
Danny Edel (dannyedel) wrote :

Regarding thermald: I have installed it and if I understand the manual correctly, it can only act with fans that are already registered in sysfs as cooling devices.

If I go to /sys/class/thermal I have two cooling_devices (the CPU and the LCD, no fans here). The CPU's cur_state affects throttling, while the LCD's controls brightness. If I write 90000 (90 °C) to thermal_zone0's emul_temp, the system becomes really slow (throttling at work), but the fan does not react (I assume it's controlled purely by BIOS because of the suspend/wake-up cycle).

So I believe the real issue here is that linux does not see the fan control and leaves the control to the BIOS (which is fine for me) after a wakeup, but still it stops the fan while starting the kernel (which sounds like a bug to me), apparently deactivating BIOS' own fancontrol routine. (Maybe it accidentally writes to the same register as Acer's fancontrol application, signaling the BIOS that fancontrol is now running, but this is pure speculation.)

Revision history for this message
Colin Ian King (colin-king) wrote :

thermald does also try to ensure the machine does not overheat via passive cooling too (e.g. cpu freq scaling etc), so I thought it may be useful to avoid the power-off overheating scenario.

It may be that once the kernel has booted it indicates to the firmware that the system is under ACPI control so the BIOS fan control turns off in favour for the OS control, which does not happen on Linux because we don't have the secret sauce of the windows driver to do this.

Revision history for this message
Danny Edel (dannyedel) wrote :

I've got some new observations on this that might help narrow down the problem.

(1) thermald
I've got thermald installed, and the default configuration seems to work *after* the standby/wakeup cycle. Before the machine goes into standby, the file cat /sys/class/thermal/thermal_zone0/temp constantly reads 40000 (40 °C), even when the processor is already way beyond 70°C (as monitored by lm-sensors' coretemp) so thermald doesn't trigger the CPU slowdown.

After the standby/wakeup cycle, this temperature reading follows the coretemp, and thermald acts correctly.

It seems that whatever the secret windows sauce does, also happens after a wakeup from standby. So maybe there's something I can do to automate this behaviour during startup of the machine, not requiring human intervention to enter "stable operation zone".

(2) apport-collect
When I run apport-collect and ignore its warning that submitting to the current bug is not recommended, the window it gives me lists as the first line "Package: linux (not installed)". I think it will not have collected all the info, but I'll send whatever it picks up and set the bug status to confirmed; maybe someone can help me operate it correctly or tell me to spawn a new bug with the apport-bug.

tags: added: apport-collected trusty
Revision history for this message
Danny Edel (dannyedel) wrote : apport information

ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dannyedel 1550 F.... pulseaudio
CurrentDesktop: Unity
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
 dmesg: write failed: Broken pipe
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2001-01-02 (5294 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64+mac (20150218.1)
MachineType: Acer Aspire 5315
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic root=UUID=36a742e5-ee21-43a3-b931-ce78a8734631 ro verbose
ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
Tags: trusty
Uname: Linux 3.16.0-41-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 09/27/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.18
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.18
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.18
dmi.modalias: dmi:bvnAcer:bvrV1.18:bd09/27/2007:svnAcer:pnAspire5315:pvrV1.18:rvnAcer:rnAcadia:rvrV1.18:cvnAcer:ct1:cvrV1.18:
dmi.product.name: Aspire 5315
dmi.product.version: V1.18
dmi.sys.vendor: Acer

Revision history for this message
Danny Edel (dannyedel) wrote : AlsaInfo.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : CRDA.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : HookError_source_linux.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : IwConfig.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : Lspci.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : Lsusb.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : ProcEnviron.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : ProcModules.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : PulseList.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : RfKill.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : UdevDb.txt

apport information

Revision history for this message
Danny Edel (dannyedel) wrote : UdevLog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

omondisingh, thank you for reporting this bug to Ubuntu. Maverick reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue on a supported release?

no longer affects: acpi (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
penalvch (penalvch) wrote :

Danny Edel, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Revision history for this message
Danny Edel (dannyedel) wrote :

Christopher: I have created the new ticket #1471530 and subscribed you.

I don't know how to correctly link the tickets (or whether I even should do that), so it would be nice if you or someone else would handle that.

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.