Compiler/TDA2SA: Created slice system-systemd\x2dfsck.slice

user6229311

Part Number: TDA2SA

Tool/software: TI C/C++ Compiler

Hi all,

I follow the instructions to build the yocto system https://processors.wiki.ti.com/index.php?title=Processor_SDK_Linux_Automotive_Software_Developers_Guide&oldid=225388#Building_Yocto_Filesystem,(shown as below pic.) which base on vsdk3.06, the file system was loaded by the kernel which is provided by vsdk3.06,but when "Created slice system-systemd\x2dfsck.slice", it spent 5s, I don't know what happen, I want to avoid this step, could anyone tell me what is this"Created slice system-systemd\x2dfsck.slice", could it not be done?The complete log here/cfs-file/__key/communityserver-discussions-components-files/791/start_5F00_log.txt

20200227_21:24:34[ OK ] Reached target System Time Synchronized.
20200227_21:24:35[ OK ] Started Network Name Resolution.
20200227_21:24:35[ OK ] Started TI IPC Daemon.
20200227_21:24:38[ OK ] Created slice system-systemd\x2dfsck.slice.
20200227_21:24:38 Starting File System Check on /dev/mmcblk0p1...
20200227_21:24:38 Starting File System Check on /dev/mmcblk0p3...
20200227_21:24:38[ OK ] Reached target Network.
20200227_21:24:38 Starting Permit User Sessions...
20200227_21:24:38[ OK ] Reached target Host and Network Name Lookups.
20200227_21:24:38 Starting Avahi mDNS/DNS-SD Stack...

over 6 years ago

0 Ramprasad over 6 years ago

TI__Mastermind 30480 points

Hi Huang,

Add the statement fsck.mode=skip code in kernel command line arguments in uenv.txt and check.

This should resolve the issue.

Thanks

RamPrasad

0 user6229311 over 6 years ago in reply to Ramprasad

Expert 1805 points

Hi RamPrasad,

Thanks for your help, I met another issue https://e2e.ti.com/support/processors/f/791/t/884024,is it the same as this issue?

Regards

Jason

0 user6229311 over 6 years ago in reply to Ramprasad

Expert 1805 points

Hi RamPrasad,

Now I use the MLO start kernel directly(Falcon mode), so I do as follows:

host # fdtput -v -t s arch/arm/boot/dts/dra7-evm-infoadas.dtb "/chosen" bootargs "fsck.mode=skip loglevel=0 console=ttyO0,115200n8 vram=16M root=PARTUUID=01669d08-02 rw rootwait ip=none cma=64M"

soyu # env default -a; setenv dfu_alt_info ${dfu_alt_info_emmc}; dfu 0 mmc 1

setenv falcon_image_file spl-os-image
setenv falcon_args_file spl-os-args
setenv boot_os 1
saveenv

but it doesn't work, it still print:

[ OK ] Created slice system-systemd\x2dfsck.slice.
Starting File System Check on /dev/mmcblk0p1...
Starting File System Check on /dev/mmcblk0p3...
Starting weston.service...
[ OK ] Reached target Network.
Starting Permit User Sessions...
[ OK ] Reached target Host and Network Name Lookups.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started File System Check on /dev/mmcblk0p1.
[ OK ] Started File System Check on /dev/mmcblk0p3.

Regards

Jason

0 Ramprasad over 6 years ago in reply to user6229311

TI__Mastermind 30480 points

Hi Jason,

I am not at all observing this trace during boot

20200227_21:24:38[ OK ] Created slice system-systemd\x2dfsck.slice.

Which device you are using?

For cascade-radar usecase we had seen such issues but adding fsck.mode=skip in boot Args resolved the issue.

Thanks

RamPrasad

0 user6229311 over 6 years ago in reply to Ramprasad

Expert 1805 points

tda2x

0 Ramprasad over 6 years ago in reply to user6229311

TI__Mastermind 30480 points

Can you confirm if you are using cascade-radar usecase?

0 user6229311 over 6 years ago in reply to Ramprasad

Expert 1805 points

I just run the kernel, not the app, when the kernel loaded the file system, it printed this " Created slice system-systemd\x2dfsck.slice.".

Processors

Processors forum

Compiler/TDA2SA: Created slice system-systemd\x2dfsck.slice