Linux Kernel 5.1.2 MVEBU - INITRD overlaps in-use memory region (11 replies)

I've compiled the mainline kernel (without patches) and trying to run the generated uImage and the ramdisk of the debian installer.
My problem is that if I use the precompiled kernle 5.1.2 the initrd is not loaded beacuse the ramfs is disabled. My compiled kernel with BLK_DEV_RAM=y instead of external module fails with these errors

...
[    0.000000][    T0] INITRD: 0x00f00000+0x01461000 overlaps in-use memory region - disabling initrd
....
[    2.495171][    T1] FAT-fs (ram0): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[    2.506803][    T1] FAT-fs (ram0): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[    2.519234][    T1] F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[    2.526774][    T1] F2FS-fs (ram0): Can't find valid F2FS filesystem in 1th superblock
[    2.534756][    T1] F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[    2.542280][    T1] F2FS-fs (ram0): Can't find valid F2FS filesystem in 2th superblock
[    2.550272][    T1] List of all partitions:
[    2.554491][    T1] 0100           32768 ram0 
[    2.554493][    T1]  (driver?)
[    2.562026][    T1] No filesystem could mount root, tried: 
[    2.562028][    T1]  ext3
[    2.567638][    T1]  ext4
[    2.570270][    T1]  vfat
[    2.572901][    T1]  msdos
[    2.575541][    T1]  iso9660
[    2.578261][    T1]  udf
[    2.581155][    T1]  f2fs
[    2.583706][    T1] 
[    2.588536][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

If I use the precompiled kernel from https://themm.net/public/ex2u/start the ramdisk is loaded and the installer popups immediately in the serial console.
Any help?
Thank you

*** EDIT ***
I've managed to start the netinstaller of debian moving the address where uRamdisk is loaded to 0x2000000, the same used in case of tftp loading

usb start
fatload usb 0:1 0xa00000 boot/uImage
fatload usb 0:1 0x2000000 boot/uRamdisk
bootm 0xa00000 0x2000000

Why this behaviour was not evidend with older kernel versions?

-----

moderator: added code tags.