Toradex iMX6 stops on Starting kernel

After some time, the kernel stopped running.
After re-uploading it starts correctly.
What could be the reason?

Industrial temperature grade DDR3 timings, 64bit bus width.
Trying to boot from MMC1

U-Boot 2016.11.DW RG KRG 02-00002-gcfd3379-dirty (Apr 24 2018 - 11:32:22 +0200)

CPU:   Freescale i.MX6DL rev1.3 at 792 MHz
Reset cause: POR
I2C:   ready
DRAM:  512 MiB
PMIC:  device id: 0x10, revision id: 0x21, programmed
auto-detected panel vga-rgb
Display: vga-rgb (640x480)
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX6 DualLite 512MB IT V1.1A, Serial# 10500816
Net:   using PHY at 0
Hit any key to stop autoboot:  0 
Booting from internal eMMC chip...
reading imx6dl-colibri-eval-v3.dtb
43156 bytes read in 19 ms (2.2 MiB/s)
reading uImage
4997304 bytes read in 154 ms (30.9 MiB/s)
## Booting kernel from Legacy Image at 11000000 ...
   Image Name:   Linux-3.14.28-00020-g83aea6c-dir
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4997240 Bytes = 4.8 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 12000000
   Booting using the fdt blob at 0x12000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 12000000, end 1200d893

Starting kernel ...

What exact software versions of things are you talking about?

I am experiencing this on imx7 1G with torizon’s latest warrior branch commit.
We use a custom designed Carrier Board with the reference design of the 3.3V rail. The voltage is oscilloscoped stable and not supicious in switching moments.

The OS is slightly adopted via device tree gpio modifications.

I have seen this on 3 out of 40 modules occouring sporadically during reboots under operation.
Onece happend the module cannot be reactivated.

Is anything known to this behavior?

How would i debug further?

Is this SW or HW related?

hi @m.telian

Could you ask a new question, please? Thanks.