Re: Trunk: boot problem - unaligned pointer 0x...

[Aleš Nesrsta]

Hi,

I discovered something.
It looks like problem is caused by empty line in booting command list:

...
script/lexer.c:305: token 290 text [Debian GNU/Linux, linux
2.6.32-bpo.5-686
/dev/sdb1]
script/script.c:50: malloc 0x3ffac100
script/script.c:50: malloc 0x3feddab0
script/lexer.c:305: token 290 text []
script/script.c:50: malloc 0x3ff11360
script/script.c:50: malloc 0x3ff14ee0
script/script.c:163: arglist
script/script.c:50: malloc 0x3ff1e4a0
script/lexer.c:305: token 259 text [
]
script/script.c:50: malloc 0x3ff24e90
script/script.c:50: malloc 0x3ff25010
script/script.c:198: cmdline
script/script.c:50: malloc 0x3ff2d2c0
script/lexer.c:305: token 0 text []
script/script.c:50: malloc 0x3fee1d10
script/script.c:50: malloc 0x3ff11340
script/script.c:294: append command
script/script.c:50: malloc 0x3ff1b130
unaligned pointer 0x692a6373

But I don't know where the empty line is generated - it is not in
grub.cfg

Regards
Ales


Aleš Nesrsta wrote:
> Hi,
> 
> there is some bug in trunk last versions:
> 
> I am not able to boot with normal configuration stored in grub.cfg - if
> I select any item from menu (or wait for timeout for default item),
> booting is aborted with messages:
> 
> 
> "
> Booting 'xyz...'
> 
> unaligned pointer 0x...
> Aborted. Press any key to exit.
> "
> 
> If I edit menu item, delete "search" command and specify Linux root
> device directly ("linux ... root=/dev/sdb1..."), Linux is booted
> normally.
> 
> 
> Some initial information:
> 
> GRUB was autoconfigured for compilation in this way:
> *******************************************************
> GRUB2 will be compiled with following components:
> Platform: i386-pc
> With devmapper support: No (need devmapper library)
> With memory debugging: No
> efiemu runtime: Yes
> grub-mkfont: Yes
> *******************************************************
> 
> Menuentry looks for example like that:
>         set root=(hd0,1)
>         search --fs-uuid --set 02ba8dca-885d-4acd-9730-eee482f3305b
>         linux   /boot/vmlinuz-2.6.32-bpo.5-686
> root=UUID=02ba8dca-885d-4acd-9730-eee482f3305b ro  
>         initrd  /boot/initrd.img-2.6.32-bpo.5-686
> 
> 
> Unfortunately, I cannot simply debug this problem, because when I set
> for example "all" into debug variable, problem does not happen and boot
> is processed normally... :-(
> 
> Regards
> Ales
> 
> 
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel
>