AMILO Pro V2030 fan control only working after suspend

Bug #1153106 reported by Rüdiger Kupper
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I see strange behavior of fan control on a Fujitsu Siemens AMILO Pro V2030 laptop, running Lubuntu 12.10:
I boot, and the cooling fan runs at high speed and never slows down. However, when I hibernate, the fan suddenly slows down shortly before the laptop turns off. After resume, fan control works perfectly: Fan changes speed and turns on and of depending on temperature.
Somehow, hibernation *fixes* fan control. This is in contrast to other reports, which mostly report that fan control breaks after hibernation.
I tried to find the place where the magic happens, reading through the pm-action script. Finally, I found that it must happen in the kernel, as simply doing
# echo -n disk > /sys/power/state
is enough to trigger the effect.

So: what is it in the hibernation process that fixes fan control on the AMILO Pro V2030?

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-25-generic 3.5.0-25.39
ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ruediger 1667 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Sun Mar 10 02:29:20 2013
HibernationDevice: RESUME=UUID=e0cbaf3c-978b-4bc1-b44c-9c3e4887a422
InstallationDate: Installed on 2013-02-12 (25 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
Lsusb:
 Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS AMILO PRO V2030
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=85560b21-2e5a-4dbe-9769-4a65850ed2a6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-25-generic N/A
 linux-backports-modules-3.5.0-25-generic N/A
 linux-firmware 1.95
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2005
dmi.bios.vendor: FUJITSU SIEMENS
dmi.bios.version: 1.0G-2309-8A20
dmi.board.name: AMILO PRO V2030
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 0.5I
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: A2030
dmi.modalias: dmi:bvnFUJITSUSIEMENS:bvr1.0G-2309-8A20:bd09/02/2005:svnFUJITSUSIEMENS:pnAMILOPROV2030:pvr20:rvnFUJITSUSIEMENS:rnAMILOPROV2030:rvr0.5I:cvnFUJITSUSIEMENS:ct10:cvrA2030:
dmi.product.name: AMILO PRO V2030
dmi.product.version: 20
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Rüdiger Kupper (ruediger.kupper) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Rüdiger Kupper (ruediger.kupper) wrote :

The same holds true for suspend, by the way. (But suspend is broken for another reason on the AMILO Pro V2030, so I don't use it.)

Revision history for this message
Rüdiger Kupper (ruediger.kupper) wrote :

The problem is still present with the latest mainline kernel (3.9.0-030900rc1-generic).

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-bug-exists-upstream raring
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Rüdiger Kupper, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update is available for your BIOS (1.0I). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-1.0i needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Rüdiger Kupper (ruediger.kupper) wrote :

Christopher,

thank you very much! I'd really like to test the BIOS upgrade! However, silly as it sounds, the AMILO Pro laptop in question completely broke down three days ago. It will not power on any more. (It is not the battery, it does not power on with battery removed, either. Probably a hardware failure in the mainboard's power supply. I know of other AMILOs that suffered this failure.)

When I have the time I will see if I can fix the power supply. If I manage, I will certainly come to you. Until then, we're out of luck :-(.
However, since I seem to have been the only one with interest in this problem (no one else subscribed to this bug), there may be no need to further pursue the issue.

I'm a little sad that a machine that served me well for 10 years or more has simply broken. I appreciate your help very much! But unless I manage to fix my AMILO, this ticket may be closed.

My regards,
Rüdiger

Revision history for this message
penalvch (penalvch) wrote :

Rüdiger Kupper, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153106/comments/7 regarding your hardware is not working anymore. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Rüdiger Kupper (ruediger.kupper) wrote :

Thanks. The description of state "invalid" ("Not a bug. May be a support request or spam.") just did not seem to fit.

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.