evbarm: dockstar hang out at boot

[Jean-Yves Moulin <jym%baaz.fr@localhost>]

Hi port-arm,

My old seagate dockstar (Marvell Kirkwood) freezes at boot just after :

	raid0: RAID Level 1                                                                            
	raid0: Components: /dev/wd0a /dev/wd1a                                                         
	raid0: Total Sectors: 1953260800 (953740 MB)                                                   
	dk0 at raid0: "root", 266240 blocks at 40, type: ffs                                           
	dk1 at raid0: "swap", 2097152 blocks at 266280, type: swap                                     
	dk2 at raid0: "var", 1048576 blocks at 2363432, type: ffs                                      
	dk3 at raid0: "usr", 67108864 blocks at 3412008, type: ffs                                     
	dk4 at raid0: "home", 1882739888 blocks at 70520872, type: ffs                                 
	boot device: dk0                                                                               
	root on dk0 dumps on dk1                                                                       
	mountroot: trying ffs...                                                                       
	root file system type: ffs                                                                     
	kern.module.path=/stand/evbarm/8.99.36/modules                                                 
	WARNING: clock lost 7038 days                                                                  
	WARNING: using filesystem time                                                                 
	WARNING: CHECK AND RESET THE DATE!  
	init: copying out path `/sbin/init' 11
	Tue Apr  9 07:19:11 GMT 2019

When using the stock SHEEVAPLUG kernel (version 8.99.36).

With my custom config kernel, I’m able to boot fine but system freezes after a couple of hours. And adding DIAGNOSTIC or DDB to this kernel (in order to help me find the issue), makes the kernel freeze at boot, like SHEEVAPLUG kernel.

How can I move forward to find the issue ? Any help appreciated :-)

Best,
jym