[Jaunty] MacBook 5.1 will not reboot (Restart).

I turned on verbose in /boot/grub/menu.1st just to see where it gets stuck and it gets all the way to the end where it says
[ 74.88548] Restarting system....
_

Then just sits there with a blinking cursor.

It is well known that Linux will not reboot on the macbook 5,1.

So it is confirmed.

Is there any further debugging needed to move this bug along? Or is it well understood and just a matter of the resource/time needed to implement a fix?
I can run any debug needed if any dev has a use.

Following this bug [https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/302452] might help fix it. I did try the mainline kernel mentioned there and still wouldn't reboot for me but I had a bunch of nvidia kernel modules errors at that point so maybe if i resolved those with that kernel it would work:

As of a couple days ago, my MacBook Pro 5,1 on Jaunty suddenly started rebooting properly! Yay! I am now on Linux 2.6.28-11-generic. Has anyone else updated their Ubuntu packages and had this problem fixed?

Hi Colin!

It does _not_ work on MBP5,1 under Jaunty (64-bit) with kernel 2.6.28-11-generic :-(

Regards, Nikos

To echo Nikos, this does not work on a MacBook 5.1 (aluminum MacBook) under 64-bit Jaunty with the 2.6.28-11-generic kernel.

@Νίκος and Chris:
That is weird that it works for me now, but not for you. Just like Nikos, I am running 64-bit Jaunty on a MacBook Pro 5,1 with that kernel. And I have tried it multiple times: Reboot from Ubuntu works! I have not idea why it started working for me.

Can you guys compare /var/log/messages.0 after you each try to reboot? That may lead us to something.

Also, is shutdown working OK? This only effects reboot?

I can also confirm my MBP5,1 with latest Jaunty updates (uname -rv: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009) does not reboot either .

@Colin: there must be something different in your setup I guess... have you changed anything which may have got it working?

I haven't actually done anything to try to fix the reboot problem. My /var/log/messages unfortunately doesn't show anything interesting after a reboot. It just looks like this:

Apr 22 08:42:53 svelte kernel: [76362.012307] PM: resume devices took 3.096 seconds
Apr 22 08:42:53 svelte kernel: [76362.013151] Restarting tasks ... done.
Apr 22 08:42:53 svelte kernel: [76362.776528] eth0: no link during initialization.
Apr 22 08:42:53 svelte kernel: [76362.777333] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 22 09:02:20 svelte exiting on signal 15
Apr 22 09:04:50 svelte syslogd 1.5.0#5ubuntu3: restart.
Apr 22 09:04:50 svelte kernel: Inspecting /boot/System.map-2.6.28-11-generic
Apr 22 09:04:50 svelte kernel: Cannot find map file.
Apr 22 09:04:50 svelte kernel: Loaded 76599 symbols from 48 modules.
Apr 22 09:04:50 svelte kernel: [ 0.000000] BIOS EBDA/lowmem at: 0009fc00/0009fc00
Apr 22 09:04:50 svelte kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 22 09:04:50 svelte kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 22 09:04:50 svelte kernel: [ 0.000000] Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 (Ubuntu 2.6.28-11.42-generic)
Apr 22 09:04:50 svelte kernel: [ 0.000000] Command line: root=UUID=79fb814c-b4fa-4660-a804-af9118fb9ff3 ro quiet splash

There's no entry regarding the reboot itself, only messages from the kernel as it was booting up again after reboot. I do get a weird screen right before Linux reboots that has a bunch of green vertical lines and the message "Restarting system" behind the lines. This screen shows for about one second before the machine actually reboots.

I'm not sure what else could be different on my machine. I did add the modprobe options needed to get sound partially working (right speaker only):

options snd-hda-intel model=mbp3

I wonder if I'm the only one whose machine decided to start working?

FYI, I think he wanted

/var/log/messages.0

Which would be the archive from the previous session....

-
Jim Rorie, PhD
Logisys

<email address hidden>
IM: jfrorie (XMPP/GoogleTalk)

On Wed, 2009-04-22 at 16:20 +0000, Colin D Bennett wrote:
> I haven't actually done anything to try to fix the reboot problem. My
> /var/log/messages unfortunately doesn't show anything interesting after
> a reboot. It just looks like this:
>
> Apr 22 08:42:53 svelte kernel: [76362.012307] PM: resume devices took 3.096 seconds
> Apr 22 08:42:53 svelte kernel: [76362.013151] Restarting tasks ... done.
> Apr 22 08:42:53 svelte kernel: [76362.776528] eth0: no link during initialization.
> Apr 22 08:42:53 svelte kernel: [76362.777333] ADDRCONF(NETDEV_UP): eth0: link is not ready
> Apr 22 09:02:20 svelte exiting on signal 15
> Apr 22 09:04:50 svelte syslogd 1.5.0#5ubuntu3: restart.
> Apr 22 09:04:50 svelte kernel: Inspecting /boot/System.map-2.6.28-11-generic
> Apr 22 09:04:50 svelte kernel: Cannot find map file.
> Apr 22 09:04:50 svelte kernel: Loaded 76599 symbols from 48 modules.
> Apr 22 09:04:50 svelte kernel: [ 0.000000] BIOS EBDA/lowmem at: 0009fc00/0009fc00
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Initializing cgroup subsys cpuset
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Initializing cgroup subsys cpu
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 (Ubuntu 2.6.28-11.42-generic)
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Command line: root=UUID=79fb814c-b4fa-4660-a804-af9118fb9ff3 ro quiet splash
>
> There's no entry regarding the reboot itself, only messages from the
> kernel as it was booting up again after reboot. I do get a weird screen
> right before Linux reboots that has a bunch of green vertical lines and
> the message "Restarting system" behind the lines. This screen shows for
> about one second before the machine actually reboots.
>
> I'm not sure what else could be different on my machine. I did add the
> modprobe options needed to get sound partially working (right speaker
> only):
>
> options snd-hda-intel model=mbp3
>
> I wonder if I'm the only one whose machine decided to start working?
>

You have to look at /var/log/messages.0

(this is the log from the previous boot. )

Ricky

On Apr 22, 2009, at 11:20 AM, Colin D Bennett <email address hidden> wrote:

> I haven't actually done anything to try to fix the reboot problem. My
> /var/log/messages unfortunately doesn't show anything interesting
> after
> a reboot. It just looks like this:
>
> Apr 22 08:42:53 svelte kernel: [76362.012307] PM: resume devices
> took 3.096 seconds
> Apr 22 08:42:53 svelte kernel: [76362.013151] Restarting tasks ...
> done.
> Apr 22 08:42:53 svelte kernel: [76362.776528] eth0: no link during
> initialization.
> Apr 22 08:42:53 svelte kernel: [76362.777333] ADDRCONF(NETDEV_UP):
> eth0: link is not ready
> Apr 22 09:02:20 svelte exiting on signal 15
> Apr 22 09:04:50 svelte syslogd 1.5.0#5ubuntu3: restart.
> Apr 22 09:04:50 svelte kernel: Inspecting /boot/System.map-2.6.28-11-
> generic
> Apr 22 09:04:50 svelte kernel: Cannot find map file.
> Apr 22 09:04:50 svelte kernel: Loaded 76599 symbols from 48 modules.
> Apr 22 09:04:50 svelte kernel: [ 0.000000] BIOS EBDA/lowmem at:
> 0009fc00/0009fc00
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Initializing cgroup
> subsys cpuset
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Initializing cgroup
> subsys cpu
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Linux version
> 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu
> 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
> (Ubuntu 2.6.28-11.42-generic)
> Apr 22 09:04:50 svelte kernel: [ 0.000000] Command line:
> root=UUID=79fb814c-b4fa-4660-a804-af9118fb9ff3 ro quiet splash
>
> There's no entry regarding the reboot itself, only messages from the
> kernel as it was booting up again after reboot. I do get a weird
> screen
> right before Linux reboots that has a bunch of green vertical lines
> and
> the message "Restarting system" behind the lines. This screen shows
> for
> about one second before the machine actually reboots.
>
> I'm not sure what else could be different on my machine. I did add
> the
> modprobe options needed to get sound partially working (right speaker
> only):
>
> options snd-hda-intel model=mbp3
>
> I wonder if I'm the only one whose machine decided to start working?
>
> --
> [Jaunty] MacBook 5.1 will not reboot (Restart).
> https://bugs.launchpad.net/bugs/338083
> You received this bug notification because you are a member of Mactel
> Support, which is the registrant for Mactel Support.
>
> Status in Mactel Support: Confirmed
> Status in “linux-meta” source package in Ubuntu: New
>
> Bug description:
> As of Jaunty (Ubuntu 9.04) Alpha 5, with kernel 2.6.28-8-generic,
> the MacBook 5.1 will hang upon attempts to reboot (restart). The
> screen will go blank black, and the system will hang indefinitely. I
> suppose this is an improvement over Intrepid (Ubuntu 8.10), where
> the computer would both hang and make very loud beeping noises. :-)
> Still, I'm marking this as a bug since reboot is currently not
> possible.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mactel-support
> Post to : <email address hidden>...

@Ricky, Jim:
My /var/log/messages.0 hasn't been modified for about a week. The 'messages' files are not rotated every boot, but once per week. Here's a listing of my /var/log/messages*

-rw-r----- 1 syslog adm 339444 2009-04-22 10:04 /var/log/messages
-rw-r----- 1 syslog adm 207454 2009-04-16 05:13 /var/log/messages.0
-rw-r----- 1 syslog adm 198544 2009-04-09 01:28 /var/log/messages.1.gz
-rw-r----- 1 syslog adm 11422 2009-04-02 13:15 /var/log/messages.2.gz

As you can see from the following excerpt, all the messages in messages.0 are old:

cdb@svelte:~$ tail /var/log/messages.0
Apr 16 02:13:37 svelte -- MARK --
Apr 16 02:31:06 svelte kernel: [15466.089053] ACPI: EC: missing confirmations, switch off interrupt mode.
Apr 16 02:53:37 svelte -- MARK --
Apr 16 03:13:37 svelte -- MARK --
Apr 16 03:33:37 svelte -- MARK --
Apr 16 03:53:37 svelte -- MARK --
Apr 16 04:13:37 svelte -- MARK --
Apr 16 04:33:37 svelte -- MARK --
Apr 16 04:53:37 svelte -- MARK --
Apr 16 05:13:37 svelte -- MARK --

I have rebooted a number of times since 16 April.

Colin, I wouldn't expect to see anything interesting in your log since it is working for you. It would be helpful for comparison to others though.

To get the log, you can try this:
do a reboot, and when your system reboots into the refit screen, turn it off (there is a menu item for shutdown here).
then put in a linux liveCD and boot from that.
mount your filesystem and make a copy of /mounted/path/var/log/messages
That should get you a log that is untouched after shutdown that you can attach here.

Then if someone else, who cannot reboot would try, then use the livecd as above to get their log file, they can be compared.

Heres mine around the point of interest, I think. It was actually in /var/log/messages. Not very exciting....

Apr 22 16:01:00 medusa -- MARK --
Apr 22 16:08:15 medusa kernel: [23312.736309] CE: hpet increasing min_delta_ns to 22500 nsec
Apr 22 16:08:15 medusa kernel: [23312.736446] CE: hpet increasing min_delta_ns to 33750 nsec
Apr 22 16:08:15 medusa kernel: [23312.736578] CE: hpet increasing min_delta_ns to 50624 nsec
Apr 22 16:17:56 medusa exiting on signal 15

# I think this is the restart. I had to do a power reset

Apr 22 16:22:23 medusa syslogd 1.5.0#5ubuntu3: restart.
Apr 22 16:22:23 medusa kernel: Inspecting /boot/System.map-2.6.28-11-generic
Apr 22 16:22:23 medusa kernel: Cannot find map file.
Apr 22 16:22:23 medusa kernel: Loaded 76489 symbols from 47 modules.
Apr 22 16:22:23 medusa kernel: [ 0.000000] BIOS EBDA/lowmem at: 0009fc00/0009fc00
Apr 22 16:22:23 medusa kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 22 16:22:23 medusa kernel: [ 0.000000] Initializing cgroup subsys cpu

messages doesn't seem to be recording anything on mine.

It seems that rebooting now works successfully for me. Perhaps I was missing a kernel update. I just tried it, though and it rebooted fine. So for me, this bug is fixed now.

Rebooting still doesn't work for me as of today. I'm on Jaunty with all latest updates 64-bit.

Chris, does it still work for you? what hardware? do you just reboot through gnome or 'shutdown -r now'?

I was about to come back and comment on here myself. No, reboot does *not* work for me now... again... I don't know. It could be perhaps installation of one of the Apple hardware packages from the PPA that kicked it out again. I actually haven't tried shutting down using ``shutdown``. For a brief period in time, however, reboot really did work.

This is not a bug in the linux-meta package, moving to the linux package.

Try adding "reboot=pci" to the kernel command line. That fixed the issue for me. I'm running 2.6.30-gentoo-r1 (x86_64) on a late 2008 MacBook Pro. Yes, I know it's not an Ubuntu kernel, but you guys appear to be the only folks on the planet with an actual bug filed about this!

In my testing, reboot=kbd (the default) did not work, nor did reboot=acpi, or reboot=efi. I didn't try reboot=triple since a triple-fault reset seems like an ugly way to recycle the system. reboot=bios might be another option if you're running 32-bit.

@M Cams:

Can you describe where exactly this "parameter" should go? In which file/script should this go?

Thanks, Nikos

it needs to go at the end of the kernel command line (in /boot/grub/menu.lst)

rather than editing the menu file each time, you can press e on the grub screen that offers you boot choices, then select the line with the kernel and press e again, and add the reboot parameter.

I've tried many variations of the reboot parameter on my macbook pro 5,1 - none work for me.

Yep, though so (that it goes to menu.lst) but often we write thing and forget that beginners or even average users (like me) will understand right away what we mean.

Thanks dberger, Nikos

@Nikos:
Here's my menu.lst entry. I've provided a "before" and "after" so you can see the differences (since it's not an Ubuntu-based menu.lst).

Before:
title Gentoo Linux 2.6.30-r1
root (hd0,2)
kernel /boot/vmlinuz-2.6.30-gentoo-r1 root=/dev/ram0 real_root=/dev/shiny/root dolvm
initrd /boot/initramfs-genkernel-x86_64-2.6.30-gentoo-r1

After:
title Gentoo Linux 2.6.30-r1
root (hd0,2)
kernel /boot/vmlinuz-2.6.30-gentoo-r1 root=/dev/ram0 reboot=pci real_root=/dev/shiny/root dolvm
initrd /boot/initramfs-genkernel-x86_64-2.6.30-gentoo-r1

The only difference should be "reboot=pci" after "root=/dev/ram0" on the kernel line.

Thank you for your time M Carns :-)

Nikos

reboot=pci nor other of reboot alternatives did not help to fix this issue on my system. is there anything that I can do to help to trace the origin of the issue? - run some debugging/logging kernel build etc.?

The parameter "reboot=pci" did not help me either.

Nikos

I just want to report that I have reboot working on the MB-P5,1. Don't know what exactly was the fix. All i did is:

* updates/ dist-upgrades
* latest PulseAudio stuff
* drop Xinerama and user TwinView (much more faster/ smoother)

Best regards, Nikos

I just upgraded as well, however I am not able to reboot. The only difference is that I'm using separate X for the display, not twinview. (I can't change it to test because I had so much trouble getting it to work the first time.)

To all,

sorry for the previous post of success. It does _not_ work again and I can't tell what is the difference since yesterday :-(

The "reboot" problem is present also in Karmic (using the "alpha 3" live-cd) for MBP5,1.

Hi,

I'm also a Gentoo user (kernel 2.6.30-gentoo-r4), so maybe that comment is not of interest for you, but I also solved the reboot issue on a macbook pro 5,1 following comment #21. It seems that the kernel is going to be patched:
http://patchwork.kernel.org/patch/39169/

So maybe it's worth digging deeper in that direction ...

my two cents,
  ph.

It works in karmic alpha 6

> It works in karmic alpha 6

Confirmed. Hope it stays that way....

Does *not* work for me on 2.6.28-15-generic. I suspect that option was added/fixed upstream in a newer kernel.

er, that's on a MacMini3,1 (nvidia). I followed the wrong link on the bugmail, sorry. (meant to add that comment on bug 343781)

Restart doesn't work on karmic beta. I tested also with "reboot=pci" that under ArchLinux with 2.6.30 works.

Greets, ercoppa.

Karmic beta still reboots here.

Yep I can also confirm Karmic beta successfully reboots on my MacBook Pro 5,1 too.

Ok, you are right, reboot works also for me (I need to uninstall kexec-tools).

Greets, ercoppa.

Working fine for me with Karmic Beta.

On a related note, suspend is working reliably under Karmic Beta. :D

Hiberate appears to work, but might be slower than booting.

Hi Chris,

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/lucid.

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 338083

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.

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

I can confirm that reboot works on my MacBook 5.1 ever since I upgraded to Karmic.

Chris,
   Can you verify that this is resolved for you as well? Please adjust the status if you still encounter this.

Thanks!

~JFo

This bug has been resolved for me in Ubuntu 9.04 Karmic Koala. Thanks for checking. Bug can be closed.

Thanks for the follow up Chris. :-)

~JFo