What do repeated journaling and getty services mean at startup?

Hi,
I'm working on an OMAP-L138 ARM processor with Linux installed. My issue is, when Linux boots up, I get the following messages at console.

Starting Journal Service...
Started Journal Service [ OK ]
Starting Journal Service...
Started Journal Service [ OK ]
Starting Journal Service...
Started Journal Service [ OK ]
Starting Journal Service...
Started Journal Service [ OK ]
Starting Journal Service...
Started Journal Service [ OK ]
Starting Getty on tty1...
Started Getty on tty1 [ OK ]
Stopping Getty on tty1...
Starting Getty on tty1...
Started Getty on tty1 [ OK ]
Stopping Getty on tty1...
Starting Getty on tty1...
Started Getty on tty1 [ OK ]
Stopping Getty on tty1...
Starting Getty on tty1...
Started Getty on tty1 [ OK ]

Journaling and getty services appear to be repeatedly restarted during startup. Is this expected? If not, how can I make these services start only once so that the boot process gets faster?

Thanks in advance,
OkCalis

Generally seeing repeated starts indicates the previous start failed or died and it has been told to start over each time it dies (respawn). Usuually in such a scenario the systems resources are being used so heavily you can't do anything else. Or alternatively you only have a console and can't get anything done because of the repeated messages preventing meaningful interaction with the screen.

You'd have to try booting into single user to see if you can find out why that's failing and address it before booting back to multiuser. Not sure how to do that on your ARM however.

get familiar with systemd.
start by looking at the journal:

journalctl

you might need to enable persistent journaling first.