[systemd-devel] Serial console issue.

[Mantas Mikulėnas]

On Tue, Nov 7, 2017 at 5:48 PM, Yann Le Mouel <yann at lemouel.ch> wrote:

>
> *Nov 06 09:37:02 systemd[1]: serial-getty at ttyS1.service
> <serial-getty at ttyS1.service> holdoff time over, scheduling restart.*
>
> *Nov 06 09:37:02 systemd[1]: Started Serial Getty on ttyS1.*
>
> *Nov 06 09:37:02 systemd[1]: Starting Serial Getty on ttyS1...*
>
> *Nov 06 09:37:02 systemd[1]: getty at ttyS1.service <getty at ttyS1.service> has
> no holdoff time, scheduling restart.*
>
> *Nov 06 09:37:02 systemd[1]: Started Getty on ttyS1.*
>
> *Nov 06 09:37:02 systemd[1]: Starting Getty on ttyS1...*
>
> *Nov 06 09:37:02 systemd[1]: serial-getty at ttyS1.service
> <serial-getty at ttyS1.service> holdoff time over, scheduling restart.*
>
> *Nov 06 09:37:02 systemd[1]: start request repeated too quickly for
> serial-getty at ttyS1.service <serial-getty at ttyS1.service>*
>
> *Nov 06 09:37:02 systemd[1]: Failed to start Serial Getty on ttyS1.*
>
> *Nov 06 09:37:02 systemd[1]: Unit serial-getty at ttyS1.service
> <serial-getty at ttyS1.service> entered failed state.*
>
> *Nov 06 09:37:02 systemd[1]: serial-getty at ttyS1.service
> <serial-getty at ttyS1.service> failed.*
>
>
>
You have two services (getty@ and serial-getty@) fighting over the tty
device. Start by disabling the former.

(Actually, since you're getting dmesg output to the serial console, you
might even have a *third* service, console-getty, doing the same...)

-- 
Mantas Mikulėnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20171108/ee437751/attachment.html>