LS1043A-RGW boot failure

[tmorrison]

We have a custom board - largely based upon the NXP LS1043A-RGW Development board

We are using the LSDK 18.03 with some patches to be able to customize it. We are having

some problems in several different areas, but I have patched around those to try to get linux

to boot all the way.

The LSDK is flex-builder based and I have built a firmware,  bootpartition, and rootfs. I load

that onto a sd card, and try to boot from that SD Card. I get this at the end:

[    3.411691] EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities
[    3.453190] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[    3.461292] VFS: Mounted root (ext4 filesystem) on device 179:3.
[    3.468133] devtmpfs: error mounting -2
[    3.472210] Freeing unused kernel memory: 832K
[    3.476726] Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[    3.490883] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.14.16-dirty #6
[    3.497397] Hardware name: LS1043A RGW Board (DT)
[    3.502089] Call trace:
[    3.504531] [<ffff000008088c70>] dump_backtrace+0x0/0x370
[    3.509920] [<ffff000008088ff4>] show_stack+0x14/0x20
[    3.514963] [<ffff000008b0e380>] dump_stack+0x9c/0xbc
[    3.520004] [<ffff0000080c7b18>] panic+0x11c/0x28c
[    3.524785] [<ffff000008b2093c>] kernel_init+0xec/0x100
[    3.529999] [<ffff000008084be0>] ret_from_fork+0x10/0x18
[    3.535301] SMP: stopping secondary CPUs
[    3.539215] Kernel Offset: disabled
[    3.542692] CPU features: 0x002004
[    3.546082] Memory Limit: none
[    3.549129] ---[ end Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

I am assuming that the lsdk shouldn't have any of the problems that Linux Documentation/admin-guide/init.rst

[tmorrison]

can you please answer my questions I have asked about

[bpe]

Your recent inputs are not quite inline with the oirginal problem description. I particular, you are running fsck over /dev/sdd4 which should be a HDD based on it's name, but the problem is,  according to what you wrote earlier,  with a bootable SD card. fsck can help, but only if used in the proper way: if you can boot your system with a tinydistro ramdisk, try mounting the problematic partition by hand and running fsck on the target.

Regards,

Platon

[tmorrison]

I will try this test soon!

[bpe]

Your Linux cannot mount the root filesystem due to certain FS feature
incompatibility. It is important how you format your SD card partitions
to put the images created by flex-builder. Use flex-installer from the
same LSDK release to populate your boot SD card. If you prefer to
format it by hand, look at flex-installer code, procedure partition_format_storage_device()
for the mkfs.ext4  invocation options. Note that you are
working with a pretty much obsolete LSDK version. You need to use
Ubuntu 16.04 on your build host for everything to work smoothly. Also, if it
is a heavily customized kernel, compare the LSDK default kernel configuration
with your one to ensure all necessary filesystem support options are
enabled.

Please keep in mind, that we can provide a very limited support to
historical (l)SDK releases. If the suggestions above do not help,
our recommendation is to move to the most recent LSDK.

Have a great day,
Platon

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[tmorrison]

Hi Platon,

Thank you for your quick response.

I am using the flex-installer that came with this LSDK.

I am sorry that this was NOT clear.

I will look at hand formatting.

I am using Ubuntu 18.04 because that was required for some of

the other LSDKs that I've unsuccessfully had no luck getting it to

work with a LS1043A-RGW.

I am not sure how to "downgrade" my Ubuntu to support this?

In addition, I am using this version of the LSDK because I was given

patches from you guys (NXP/Freescale) that explicitly patch this version

of LSDK to support the LS1043A-RGW BSP. There are no supported

patches for newer LSDK's - I certainly would use them if I could.

I will update after I try hand formatting.

Tom

[tmorrison]

Hi,

I compared the flex-installer for the newest SDK with this - and there was one parameter I added.

Still no luck....

I have a couple more questions about this:

It says here that it successfully mounted it:

  [    3.637912] EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities
  [    3.673534] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
  [    3.681636] VFS: Mounted root (ext4 filesystem) on device 179:3.

Why it is trying to mount as ext3 first, I also did an e2fsck on this partition:

  tom@newSNIPC:~$ sudo e2fsck /dev/sdd4
  e2fsck 1.44.1 (24-Mar-2018)
  system: clean, 71311/1479856 files, 645570/5912960 blocks

So, I am confused why it is having an issue. There is a /sbin/init (points to /lib/systemd/systemd)

Thanks in advance.

Tom

[tmorrison]

I don't think this is answered completely - still not working for me - and I have verified everything I can.