MacBook Air running Ubuntu 12.04 Beta 2 overheats

[shuhart]

After about a 30 minutes of use (web browsing, nothing special, no flash) mba 4,2 begins to overheat. Overheating begins only if the external power cable plugged in.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ivan 1976 F.... pulseaudio
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=66fd03ea-b71e-4d11-9dfb-67b5da12a4bb
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac (20120328)
MachineType: Apple Inc. MacBookAir4,2
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=57f5664f-a7e0-49ba-8e51-4a791ed5dac4 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
SourcePackage: linux
StagingDrivers: mei
Tags: precise staging precise staging
Uname: Linux 3.2.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/14/2011
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA41.88Z.0077.B0E.1110141154
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-742912EFDBEE19B3
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir4,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-742912EFDBEE19B3
dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0E.1110141154:bd10/14/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
dmi.product.name: MacBookAir4,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/973930/+editstatus and add the package name in the text box next to the word Package.

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

[Fabio Marconi (fabiomarconi)]

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.

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.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

[Brad Figg (brad-figg)]

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

apport-collect 973930

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.

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

apport information

[shuhart (shuhart75)]

Clean Ubuntu 12.04 install, no upgrade. Overheating begins only if the external power cable plugged in. And it seems less critical after today's system update. I don't know, may be I should try to reinstall the system?

[Tommy_CZ (t-kijas)]

Same here, my MacBook Air 4,2 is noisy like a vacuum cleaner with ubuntu, after some time. I think it started when I had started to play some songs from player.

So I can confirm it.

[Tommy_CZ (t-kijas)]

You (shuhart) forgot to change the status to confirmed, as comment #4 suggests, so I did it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/

[Tommy_CZ (t-kijas)]

The bug still exists. Even when using latest 3.4.xx kernel. Bad situation.

[Joseph Salisbury (jsalisbury)]

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 at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

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

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

[Tommy_CZ (t-kijas)]

I will report it in bugzilla.kernel.org, although I never did it before.)
I must say it hasn't started after an upgrade, but the reporter of this bug had been using Ubuntu on Macbook Air more to the past than me so probably he can provide more information.
I must say that overheating is not brutal in my case, but the Macbook is kinda warm and that is a CHANGE -> with OSX it wasn't even warm. (of course when I enable e.g. HoN the Macbook is very hot, but so it was with OSX).
The problem is in another place - it is not disturbing, but I think it is connected to it's lowered battery life in Ubuntu with comparison in OSX. Something takes more energy than it should and so laptop is WARMER and the battery life is LOWER.

[SethWoodworth (seth-woodworth)]

Have you installed macfanctld? I am using the 13" model and I do not get overheating.

[shuhart (shuhart75)]

No, I haven't. I presume Ubuntu should work perfectly out of the box. Otherwise it's a bug :-) Macfanctld is a workaround, isn't it?

[Tommy_CZ (t-kijas)]

I have no problem with Ubuntu 12.04/13.04, do you?

[penalvch (penalvch)]

shuhart, 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>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) 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.12

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.

[Launchpad Janitor (janitor)]

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