Sudden reboot happens randomly on MacBook Pro 2,2

Bug #572162 reported by Moræus
58
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Randomly the systems freezes for about 1 or 2 seconds, and the just reboots. I can hear the fans starting to go faster so I think the CPU must be running at a 100% the few seconds before reboot.
I can not find any way of triggering this fault, it is just as likely to happen in almost idle as in heavy load.
Below is logs from the the minutes before reboot. The reboot happened about 10:48:30

/var/log/kern.log:
Apr 30 10:17:39 macix kernel: [ 66.252661] wlan0: deauthenticating from 00:1e:e5:45:bf:a3 by local choice (reason=3)
Apr 30 10:21:32 macix kernel: [ 300.050054] Machine check events logged
Apr 30 10:27:58 macix kernel: [ 685.284026] ACPI: EC: GPE storm detected, transactions will use polling mode
Apr 30 10:40:48 macix kernel: imklog 4.2.0, log source = /proc/kmsg started.
Apr 30 10:40:48 macix kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 30 10:40:48 macix kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 30 10:40:48 macix kernel: [ 0.000000] Linux version 2.6.32-22-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 (Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2)
Apr 30 10:40:48 macix kernel: [ 0.000000] Command line: root=UUID=e24a230e-9218-4592-859b-2b8ef474cf5b ro quiet splash crashkernel=384M-2G:64M,2G-:128M
Apr 30 10:40:48 macix kerApr 30 10:21:32 macix kernel: [ 300.050054] Machine check events logged

/var/log/syslog:
Apr 30 10:21:53 macix ntpd[2064]: sendto(91.189.94.4) (fd=23): Invalid argument
Apr 30 10:22:34 macix ntpd[2064]: Listening on interface #8 br0, 10.0.0.144#123 Enabled
Apr 30 10:22:34 macix ntpd[2064]: Deleting interface #3 wlan0, fe80::21b:63ff:fe04:bb74#123, interface stats: received=0, sent=0, dropped=0, active_time=301 secs
Apr 30 10:22:34 macix ntpd[2064]: Deleting interface #6 br0, 10.0.0.50#123, interface stats: received=0, sent=0, dropped=0, active_time=301 secs
Apr 30 10:22:34 macix ntpd[2064]: Deleting interface #7 wlan0, 10.10.0.225#123, interface stats: received=1, sent=1, dropped=4, active_time=301 secs
Apr 30 10:22:34 macix ntpd[2064]: new interface(s) found: waking up resolver
Apr 30 10:22:42 macix NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Apr 30 10:27:11 macix ntpd[2064]: synchronized to 91.189.94.4, stratum 2
Apr 30 10:27:11 macix ntpd[2064]: time reset -0.129861 s
Apr 30 10:27:11 macix ntpd[2064]: kernel time sync status change 2001
Apr 30 10:27:58 macix kernel: [ 685.284026] ACPI: EC: GPE storm detected, transactions will use polling mode
Apr 30 10:33:42 macix ntpd[2064]: synchronized to 91.189.94.4, stratum 2
Apr 30 10:40:48 macix kernel: imklog 4.2.0, log source = /proc/kmsg started.
Apr 30 10:40:48 macix rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1113" x-info="http://www.rsyslog.com"] (re)start
Apr 30 10:40:48 macix rsyslogd: rsyslogd's groupid changed to 102
Apr 30 10:40:48 macix rsyslogd: rsyslogd's userid changed to 101
Apr 30 10:40:48 macix rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Apr 30 10:40:48 macix kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 30 10:40:48 macix kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 30 10:40:48 macix kernel: [ 0.000000] Linux version 2.6.32-22-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 (Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2)
Apr 30 10:40:48 macix kernel: [ 0.000000] Command line: root=UUID=e24a230e-9218-4592-859b-2b8ef474cf5b ro quiet splash crashkernel=384M-2G:64M,2G-:128M
Apr 30 10:40:48 macix kernel: [ 0.000000] KERNEL supported cpus:nel: [ 0.000000] KERNEL supported cpus:

uname -a:
Linux macix 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux

Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: moraus 2119 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x90400000 irq 22'
   Mixer name : 'SigmaTel STAC9221 A1'
   Components : 'HDA:83847680,106b1e00,00103401'
   Controls : 20
   Simple ctrls : 12
Date: Fri Apr 30 11:04:34 2010
Frequency: Once a day.
HibernationDevice: RESUME=UUID=61f800d1-739b-4900-a0fb-0b68c6753090
MachineType: Apple Computer, Inc. MacBookPro2,2
ProcCmdLine: root=UUID=e24a230e-9218-4592-859b-2b8ef474cf5b ro quiet splash crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 08/13/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP22.88Z.00A5.B07.0708131242
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42187C8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42187C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP22.88Z.00A5.B07.0708131242:bd08/13/07:svnAppleComputer,Inc.:pnMacBookPro2,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42187C8:rvrPVT:cvnAppleInc.:ct8:cvrMac-F42187C8:
dmi.product.name: MacBookPro2,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

Revision history for this message
Moræus (moraus) wrote :
Revision history for this message
Kevin Mauser (kmauser) wrote :

I'm on a MacBook Pro 2,2 as well:

2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux

I have a similar issue where I'll have a sudden freeze for a few seconds and then a reboot. This happened in the 32-bit version as well. This happens at least once a day. I ran Karmic for a while and it didn't seem to happen. Any help or advice is appreciated.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Moraus,

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
Revision history for this message
Kevin Mauser (kmauser) wrote :

Jeremy,
I'm running the latest upstream kernel (2.6.34-999-generic #201005011008 SMP Sat May 1 09:09:57 UTC 2010 x86_64 GNU/Linux) and I'm still having this trouble. It just happened about 5 minutes ago at approximately 21:11. I don't know exactly what you need to see in terms of logs and I don't really see anything that stands out. Nevertheless, I've attached the messages log from 20:49 up until the computer froze and then did a reboot. Let me know what else you want or need to see and I'll attach them.

Revision history for this message
Moræus (moraus) wrote :

As this bug is becoming a real problem, where files get damaged and data lost, I'm more than average interested in hunting down this issue. If anyone has an idea where to start, please let me know.
I've started to remove modules such as ath9k, bluetooth, aes.* etc. to see if there is a connection.

Revision history for this message
Moræus (moraus) wrote :

After disable of KMS this problems seems to go away.

Revision history for this message
Kevin Mauser (kmauser) wrote :

I disabled KMS but the problem still occurs. The crashes cause data loss occasionally so getting this bug fixed would be very nice, indeed. This doesn't happen on the two other PC machines I've installed Lucid on so it must be something specific to Macs. It may be related to overheating and/or the video card. I have ATI graphics. What do you have?

After disabling KMS I did see some other messages in the logs that might hint at this problem, but I'm not able to post them right now. I'll look at it again and do it soon though.

Revision history for this message
Frank (spam2-fdoelitzscher) wrote :

Same problem here.
Laptop freezes for 1-4 seconds and the reboots.
Mostly when using openoffice impress, kile or okular.

Hardware: MacbookPro 2.2

Revision history for this message
white_gecko (natanaela) wrote :

So just to let you know, I have the same Problem on my MacBook Pro 2,2.

uname: Linux mbp 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

I also would like to help with more logs, but can't find messages from the minutes before the crash, how could I provide more information?

Revision history for this message
James Younger (james-grondle) wrote :

This bug affects my macbook pro 2,2 also, and has since I first installed Lucid. Never happened in Karmic.

System freezes for a few seconds, then reboots

uanmeL Linux james-macbuntu 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

Revision history for this message
Kevin Mauser (kmauser) wrote :

As Moraus said, after disabling KMS the problem goes away. You can disable KMS by adding "nomodest" in your grub (/etc/default/grub) file like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

It'll make the boot splash screen not look at nice, but at least your computer won't randomly crash. From my understanding, it seems that the reason this doesn't happen with Karmic is because KMS (Kernel Mode Setting) was added into Lucid and wasn't in Karmic. You might want to check out this link for more information: https://wiki.ubuntu.com/X/KernelModeSetting

This isn't really a solution - it's a temporary workaround. It'd be nice if someone would like into this. I haven't been able to find anything useful in the log files though.

Revision history for this message
Kevin Mauser (kmauser) wrote :

I had a typo above: "nomodest" should be "nomodeset" as in the grub file line.

Revision history for this message
white_gecko (natanaela) wrote :

@Kevin Mauser: Thank you this seams to work, I didn't experience a reboot since I boot with "nomodeset".

Revision history for this message
Pierre-Yves Langlois (pyl-regis) wrote :

Hi...

I'm running Lucid 64bits on a macbook 2.2. I added the "nomodeset" in my /etc/default/grub file as explained by Kevin Mauser but it still reboot randomly... :(

2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 05:14:15 UTC 2010 x86_64 GNU/Linux

Revision history for this message
Kevin Mauser (kmauser) wrote :

@Pierre: Did you run "sudo update-grub" after editing your grub file?

Revision history for this message
Pierre-Yves Langlois (pyl-regis) wrote :

:) Sorry for that, you are absolutely right... I ran the "sudo update-grub" and now it's working.

Thank you!

Revision history for this message
Marco Papa (mpapa) wrote :

For solving the "Hugly" splash screen and the slowdown at startup, it is enough to add another parameter in the grub config file:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset vga=803"

followed, of course, by "update-grub". In this way the resolution is manually set and the splash screen is better and the slowdown (that, I think, is related to the slow resolution/splash screen) is solved.

Revision history for this message
Leo (leorolla) wrote :

I found this report searching for "synchronized to 91.189.94.4, stratum 2" on google.

My laptop totally froze a few minutes after this entry on the syslog, CPU went high and Fans went crazy.

It only happened to me twice, both times last week, exactly when I booted Windows XP. ntpd has pulled the system clock back by -7201 seconds (the two hours between me and UTC).

So, maybe these questions help understand the issue:

Did you boot another OS before it happened, like me?
Is your time zone is ahead of London, like mine?
Are you able to reproduce this crash again?

Revision history for this message
Adi Sieker (adsworth) wrote :

#612597 is a duplicate of this and he solved it using upstream kernel 2.6.35-12.

tags: removed: needs-upstream-testing
Revision history for this message
Simon Déziel (sdeziel) wrote :

@Adi, thanks for pointing me to this bug.

@all
In my tests to find a fix for this issue I have tested various kernels for the Kernel PPA (https://launchpad.net/~kernel-ppa/+archive/ppa). Here are my findings :

Kernels that I have tested and are affected :
- 2.6.32 (All official Lucid kernels up to linux-image-2.6.32-24-generic 2.6.32-24.42)
- 2.6.33 (linux-image-2.6.33-02063301-generic_2.6.33-02063301_amd64.deb)
- 2.6.34 (linux-image-2.6.34-020634-generic_2.6.34-020634_amd64.deb)

Kernels that fix the bug (don't know which commit as I haven't done a git bisect yet) :
- 2.6.35 (Maverick kernels backported to Lucid from 2.6.35-12 to 2.6.35-19)

I will test latest the Lucid kernel in -proposed because it includes some fixes for the radeon driver :

  * drm/radeon/kms: reset ddc_bus in object header parsing
    - LP: #607824
  * drm/radeon/kms/atom: fix typo in LVDS panel info parsing
    - LP: #607824
  * drm/radeon: r100/r200 ums: block ability for userspace app to trash 0
    page and beyond
    - LP: #607824
  * drm/radeon: fix the r100/r200 ums block 0 page fix
    - LP: #607824

I will report my results here. I will also give a try to "nomodeset". Thanks everyone for the hint.

Revision history for this message
white_gecko (natanaela) wrote :

I just wanted to get a proper vga= value for my MacBook Pro 2,2 because the value of @Marco Papa didn't produce a nice output for me, so I've tried to run "sudo hwinfo --framebuffer" as described in [1] but my complete computer hung, when it reaches "> bios.4.2: node info". Maybe this is the same reason, why the devices suddenly reboot if "nomodeset" is not set. It also worked a second time, so I hope it is reproducible.

[1] http://wiki.ubuntuusers.de/Konsolen-Aufl%C3%B6sung#fuer-vesafb (german)

Revision history for this message
Simon Déziel (sdeziel) wrote :

The official Lucid kernel in -proposed linux-image-2.6.32-25-generic (2.6.32-25.43) is still affected by sudden reboots.
I am now testing this same kernel with the "nomodeset" and will report if it's a valid workaround.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - Sudden reboot happens randomly
+ Sudden reboot happens randomly on MacBook Pro 2,2
Revision history for this message
Adi Sieker (adsworth) wrote :

Just to confirm other people. I've been running with nomodeset for the last 5 days and everything is fine.
I'm running 2.6.32-24-generic-pae

Revision history for this message
Adi Sieker (adsworth) wrote :

I had one lock up yesterday. This is my first lockup since running with nomodeset. That's 1 lockup in 12 days. Instead of 1 lockup per day.

Revision history for this message
white_gecko (natanaela) wrote :

I had my first reboot since setting nomodeset today.
But in the last days I had some power-offs I think because of overheating.
Some people say that the fan turns high right before the reboot, could the reboot maybe have to do something with overheating?

Revision history for this message
white_gecko (natanaela) wrote :

After watching the temperature I can say that I havn't experienced a sudden shutdown below 100°C, but my CPU is getting hot very soon.
But I can't say what is with the "sudo hwinfo --framebuffer" thing, as I wrote in #21, I didn't check it again, can somebody else check this pleas if it happens on other MacBooks too?

Revision history for this message
Simon Déziel (sdeziel) wrote :

The cleanest workaround for this bug that I've found is to run the Maverick kernel that is now officially supported on Lucid. All you need to do is :

sudo apt-get install linux-image-generic-lts-backport-maverick

Official specs that documents this: https://wiki.ubuntu.com/KernelTeam/Specs/KernelMaverickNewKernelOnLTS

Revision history for this message
Alan Aversa (aversa) wrote :

I have a sudden shutdown problem in 11.04. My MacBook 2,1 will not freeze; it'll just immediately shutdown. Occasionally, it will suddenly shutdown and immediately reboot. Often it has this problem when waking from suspend.

Revision history for this message
quequotion (quequotion) wrote :

I am having this issue in 2012 in Oneiric with an AMD cpu.

What changes in the kernel cause these reboots?

Revision history for this message
penalvch (penalvch) wrote :

Moraus, thank you for reporting this and helping make Ubuntu better. 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could 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.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.