Re: alloc magic is broken at... error

[SevenBits]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/20/2014 10:33 AM, Andrey Borzenkov wrote:
> В Mon, 20 Jan 2014 10:30:33 -0500 SevenBits
> <address@hidden> пишет:
> 
>> On Jan 20, 2014, at 10:27 AM, Andrey Borzenkov
>> <address@hidden> wrote:
>> 
>>> В Mon, 20 Jan 2014 09:59:40 -0500 SevenBits
>>> <address@hidden> пишет:
>>> 
>>>> On Jan 19, 2014, at 9:23 PM, Andrey Borzenkov
>>>> <address@hidden> wrote:
>>>> 
>>>>> В Sun, 19 Jan 2014 19:45:23 -0500 SevenBits
>>>>> <address@hidden> пишет:
>>>>> 
>>>>>> Not sure whether to post this in this bug-grub list or
>>>>>> here, so feel free to correct me if perhaps this is in
>>>>>> the wrong spot. I’m not sure if the issue I’m having is
>>>>>> due to a fault in setup or a bug within GRUB.
>>>>>> 
>>>>>> I’m the developer of a tool called Mac Linux USB Loader,
>>>>>> and some of my users are reporting errors with my
>>>>>> compiled copy of GRUB. Specifically, after loading the
>>>>>> kernel, GRUB spits out the following error message:
>>>>>> 
>>>>>> alloc magic is broken at 0x81493ca0: 207d007d68746170 
>>>>>> Aborted. Press any key to exit.
>>>>>> 
>>>>>> The hexadecimal values vary slightly, but generally
>>>>>> speaking this is what the error looks like. The kernel
>>>>>> loading operation with GRUB’s linux command is followed
>>>>>> by the initrd command to load the RAM disc, and that
>>>>>> operation never occurs, so I know that the operation
>>>>>> never completes.
>>>>>> 
>>>>>> This error never seems to occur with Ubuntu-based
>>>>>> distributions. It also seems to occur if the kernel can’t
>>>>>> be found - but in that case, shouldn’t the linux command
>>>>>> fail with an error instead of something like this?
>>>>>> 
>>>>>> I can’t post my GRUB config at the moment, as I’m not on
>>>>>> the machine where it is stored, but any advice that you
>>>>>> can give me without it would be appreciated, such as
>>>>>> under what conditions this error occurs.
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> — SevenBits
>>>>> 
>>>>> Well, the first thing to try would be upstream HEAD to
>>>>> verify whether problem is still present there.
>>>> 
>>>> Sorry, just realized my previous reply didn’t get posted.
>>>> 
>>>> The GRUB build I’m using is compiled straight from the
>>>> current git repository. It might be a week or two old, but
>>>> unless something really changed in the last two to three
>>>> weeks I don’t think it’ll differ.
>>>> 
>>> 
>>> In this case you need to post to gurb-devel. Is there any way
>>> to get output to serial console?
>> 
>> No, I don’t think so, unless there’s some GRUB trick that I don’t
>> know about. Once this happens GRUB crashes to a stop and I can’t
>> do anything.
>> 
> 
> You could change to serial console before running this command and 
> enable debugging.

Unfortunately, I can't seem to be to able to get a serial cable that
works with the MacBook that I'm testing on, so it doesn't appear that
I'll be able to test this using the method you recommended.

Is there any other way to get output from GRUB, or at least discern
what is causing this error?

> 
>>> 
>>>> I can try an older release of GRUB, like the latest stable
>>>> and see if that does anything though.
>> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS5CmXAAoJEFbRvtGxmFPEOcoIAJjS1WWvF+KdJSOcmqslhtFK
WfNUGn/aeDK0Z0mR4CNHGTa4aKc7jX2/iAkyqg9FfIqV5zAJ7akPEjX5de8IWIrp
7QoNH4G9ihJ9D/KjICcdL9jJgt20Mi/Bb2e6zhH6As9IMq4E606OehpjnKs6p2rG
WZv0piOSj7Cm0PmqDv/pKCcNvxcIifFBD+rQmST4mRYwyILakpY028EALMfFGrLR
1w6s2TJBQvWqsKY+761uGL5EVB/hyQkNx8bawz+GZyVSMTEivBE+sIKIjoORNTUs
54+f11clA/ld1L+4+0eu4cx3PqKHEZawr6KXmsdrC4XSEQqgsQ2/ZoYrjyPsEJM=
=+OUc
-----END PGP SIGNATURE-----