getty-serial@ttyLP0.service restarts frequently

Oct 30 14:31:28 colibri-vf kernel: random: nonblocking pool is initialized
Oct 30 14:31:29 colibri-vf login[377]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:29 colibri-vf login[377]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:31:31 colibri-vf login[377]: FAILED LOGIN (1) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:32 colibri-vf login[377]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:32 colibri-vf login[377]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:31:35 colibri-vf login[377]: FAILED LOGIN (2) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:36 colibri-vf login[377]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:38 colibri-vf login[377]: FAILED LOGIN (3) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:39 colibri-vf login[377]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:43 colibri-vf login[377]: FAILED LOGIN (4) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:44 colibri-vf systemd[1]: serial-getty@ttyLP0.service: Service has no hold-off time, scheduling restart.
Oct 30 14:31:44 colibri-vf systemd[1]: Stopped Serial Getty on ttyLP0.
Oct 30 14:31:44 colibri-vf systemd[1]: Started Serial Getty on ttyLP0.
Oct 30 14:31:46 colibri-vf login[388]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:46 colibri-vf login[388]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:31:50 colibri-vf login[388]: FAILED LOGIN (1) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:50 colibri-vf login[388]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:50 colibri-vf login[388]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:31:54 colibri-vf login[388]: FAILED LOGIN (2) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:55 colibri-vf login[388]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:31:57 colibri-vf login[388]: FAILED LOGIN (3) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:31:58 colibri-vf login[388]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:32:02 colibri-vf login[388]: FAILED LOGIN (4) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:32:02 colibri-vf login[388]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:32:06 colibri-vf login[388]: FAILED LOGIN (5) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:32:06 colibri-vf login[388]: TOO MANY LOGIN TRIES (5) on '/dev/ttyLP0' FOR 'UNKNOWN'
Oct 30 14:32:06 colibri-vf login[388]: pam_mail(login:session): user unknown
Oct 30 14:32:06 colibri-vf login[388]: pam_unix(login:session): close_session - error recovering username
Oct 30 14:32:06 colibri-vf login[388]: PAM 3 more authentication failures; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:32:06 colibri-vf login[388]: PAM service(login) ignoring max retries; 4 > 3
Oct 30 14:32:06 colibri-vf systemd[1]: serial-getty@ttyLP0.service: Service has no hold-off time, scheduling restart.
Oct 30 14:32:06 colibri-vf systemd[1]: Stopped Serial Getty on ttyLP0.
Oct 30 14:32:06 colibri-vf systemd[1]: Started Serial Getty on ttyLP0.
Oct 30 14:32:08 colibri-vf login[398]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:32:08 colibri-vf login[398]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:32:11 colibri-vf login[398]: FAILED LOGIN (1) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:32:12 colibri-vf login[398]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:32:12 colibri-vf login[398]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/ttyLP0 ruser= rhost=
Oct 30 14:32:14 colibri-vf login[398]: FAILED LOGIN (2) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:32:16 colibri-vf login[398]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:32:19 colibri-vf login[398]: FAILED LOGIN (3) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure
Oct 30 14:32:19 colibri-vf login[398]: pam_unix(login:auth): check pass; user unknown
Oct 30 14:32:22 colibri-vf login[398]: FAILED LOGIN (4) on '/dev/ttyLP0' FOR 'UNKNOWN', Authentication failure

And on what exact carrier board? Were/are you sending anything via that UART? You sure you did not simply run out of flash space? E.g. What does df say? Please attach the full boot log as a textual log file should you want us to look into it any further.

We are using our custom carrier board and running our application from SD Card.

root@colibri-vf:~# df
    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/root              7506808    371784   6747032   5% /
    devtmpfs                 52036         4     52032   0% /dev
    tmpfs                    60532         0     60532   0% /dev/shm
    tmpfs                    60532       260     60272   0% /run
    tmpfs                    60532         0     60532   0% /sys/fs/cgroup
    tmpfs                    60532         4     60528   0% /tmp
    tmpfs                    60532         0     60532   0% /var/volatile
    tmpfs                    12104         0     12104   0% /run/user/0
    root@colibri-vf:~#

Log files

Ok, that isn’t exactly the console boot log I asked for. Anyway. Did you by any chance modify e.g. the device tree in any way? How about U-Boot and/or the kernel boot arguments? Do you actually even have that LP0 UART? If not you would just need to disable resp. systemd service.

We have modified the device tree for gpio. Uboot for port setting and display configuration. We are using ttyLP0

Could you share all your changes in git diff format and serial boot log in a text file?
Thanks.

link text

Can someone update on the above git diff which has been attached

Thanks for the git diff. You still did not send the serial boot log.

Could you share the output of dmesg ( dmesg > dmesg.txt ) and output of ( journalctl -b )?

Thanks and best regards,
Jaski

The log_2019-10-30-09-06-44.txt files is the output of journatctl -b which has our program debug.

link text

Uploaded dmesg output

Thanks for the dmesg log.

[    1.552943]  mmcblk0: p1
[    1.561115] vf610-pinctrl 40048000.iomuxc: pin VF610_PAD_PTD4 already requested by 4002d000.dspi1; cannot claim for regulator-usbh-vbus
[    1.573548] vf610-pinctrl 40048000.iomuxc: pin-83 (regulator-usbh-vbus) status -22
[    1.581198] vf610-pinctrl 40048000.iomuxc: could not request pin 83 (VF610_PAD_PTD4) from group gpio_usb_vbus  on device 40048000.iomuxc
[    1.593591] reg-fixed-voltage regulator-usbh-vbus: Error applying setting, reverse things back

You make iomuxing errors. Could you correct them and check if you still have the issue?

Best regards,
Jaski

Please suggest how to do, we have provided the device tree diff file in the below link:
https://share.toradex.com/4unrak5psgt3pj1?direct