Kernel doesn't boot after u-boot I2C device access

Hello all,
I try to read data from an I2C device in u-boot. Right now, I observe a issue in the current version of u-boot-socfpga:

When I boot the device without any I2C command in u-boot, the bootcmd is successfully and the Linux kernel starts.
When I just select the I2C Bus on the u-boot console with i2c dev 0 and then try to boot with run bootcmd the kernel dosen’t start and hangs on the output Starting kernel ...

The device which I use is an Arria10.

Does anyone know how to fix this issue or how to debug it? Right now, I’m quite confused and have no idea where to look in. Is it the u-boot dtb or Linux dtb? Reset sequence or clock configuration…? Or maybe just a bug in u-boot?

=> i2c dev 0
Setting bus to 0
I2C bus i2c@ffc02300 version 0x3132312a
=> run bootcmd
16197608 bytes read in 853 ms (18.1 MiB/s)
fpga - loadable FPGA image support

fpga [operation type] [device number] [image address] [image size]
fpga operations:
dump [dev] [address] [size] Load device to memory buffer
info [dev] list known device information
load [dev] [address] [size] Load device from memory buffer
loadb [dev] [address] [size] Load device from bitstream buffer (Xilinx only)
loadmk [dev] [address] Load device generated with mkimage
For loadmk operating on FIT format uImage address must include
subimage unit name in the form of addr:<subimg_uname>
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
235 bytes read in 4 ms (56.6 KiB/s)
1: Arria10 SOCDK SDMMC
Retrieving file: /extlinux/…/zImage
4636312 bytes read in 245 ms (18 MiB/s)
append: root=/dev/mmcblk0p3 rootwait rw earlycon console=ttyS0,115200 mem=1024M memmap=1024M$0x40000000
Retrieving file: /extlinux/…/c4brd_rev1_0.dtb
19054 bytes read in 6 ms (3 MiB/s)

Flattened Device Tree blob at 02000000

Booting using the fdt blob at 0x2000000
Loading Device Tree to 09ff8000, end 09fffa6d … OK

Starting kernel …