Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-03 Thread Michael Schmitz
Hi Geert, Am 03.12.2018 um 20:49 schrieb Geert Uytterhoeven: Hi Michael, Mike, On Mon, Dec 3, 2018 at 5:53 AM Michael Schmitz wrote: Am 03.12.2018 um 00:04 schrieb Mike Rapoport: I don't know what were the shortcomings of the old memory model, and why ST-RAM and FastRAM are treated

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Geert Uytterhoeven
Hi Michael, Mike, On Mon, Dec 3, 2018 at 5:53 AM Michael Schmitz wrote: > Am 03.12.2018 um 00:04 schrieb Mike Rapoport: > > I don't know what were the shortcomings of the old memory model, and why > > ST-RAM and FastRAM are treated differently, so probably the simplest way > > would be just

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Michael Schmitz
Hi Mike, Am 03.12.2018 um 00:04 schrieb Mike Rapoport: I don't know what were the shortcomings of the old memory model, and why ST-RAM and FastRAM are treated differently, so probably the simplest way would be just inform memblock that the ST-RAM is not available to it: diff --git

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Michael Schmitz
Geert, On 3/12/18 11:57 AM, Michael Schmitz wrote: Only a single memory chunk (ST-RAM), and kernel loaded there. Same here. The only memory-related option I have in my ARAnyM config is FastRAM = 256 and that works. Andreas: can you please share your ARAnyM config, so we can reproduce?

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Michael Schmitz
On 3/12/18 12:04 AM, Mike Rapoport wrote: On Sat, Dec 01, 2018 at 11:51:52AM +1300, Michael Schmitz wrote: Andreas, Am 01.12.2018 um 11:23 schrieb Andreas Schwab: On Dez 01 2018, Michael Schmitz wrote: Must be a new kind of monster kernel that wouldn't fit inside 14 MB. There's way more

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Michael Schmitz
Geert, On 2/12/18 10:57 PM, Geert Uytterhoeven wrote: On Fri, Nov 30, 2018 at 10:24 PM Michael Schmitz wrote: Am 01.12.2018 um 10:12 schrieb Andreas Schwab: On Nov 30 2018, Andreas Schwab wrote: [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1 20180712 (GCC)) #3

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Mike Rapoport
On Sat, Dec 01, 2018 at 11:51:52AM +1300, Michael Schmitz wrote: > Andreas, > > Am 01.12.2018 um 11:23 schrieb Andreas Schwab: > >On Dez 01 2018, Michael Schmitz wrote: > > > >>Must be a new kind of monster kernel that wouldn't fit inside 14 MB. > > > >There's way more than the kernel that must

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Mike Rapoport
Hello Andreas, On Fri, Nov 30, 2018 at 10:12:47PM +0100, Andreas Schwab wrote: > On Nov 30 2018, Andreas Schwab wrote: > > > [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1 > > 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018 > > [0.00] Saving 190 bytes of

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-02 Thread Geert Uytterhoeven
On Fri, Nov 30, 2018 at 10:24 PM Michael Schmitz wrote: > Am 01.12.2018 um 10:12 schrieb Andreas Schwab: > > On Nov 30 2018, Andreas Schwab wrote: > > > >> [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1 > >> 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018 > >> [

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-01 Thread Andreas Schwab
On Dez 01 2018, Michael Schmitz wrote: > Am 01.12.2018 um 12:09 schrieb Andreas Schwab: >> On Dez 01 2018, Michael Schmitz wrote: >> >>> Doesn't work for me - with or without -s option I get the same >> >> What -s option? > > In the LILO section: > > Args = -s root=/dev/hda1 debug=par

Re: m68k-v4.19 crashes in free_all_bootmem

2018-12-01 Thread Michael Schmitz
Andreas, Am 01.12.2018 um 08:57 schrieb Andreas Schwab: [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018 [0.00] Saving 190 bytes of bootinfo [0.00] console [debug0] enabled [0.00] Atari hardware

Re: m68k-v4.19 crashes in free_all_bootmem

2018-11-30 Thread Michael Schmitz
Am 01.12.2018 um 12:09 schrieb Andreas Schwab: On Dez 01 2018, Michael Schmitz wrote: Doesn't work for me - with or without -s option I get the same What -s option? In the LILO section: Args = -s root=/dev/hda1 debug=par stram_pool=2048k Cheers, Michael

Re: m68k-v4.19 crashes in free_all_bootmem

2018-11-30 Thread Andreas Schwab
On Dez 01 2018, Michael Schmitz wrote: > Doesn't work for me - with or without -s option I get the same What -s option? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: m68k-v4.19 crashes in free_all_bootmem

2018-11-30 Thread Michael Schmitz
Andreas, Am 01.12.2018 um 11:23 schrieb Andreas Schwab: On Dez 01 2018, Michael Schmitz wrote: Must be a new kind of monster kernel that wouldn't fit inside 14 MB. There's way more than the kernel that must fit in 14 MB. I realize that. I only said to try and load the kernel to ST-RAM,

Re: m68k-v4.19 crashes in free_all_bootmem

2018-11-30 Thread Andreas Schwab
On Dez 01 2018, Michael Schmitz wrote: > Try with the kernel loaded in ST-RAM - should not make a difference for > ARAnyM, or does it now? There isn't enough space there. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA

Re: m68k-v4.19 crashes in free_all_bootmem

2018-11-30 Thread Michael Schmitz
Andreas, Am 01.12.2018 um 10:12 schrieb Andreas Schwab: On Nov 30 2018, Andreas Schwab wrote: [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018 [0.00] Saving 190 bytes of bootinfo [0.00] console

Re: m68k-v4.19 crashes in free_all_bootmem

2018-11-30 Thread Andreas Schwab
On Nov 30 2018, Andreas Schwab wrote: > [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1 > 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018 > [0.00] Saving 190 bytes of bootinfo > [0.00] console [debug0] enabled > [0.00] Atari hardware found: