• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 573 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMDSSK3358: Flood with serial-getty@ttyS3.service in journal

Taris
Prodigy 20 points

Part Number: TMDSSK3358

Hello,

I'm using AM335X Starter Kit. I have created new SD card image with "ti-processor-sdk-linux-am335x-evm-06.01.00.08" and have started in my start kit. I've noticed with "journalctl: that service "serial-getty@ttyS3.service" spams in a log:

..........................

Oct 19 16:17:43 am335x-evm systemd[1]:serial-getty@ttyS3.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Oct 19 16:17:43 am335x-evm systemd[1]: serial-getty@ttyS3.service: Scheduled restart job, restart counter is at 18.
Oct 19 16:17:43 am33-evm systemd[1]: Stopped Serial Getty on ttyS3.
Oct 19 16:17:43 am335x-evm systemd[1]: Started Serial Getty on tt3.

...........................

How can I stop a flood journal from this service ? For what purpose does this service use if start kit does not have external serial port (except through USB FTDI chip) .

Where could I get newest documentation (for sdk-linux-am335x-evm-06.01.00.08) related with management of services (starting on boot time, adding or removing from boot time and etc.)?

  • 0
    TI__Guru**** 168261 points

    Hi,

    I will check with my Starter Kit to understand why the getty on ttyS3 generate log spams, and get you back.

    The Processor SDK linux uses systemd managing services, there are plenty of information of using systemd on internet.

  • 0
    TI__Guru**** 168261 points

    Hi,

    I am unable to reproduce the ttyS3 log spam issue with Processor SDK Linux v6.1.0.8 on Starter Kit. I don't see the ttyS3 systemd log messages in any log file under /var/log/. uart3 which is corresponding to ttyS3 should be disabled in device tree.

    Anyway, please try the following command to stop ttyS3 gettty service and reboot the board to see if the issue still happens.

    root@am335x-evm:~# systemctl disable serial-getty@ttyS3.service

  • 0 in reply to Bin Liu
    Prodigy 20 points

    Thanks it helps