Bug#560823: grub-ieee1275: Error "Memory Address not Alligned" when trying to boot any menu entry

[Colin Watson]

On Sat, Dec 12, 2009 at 04:20:58PM +0100, Axel Beckert wrote:
> this is basically a followup bug to #550160. I haven't updated much on
> the box since then (except grub2 itself of course and replaced
> 2.6.30-1 by 2.6.31-1) and the box is still offline since I only can
> boot it from CD over serial console currently.
> 
> So I copied the package information at the end of the bug report from
> #550160, just added the recently appeared double slashes at path
> beginnings in in grub.cfg and updated the grub-common version
> manually.
> 
> If you think, even small changes in there could be the source of the
> bug, feel free to tell me, and I'll try to get current data or update
> some other packages if you think it could help.
> 
> Since #550160 has been fixed, the grub menu appears, I can edit the
> entries on the console, etc.
> 
> But as soon as I want to boot one entry, I get the error message
> "Memory Address not Alligned" and I'm back to the boot prompt "ok" of
> OpenPROM/OpenBoot.

Vladimir Serbinenko (upstream) told me that he believes he's fixed this:
the problem was apparently that Open Firmware only gives us a very small
stack, so he had to add the ability to switch the stack pointer to our
own chunk of memory in order to have a decent stack size.  Any version
from 1.98+20100527-1 onward should have this fix.  If you still have the
affected system in operation, could you please try upgrading to the
current version in unstable and letting us know if it resolves this
problem?

Thanks,

-- 
Colin Watson                                       [cjwatson at debian.org]