U-Boot 2020.10-53187-g0238401ae4 (Feb 28 2022 - 08:01:36 -0800), Build: jenkins-uboot_v2020.10-195

CPU:   i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: nitrogen6_max
I2C:   ready
DRAM:  3.8 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from SPIFlash...
SF: Detected gd25q16 with page size 256 Bytes, erase size 4 KiB, total 2 MiB
OK
Display: lvds:XGA (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   Micrel ksz9021 at 6
FEC [PRIME], usb_ether
Hit any key to stop autoboot:  0
gpio: pin 125 (gpio 125) value is 1
   Warning: value of pin is still 0
gpio: pin 112 (gpio 112) value is 0
checking mmc 0:1 for clearview.dtb
clearview.dtb found!
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
5598 bytes read in 1688 ms (2.9 KiB/s)
## Executing script at 10008000
Failed to load 'uEnv.txt'
54711 bytes read in 436 ms (122.1 KiB/s)
only CEA modes allowed on HDMI port
----------- trying to load /initrd.img
6574831 bytes read in 1586 ms (4 MiB/s)
6048768 bytes read in 1893 ms (3 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x5c4c00 ]
## Flattened Device Tree blob at 13000000
   Booting using the fdt blob at 0x13000000
   Using Device Tree in place at 13000000, end 13010fff

Starting kernel ...

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_NANDF_CS2 already requested by 20e0000.iomuxc; cannot claim for regulators:regulator@4
imx6q-pinctrl 20e0000.iomuxc: pin-187 (regulators:regulator@4) status -22
imx6q-pinctrl 20e0000.iomuxc: could not request pin 187 (MX6Q_PAD_NANDF_CS2) from group reg-wlan-engrp  on device 20e0000.iomuxc
reg-fixed-voltage regulators:regulator@4: Error applying setting, reverse things back
rtc-m41t80 0-0068: Oscillator failure, data is invalid.
imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_NANDF_CS3 already requested by 20e0000.iomuxc; cannot claim for bt_rfkill
imx6q-pinctrl 20e0000.iomuxc: pin-188 (bt_rfkill) status -22
imx6q-pinctrl 20e0000.iomuxc: could not request pin 188 (MX6Q_PAD_NANDF_CS3) from group bt-rfkillgrp  on device 20e0000.iomuxc
rfkill_gpio bt_rfkill: Error applying setting, reverse things back
rtc-m41t80 0-0068: Oscillator failure, data is invalid.
rtc-m41t80 0-0068: hctosys: unable to read the hardware clock
Loading, please wait...
starting version 232
xhci_hcd 0000:01:00.0: firmware request for uPD72020x.mem failed (-2).
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
sys-1Ah: recovering journal
JBD2: Invalid checksum recovering block 483 in log
JBD2: Invalid checksum recovering block 518 in log
JBD2: Invalid checksum recovering block 634 in log
JBD2: Invalid checksum recovering block 3175 in log
JBD2: Invalid checksum recovering block 699 in log
JBD2: Invalid checksum recovering block 698 in log
JBD2: Invalid checksum recovering block 691 in log
JBD2: Invalid checksum recovering block 692 in log
JBD2: Invalid checksum recovering block 693 in log
JBD2: Invalid checksum recovering block 694 in log
JBD2: Invalid checksum recovering block 695 in log
JBD2: Invalid checksum recovering block 696 in log
JBD2: Invalid checksum recovering block 697 in log
JBD2: Invalid checksum recovering block 3474 in log
JBD2: Invalid checksum recovering block 3475 in log
JBD2: Invalid checksum recovering block 3484 in log
JBD2: Invalid checksum recovering block 690 in log
JBD2: Invalid checksum recovering block 689 in log
JBD2: Invalid checksum recovering block 688 in log
JBD2: Invalid checksum recovering block 612 in log
JBD2: Invalid checksum recovering block 644 in log
JBD2: Invalid checksum recovering block 660 in log
JBD2: Invalid checksum recovering block 661 in log
JBD2: Invalid checksum recovering block 667 in log
JBD2: Invalid checksum recovering block 599 in log
JBD2: Invalid checksum recovering block 502 in log
JBD2: Invalid checksum recovering block 510 in log
JBD2: Invalid checksum recovering block 512 in log
JBD2: Invalid checksum recovering block 538 in log
JBD2: Invalid checksum recovering block 826 in log
JBD2: Invalid checksum recovering block 497 in log
JBD2: Invalid checksum recovering block 498 in log
JBD2: Invalid checksum recovering block 499 in log
JBD2: Invalid checksum recovering block 501 in log
JBD2: Invalid checksum recovering block 491 in log
JBD2: Invalid checksum recovering block 483 in log
JBD2: Invalid checksum recovering block 486 in log
JBD2: Invalid checksum recovering block 487 in log
JBD2: Invalid checksum recovering block 488 in log
JBD2: Invalid checksum recovering block 489 in log
JBD2: Invalid checksum recovering block 490 in log
JBD2: Invalid checksum recovering block 3477 in log
JBD2: Invalid checksum recovering block 484 in log
JBD2: Invalid checksum recovering block 485 in log
JBD2: Invalid checksum recovering block 486 in log
JBD2: Invalid checksum recovering block 487 in log
JBD2: Invalid checksum recovering block 491 in log
JBD2: Invalid checksum recovering block 488 in log
JBD2: Invalid checksum recovering block 489 in log
JBD2: Invalid checksum recovering block 490 in log
JBD2: Invalid checksum recovering block 637 in log
JBD2: Invalid checksum recovering block 3124 in log
JBD2: Invalid checksum recovering block 3470 in log
JBD2: Invalid checksum recovering block 3471 in log
JBD2: Invalid checksum recovering block 3472 in log
JBD2: Invalid checksum recovering block 3478 in log
JBD2: Invalid checksum recovering block 502 in log
JBD2: Invalid checksum recovering block 503 in log
JBD2: Invalid checksum recovering block 504 in log
JBD2: Invalid checksum recovering block 506 in log
JBD2: Invalid checksum recovering block 507 in log
JBD2: Invalid checksum recovering block 509 in log
JBD2: Invalid checksum recovering block 510 in log
JBD2: Invalid checksum recovering block 2833 in log
JBD2: Invalid checksum recovering block 513 in log
JBD2: Invalid checksum recovering block 514 in log
JBD2: Invalid checksum recovering block 515 in log
JBD2: Invalid checksum recovering block 516 in log
JBD2: Invalid checksum recovering block 517 in log
JBD2: Invalid checksum recovering block 518 in log
Journal checksum error found in sys-1Ah
sys-1Ah was not cleanly unmounted, check forced.
sys-1Ah: 85231/477120 files (0.1% non-contiguous), 691454/1952869 blocks
fsck exited with status code 1
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... Warning: overlayroot: configuring overlayroot with driver=overlay mode=tmpfs opts='' per /dev/mmcblk0p1/etc/overlayroot.conf
Success: overlayroot: configured root with 'tmpfs' using overlay per /dev/mmcblk0p1/etc/overlayroot.conf
done.

Welcome to Debian GNU/Linux 9 (stretch)!