[meta-freescale] Kernel panic on mvme2500 (Freescale p2020 QorIQ e500v2 ) with fresh yocto built core-image-minimal

[tjscheffel at bitulator.nl]

Hi meta-freescale gurus,

I would like to get in contact with people running a fresh yocto-built 
Linux on a mvme2500 (Freescale p2020 QorIQ e500v2).
Reason is that I have freshly built and tested a core-image-minimal on 
the mvme2500 and it gets a kernel panic apparently upon some Machine 
Check.
Comparing the startup of this version with a working one I built back in 
2012 I see that there is something different in the PCI department:

< …
PCI: Probing PCI hardware
fsl-pci ffe09000.pcie: PCI host bridge to bus 9000:00
pci_bus 9000:00: root bus resource [io  0x0000-0xffff]
pci_bus 9000:00: root bus resource [mem 0xa0000000-0xbfffffff] (bus 
address [0xe0000000-0xffffffff])
pci_bus 9000:00: root bus resource [bus 00-ff]
pci 9000:01:00.0: reg 0x24: initial BAR value 0xa0000000 invalid
…>

Fairly near the end of startup the kernel panic looks like:
<…
Disabling lock debugging due to kernel taint
Machine check in kernel mode.
Caused by (from MCSR=10008): Bus - Read Data Bus Error
Kernel panic - not syncing: Unrecoverable Machine check
CPU: 1 PID: 1 Comm: swapper/0 Tainted: G   M              
4.19.26+gc0c214110624 #1
Call Trace:
…>

After Call Trace: the board reboots.
Tested this on two different boards that both function OK with an old 
distribution I put together in 2012, and both show the same behavior.

So if someone has experienced this on a similar board I would very much 
like to know how to get rid of some panic.

Thanks for your time!

Best regards,

Teun Scheffel