Ticket #17 (closed defect: fixed)

Opened 17 months ago

Last modified 4 months ago

mips32 and ppc32 cannot boot from a large ramdisk

Reported by: decky Owned by:
Priority: major Milestone:
Component: unspecified Version: mainline
Keywords: Cc:

Description

The loader doesn't check whether the contents of image.boot overlaps with the memory where it intends to copy the kernel and the init tasks. Currently, the FAT root file system image has several megabytes in size and IMHO overlaps with the destination area. This prevents the system from booting the kernel.

With arm32 the symptoms are little bit different. The kernel and init tasks boot fine, but the ramdisk content seems to be corrupted.

Change History

Changed 16 months ago by jermar

  • component set to unspecified
  • summary changed from mips32, ppc32 and arm32 cannot boot from a large ramdisk to mips32 and ppc32 cannot boot from a large ramdisk

In 4436, the arm32 has been fixed wrt. this bug.

Changed 4 months ago by decky

  • status changed from new to closed
  • resolution set to fixed

With the new boot framework since changeset:[head,428] this has been fixed. The loaders check for any possible overlap.

The mips32 bootloader is still limited to 4 MB (since this is the size of the dedicated ROM memory of MIPS) and larger sizes are not actually detected by the loader. However, loading an oversized ROM image should be a simulator warning.

Note: See TracTickets for help on using tickets.