Hi,
On Sun, May 12, 2019 at 09:59:00AM +0200, Angelo Dureghello wrote:
Hi all,
resending this in the proper mailing (sent to lkml for error).
Just rebased to master right now, so @ > 5.1.1,
nommu boot works, mmu boot hangs without any message.
Before rebase i was near 5.1-rc1 but lost the log, unfortunately.
I am booting linux passing a ramfs address of a ramfs loaded
in memory from u-boot.
After some investigations, just found this:
- without passing the ramfs, kernel boots.
- with ramfs, adding some low level traces, i get:
5Linux version 5.1.0stmark2-001-09826-gd881126bf3f8-dirty (angelo@box)
(gcc version 5.2.0 (crosstools-sysam-2016.04.16))
#221 Sun May 12 00:31:57 CEST 2019
initrd at 0x47d33000:0x47d85e44
overlap at 1073741889 for chunk 0
overlap at 1073746160 for chunk 0
overlap at 1073746719 for chunk 0
overlap at 1073746720 for chunk 0
overlap at 1073746721 for chunk 0
overlap at 1073746722 for chunk 0
i am far from understanding the real issue, btw, i found a workaround:
diff --git a/arch/m68k/mm/init.c b/arch/m68k/mm/init.c
index 8868a4c9adae..33d14cb60fe5 100644
--- a/arch/m68k/mm/init.c
+++ b/arch/m68k/mm/init.c
@@ -57,7 +57,7 @@ pg_data_t *pg_data_table[65];
EXPORT_SYMBOL(pg_data_table);
#endif
-void __init m68k_setup_node(int node)
+void m68k_setup_node(int node)
{
#ifndef CONFIG_SINGLE_MEMORY_CHUNK
struct m68k_mem_info *info = m68k_memory + node;
In this way i can boot again with mmu enabled.
Regards,
Angelo
