On Fri, 9 Sep 2022, Stephen Walsh wrote:
> Hi Finn, > > On Fri, 9 Sep 2022 11:36:49 +1000 (AEST) > Finn Thain <fth...@linux-m68k.org> wrote: > > > You mean, you tried kernel 5.15 with initrd 5.19? The question is, > > "did it oops?". Having seen the results below, I suspect that it > > didn't oops, despite the large initrd. > > ohh.. here's a successful boot with vmlinux-5.15.0-2-m68k > initrd.img-5.19.0-1-m68k > > > >>>>>>>>>>>>>>>>>>>> > [ 0.000000] Linux version 5.15.0-2-m68k (debian-ker...@lists.debian.org) > (gcc-11 (Debian 11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 > Debian 5.15.5-2 (2021-12-18) > [ 0.000000] printk: console [debug0] enabled > [ 0.000000] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF AUDIO > FLOPPY A3000_SCSI KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA > DENISE_HR AGNUS_HR_PAL MAGIC_REKICK ZORRO3 > [ 0.000000] Ignoring memory chunk at 0x7800000:0x800000 before the first > chunk > [ 0.000000] Fix your bootloader or use a memfile to make use of this area! > [ 0.000000] Zone ranges: > [ 0.000000] DMA [mem 0x0000000008000000-0x000000ffffffffff] > [ 0.000000] Normal empty > [ 0.000000] Movable zone start for each node > [ 0.000000] Early memory node ranges > [ 0.000000] node 0: [mem 0x0000000008000000-0x000000000fffffff] > [ 0.000000] Initmem setup node 0 [mem > 0x0000000008000000-0x000000000fffffff] > [ 0.000000] initrd: 0783283d - 08000000 That appears to be the 5.15 initrd.