mactel-support team mailing list archive

[Ricky Campbell <cyberdork33@xxxxxxxxx>]

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 <colin@xxxxxxxxxxx> 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     : mactel-support@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mactel-support
> More help   : https://help.launchpad.net/ListHelp

-- 
[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.