On Tue, Mar 5, 2019 at 3:32 PM Thierry Reding <thierry.reding@xxxxxxxxx> wrote: > > One thing besides memory timings in BCT that comes to mind that could be > causing memory corruption are power supplies. Are you sure they're all > correctly configured and enabled as required? This part is 100% same as the Jetson TK1 on hardware end. And in device tree, the node 'vdd_1v35_lp0: sd2' has already 'regulator-always-on' property. We also tried once by using oscilloscope to check if the power drops/fluctuates during operation but noticed that DDR chips were getting stable power. > Does the upstream kernel and DTB boot reliably, even if it doesn't get > you to a login prompt? Or does it also behave erratically like the > downstream kernel and DTB that you have? 2 out of 10 times it behaved erratically, i.e. one time it stuck at 'Starting kernel ...' and the other time it stuck after following prints: Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.0.0-rc8-next-20190304-dirty (teresol@ubuntu) (gcc version 6.1.1 20160711 (Linaro GCC 6.1-2016.08)) #2 SMP PREEMPT Tue Mar 5 02:15:14 PST 2019 [ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: NVIDIA Tegra124 Jetson TK1 [ 0.000000] earlycon: uart0 at MMIO 0x70006300 (options '115200n8') [ 0.000000] printk: bootconsole [uart0] enabled [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 64 MiB at 0xac000000
