Fan malfunction on Lenovo 3000 N100.

[Laserulo]

The laptop cooling fan *sometimes* switches on at startup even though the machine is cold. It then stays on until the machine is closed down. It seems to be a random problem only happening intermittently.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-generic 2.6.32-25.45
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hugh 1402 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xb0000000 irq 22'
   Mixer name : 'Analog Devices AD1986A'
   Components : 'HDA:11d41986,17aa2066,00100500 HDA:11c11040,11c10001,00100200'
   Controls : 20
   Simple ctrls : 11
Date: Fri Oct 29 17:10:38 2010
HibernationDevice: RESUME=UUID=e8487945-2cfc-4dab-b050-87c0327dde08
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: LENOVO 07686VG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=UUID=6a43dd0b-2f9f-46bb-86c3-d2a06853cdf5 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
SourcePackage: linux
dmi.bios.date: 08/04/06
dmi.bios.vendor: LENOVO
dmi.bios.version: 61ET21WW
dmi.board.name: MPAD-MSAE Customer Reference Boards
dmi.board.vendor: LENOVO
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr61ET21WW:bd08/04/06:svnLENOVO:pn07686VG:pvr3000N100:rvnLENOVO:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 07686VG
dmi.product.version: 3000 N100
dmi.sys.vendor: LENOVO

[Fabio Marconi (fabiomarconi)]

I assign this report to lm-sensors-3 as it is related to fancontrol.

[Jeremy Kerr (jk-ozlabs)]

The logs from the original report - were they created when the machine booted correctly, or was the fan (incorrectly) switched on during this boot?

[Laserulo (hugh-reid2)]

They were when the machine booted correctly. The fault is intermittent. I cannot make it happen. Which outputs do you want and I'll send them when it next occurs?

[Jeremy Kerr (jk-ozlabs)]

Laserulo: the output of the 'dmesg' command (when working and non-working) would be most helpful. Thanks!

[Laserulo (hugh-reid2)]

ok Jeremy, output attached as laserulodmesg.txt ... this is the normally functioning output.

[Laserulo (hugh-reid2)]

ok Jeremy, output attached as laserulodmesg.txt ... this is the normally functioning output.

[Laserulo (hugh-reid2)]

Jeremiy output attached from dmesg with fan running from switch-on as laserulodmesg3112010.txt

[Jeremy Kerr (jk-ozlabs)]

Hi Laserulo,

Looking through your logs, I see one important difference:

From the non-working dmesg log:

  ACPI: Thermal Zone [TZ00] (87 C)

From the working dmesg log:

  ACPI: Thermal Zone [TZ00] (12 C)

- looks like the working boot reported starting at 12°C, but the non-working boot started at 87°C; I'm not surprised that the fan was running in the latter case.

Would these numbers be correct? was the non-working boot from a previously running system, and was the working boot from a "cold start"? And would that have been when it was 12°C where you are?

[Laserulo (hugh-reid2)]

Hi Jeremy,

Both cases were from a cold boot. 87°C sounds very high and it can't be right in any case.
Were in Scotland so 12°C could be right. We do have central heating but it doesn't switch on until around half an hour before I would normally switch on the machine, so it is feasible that it hadn't reached room temperature by that time.

Cheers

Hugh (Laserulo)

[Jeremy Kerr (jk-ozlabs)]

Hi Hugh,

when you mean "cold boot", was the machine off for some time beforehand? I wouldn't be surprised if the CPU temperature was around 87°C after doing some computational work, but this would be very strange if the machine had been off before booting.

If your machine was indeed off before this non-working boot, it would seem that ACPI is reporting incorrect temperatures.

Also, your logs show that the AC adaptor was connected for the non-working boot, but not the working one. Would this be correct?

Cheers,

Jeremy

[Laserulo (hugh-reid2)]

Hi Jeremy,

The machine was switched off overnight in both cases. With regard to the ac adapter I actually can't remember. I didn't check that, but normally the adaptor would be on in both cases.

It haven't notice a correlation between the adapter being switched off for that particular working boot up.

I'll will keep an eye on this, but it seems to me that the machine is incorrectly reading its state. Incidentally whenever I get a non-working boot-up only have to reboot and the fan works correctly.

Rgards
hguh

[Colin Ian King (colin-king)]

My experience with Lenovo Laptops (I've got a 3000 N200) is that the fan control is performed by the BIOS. Typically there are periodic System Management Mode interrupts into the BIOS and the fan is controlled by this. So, the issue may be that there is a sensor fault, or the BIOS is not doing the right thing.

My Lenovo was playing up after nearly 3 years of use and cleaning the dust out of the fan grill outlet solved my sporadic fan overheating issues. http://smackerelofopinion.blogspot.com/2010/09/hot-laptop.html

Secondly, I checked the Lenovo website and it appears there are some newer BIOS images available, so maybe these contain updates that *may* be relevant.

[Jeremy Foshee (jeremyfoshee)]

Hi Laserulo,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Laserulo (hugh-reid2)]

Hi Jeremy,

This is far too complicated for someone who does not have the time to decipher
and understand terminology such as "upstream" and "mainline". It was for this
reason that I took out a contract with Canonical, so that they would deal with
the technical stuff for me.

If you have no objection I will pass on your message to them to ask for their
assistance in executing it.

Thank you for taking the time to send the message.

Regards

Hugh

________________________________
From: Jeremy Foshee <email address hidden>
To: <email address hidden>
Sent: Wed, 1 December, 2010 18:19:43
Subject: [Bug 668413] Re: Fan malfunction on Lenovo 3000 N100.

Hi Laserulo,

If you could also please test the latest upstream kernel available that would be
great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the 'needs-upstream-testing' tag. This can be
done by clicking on the yellow pencil icon next to the tag located at the bottom
of the bug description and deleting the 'needs-upstream-testing' text. Please
let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: kj-triage

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

--
Fan malfunction on Lenovo 3000 N100.
https://bugs.launchpad.net/bugs/668413
You received this bug notification because you are a direct subscriber
of the bug.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]