Re: BigRAMPlus seems to be detected now
On Tue, Mar 10, 2020 at 1:15 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Stefan,
>
> On Tue, Mar 10, 2020 at 4:06 AM Stefan Reinauer
> <stefan.k.reinauer@gmail.com> wrote:
> > On Sun, Mar 8, 2020 at 3:43 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > As well as trying to boot it with the BRP as primary memory (BRP first
> > > in memfile) or sole memory (motherboard RAM disabled in memfile).
> >
> > With BigramPlus as sole memory the system can't seem to deal with the
> > initramfs (see log)
>
> However, according to this log you have both enabled:
>
> > On node 0 totalpages: 4096
> > DMA zone: 40 pages used for memmap
> > DMA zone: 0 pages reserved
> > DMA zone: 4096 pages, LIFO batch:0
>
> 16 MiB
>
> > On node 1 totalpages: 65536
> > DMA zone: 640 pages used for memmap
> > DMA zone: 0 pages reserved
> > DMA zone: 65536 pages, LIFO batch:15
>
> 256 MiB
>
> > SLUB: Unable to allocate memory from node 0
> > SLUB: Allocating a useless per node structure in order to be able to continue
> > SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=8
>
> Probably the 16 MiB in the first chunk is too small to allocate
> page tables from, especially if it contains the initramfs.
>
> What happens if you put the BRP first in the memfile?
Before chipram?
---------------------------------
0x50000000 268435456
2097152
---------------------------------
[ 0.000000] Linux version 5.4.0-4-m68k
(debian-kernel@lists.debian.org) (gcc version 9.2.1 20200203 (Debian
9.2.1-28)) #1 Debian 5.4)
[ 0.000000] Amiga hardware found: [A4000] VIDEO BLITTER AUDIO
FLOPPY A4000_IDE KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAU
[ 0.000000] initrd: 008517bf - 01000000
[ 0.000000] Built 2 zonelists, mobility grouping on. Total pages: 68952
[..]
[ 53.910000] Run /init as init process
[ 53.940000] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000004
[ 53.940000] CPU: 0 PID: 1 Comm: init Not tainted 5.4.0-4-m68k #1
Debian 5.4.19-1
[ 53.940000] Stack from 00821e38:
[ 53.940000] 00821e38 00377373 0002c276 000000ff 00000001
400004d8 0081c000 00000004
[ 53.940000] 00820000 0000000c 00821ea4 0002db40 0036f405
00000004 00000004 00000001
[ 53.940000] 400004d8 0003477c 00032732 008272dc 00821f6c
00821f80 00828f60 00000000
[ 53.940000] 00000000 000000cd 00000000 008dc150 0002e182
00000004 00000003 000350fe
[ 53.940000] 00000004 0000007c 00000000 00000000 00000000
00000001 00000000 00821fcc
[ 53.940000] 00821f6c 00820000 00821fa4 008272a0 00002be2
00820007 000042f2 00821f6c
[ 53.940000] Call Trace: [<0002c276>] panic+0xc4/0x296
[ 53.940000] [<0002db40>] do_exit+0x142/0x70e
[ 53.940000] [<0003477c>] do_signal_stop+0x0/0x142
[ 53.940000] [<00032732>] __list_del_entry+0x0/0x24
[ 53.940000] [<0002e182>] do_group_exit+0x48/0x80
[ 53.940000] [<000350fe>] get_signal+0x124/0x490
[ 53.940000] [<00002be2>] do_IRQ+0x26/0x32
[ 53.940000] [<000042f2>] do_notify_resume+0x32/0x4d4
[ 53.940000] [<002e099e>] kernel_init+0x0/0xd2
[ 53.940000] [<00034fb4>] force_sig_fault_to_task+0x30/0x3c
[ 53.940000] [<00002a64>] do_signal_return+0x10/0x1a
[ 53.940000] [<002e099e>] kernel_init+0x0/0xd2
[ 53.940000] [<0000c000>] apollo_irq_eoi+0x10/0x24
[ 53.940000] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x00000004 ]---
This one works:
---------------------------------
2097152
0x50000000 268435456
0x07000000 16777216
---------------------------------
Same as only using the bigram (and I got into the OS just fine, but I
had to do the installation through qemu)
I also did some tests, and had Amiga Test Kit running over night,
which couldn't find anything wrong with the onboard fast ram.
Stefan
> Thanks!
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
Reply to: