Opened 15 years ago
Closed 14 years ago
#17 closed defect (fixed)
mips32 and ppc32 cannot boot from a large ramdisk
| Reported by: | Martin Decky | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | helenos/unspecified | Version: | mainline |
| Keywords: | Cc: | ||
| Blocker for: | Depends on: | ||
| See also: |
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 (2)
comment:1 by , 15 years ago
| Component: | → unspecified |
|---|---|
| Summary: | mips32, ppc32 and arm32 cannot boot from a large ramdisk → mips32 and ppc32 cannot boot from a large ramdisk |
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
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.
In 4436, the arm32 has been fixed wrt. this bug.