On Tue, Nov 7, 2017 at 5:48 PM, Yann Le Mouel <[email protected]> wrote:
> > *Nov 06 09:37:02 systemd[1]: [email protected] > <[email protected]> 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]: [email protected] <[email protected]> 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]: [email protected] > <[email protected]> holdoff time over, scheduling restart.* > > *Nov 06 09:37:02 systemd[1]: start request repeated too quickly for > [email protected] <[email protected]>* > > *Nov 06 09:37:02 systemd[1]: Failed to start Serial Getty on ttyS1.* > > *Nov 06 09:37:02 systemd[1]: Unit [email protected] > <[email protected]> entered failed state.* > > *Nov 06 09:37:02 systemd[1]: [email protected] > <[email protected]> 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 <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
