Re: grub2 not able to boot 1G size of linux iso file

[Andrei Borzenkov]

On Mon, Jan 18, 2016 at 7:08 AM, Ramakrishna Maladi (rmaladi)
<address@hidden> wrote:
> I don’t see memory allocation error. However, with allocated memory, after
> copying 1.12G of initrd.img, I see x64 exception indication memory
> corruption
>

That's rather different from what you described before.

> !!! X64 Exception Type - 0000000000000006 !!!!
>

As far as I understand this is "Illegal opcode", but unfortunately it
is absolutely unclear at which point you get it.

GRUB knows how much memory it has and how much memory initrd needs. So
I expect it to fail allocation for initrd if not enough memory is
available.

Could you please

- describe step-by-step what you did (from the very start - booting
GRUB) before you got this exception
- provide output of "lsmmap" in GRUB to show current available memory
- test current upstream GIT master whether it still has the same problem

Do you have possibility to capture serial output? It looks like you
are using QEMU, am I right?


> RIP - 000000007BF0B7C2, CS - 0000000000000038, RFLAGS - 0000000000210086
>
> RAX - 000000007BF23657, RCX - 000000000000001F, RDX - 000000007BF0B768
>
> RBX - 00000000684AF0A0, RSP - 000000007BF0B708, RBP - 000000007BF0BAC0
>
> RSI - 00000000666AEAE1, RDI - 000000007BF0B770
>
> R8 - 0000000000000012, R9 - 0000000000000020, R10 - 0000000000000002
>
> R11 - 0000000000C00E14, R12 - 0000000000002800, R13 - 0000000000005800
>
> R14 - 0000000000000F71, R15 - 0000000077973800
>
> DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030
>
> GS - 0000000000000030, SS - 0000000000000030
>
> GDTR - 00007BC351D00047 4848246C8B480000, LDTR - 0000000000000000
>
> IDTR - 00007B1520180FFF CCCCC35F5C410000, TR - 0000000000000000
>
> CR0 - 0000000080000013, CR2 - 0000000000000000, CR3 - 000000007BD7B000
>
> CR4 - 0000000000000668, CR8 - 0000000000000000
>
> DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
>
> DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
>
>
>
>
> If I use initrd.img of 850M, it works fine.
>
> If I reduce PCIe MMIO config memory, even 1.12G file boots up fine.
>
> So, idea here is, if I have grub allocating memory above 4G, it might work
> fine.
>
> Thanks,
> Ram
>
> On 1/17/16, 7:40 PM, "Andrei Borzenkov" <address@hidden> wrote:
>
>>18.01.2016 06:24, Ramakrishna Maladi (rmaladi) пишет:
>>> It is for i386-pc family (in fact x86_64 - broad well DE).
>>> I need it because I want to boot 1.12G size of initrd.img from USB
>>> This is failing because of low mem crunch
>>>
>>
>>I do not understand what "low mem crunch" is, nor do I see any memory
>>allocation error.
>>
>>> Thanks,
>>> Ram
>>>
>>> On 1/17/16, 7:19 PM, "Andrei Borzenkov" <address@hidden> wrote:
>>>
>>>> 18.01.2016 01:36, Ramakrishna Maladi (rmaladi) пишет:
>>>>> Hi
>>>>>   Is there a way to allocate memory which is above 4G for initrd.img
>>>>>in
>>>>> grub?
>>>>>
>>>>
>>>> It probably depends on platform, on i386-pc memory allocator is
>>>> restricted to 4G address space. Why would you need that?
>>>>
>>>>> Thanks,
>>>>> Ram
>>>>>
>>>>> On 1/10/16, 12:20 AM, "address@hidden on
>>>>> behalf of Ramakrishna Maladi (rmaladi)"
>>>>> <address@hidden on behalf of
>>>>> address@hidden> wrote:
>>>>>
>>>>>>
>>>>>> set default=0
>>>>>> serial --unit=0 --speed=51200
>>>>>>
>>>>>> terminal_input console
>>>>>> terminal_output serial
>>>>>> set timeout=5
>>>>>>
>>>>>> menuentry "System Install OS" {
>>>>>>        echo "Booting from USB.."
>>>>>>        loopback loop /myimage.iso
>>>>>>        set root=(loop)
>>>>>>        echo "Loading Kernel.."
>>>>>>        linux (loop)/boot/bzImage root=/dev/ram install=/dev/sda
>>>>>> console=ttyS0,38400 prod=1 address@hidden bigphysarea=10M quiet
>>>>>> pci=assign-busses noissu aer=off pci=hpmemsize=0M,hpiosize=0
>>>>>>        echo "Loading initrd.."
>>>>>>        initrd (loop)/boot/initrd.img
>>>>>> }
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Ram
>>>>>>
>>>>>> On 1/9/16, 11:49 PM, "Andrei Borzenkov" <address@hidden> wrote:
>>>>>>
>>>>>>> 10.01.2016 08:11, Ramakrishna Maladi (rmaladi) пишет:
>>>>>>>> Friends,
>>>>>>>>   On broad well-DE intel CPU chipset when I run grub2.0 to load my
>>>>>>>> linux (Windriver destro of) iso file 1.2G, I am seeing an exception
>>>>>>>>   Would it be the EFI boot sevices issue in BIOS or an known issue
>>>>>>>>on
>>>>>>>> grub2.0 ?
>>>>>>>>   Could you pls point me if there is a patch I need to take in
>>>>>>>> grub2.0?
>>>>>>>> I have grub2.0 source of 2014.
>>>>>>>>
>>>>>>>> error: unsupported serial port speed.
>>>>>>>> error: terminal `serial' isn't found.
>>>>>>>>
>>>>>>>>
>>>>>>>> GNU GRUB version 2.00
>>>>>>>> Press F2 to goto grub Menu..
>>>>>>>> Booting from USB..
>>>>>>>> Loading Kernel..
>>>>>>>> loader/i386/linux.c:535: prot_mode_mem = 2000000, prot_mode_target
>>>>>>>>=
>>>>>>>> 2000000,
>>>>>>>> prot_size = 124a000
>>>>>>>> loader/i386/linux.c:1225: bzImage, setup=0x3c00, size=0x124a000
>>>>>>>> Loading initrd..
>>>>>>>> loader/i386/linux.c:1440: linux cmd agrc = 1
>>>>>>>> loader/i386/linux.c:1444: argv[0]: (loop)/boot/initrd.img
>>>>>>>> ERROR: Class:3000000; Subclass:50000; Operation: 6
>>>>>>>>
>>>>>>>
>>>>>>> I do not see such error string in current GRUB sources at all. Could
>>>>>>> you
>>>>>>> attach grub.cfg, otherwise we have no idea what your ISO does.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Help-grub mailing list
>>>>>> address@hidden
>>>>>> https://lists.gnu.org/mailman/listinfo/help-grub
>>>>>
>>>>
>>>
>>
>