From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/systemd: fix "Timed out waiting for device /dev/console."
Date: Mon, 04 Mar 2019 22:32:37 +0100 [thread overview]
Message-ID: <871s3miave.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190304192547.23954-1-xruppen@gmail.com> (Xavier Ruppen's message of "Mon, 4 Mar 2019 20:25:47 +0100")
>>>>> "Xavier" == Xavier Ruppen <xruppen@gmail.com> writes:
> Buildroot built with systemd fails to open a login prompt on the
> serial port when /dev/console is specified as BR2_TARGET_GENERIC_GETTY_PORT
> (which is its default value):
> systemd[1]: dev-console.device: Job dev-console.device/start timed out.
> systemd[1]: Timed out waiting for device /dev/console.
> systemd[1]: Dependency failed for Serial Getty on console.
> systemd[1]: serial-getty at console.service: Job serial-getty at console.service/start failed with result 'dependency'.
> systemd[1]: dev-console.device: Job dev-console.device/start failed with result 'timeout'.
> systemd[1]: Reached target Login Prompts.
> systemd[1]: Reached target Multi-User System.
> According to this issue on Github [1], serial-getty at .service should
> not be instantiated on /dev/console, console-getty at .service should
> be used instead. This stems from the fact that there should be no
> dependency on /dev/console.
> [1] https://github.com/systemd/systemd/issues/10914
> Signed-off-by: Xavier Ruppen <xruppen@gmail.com>
Committed after adding the cleanups as suggested by Yann, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-03-04 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 19:25 [Buildroot] [PATCH v3 1/1] package/systemd: fix "Timed out waiting for device /dev/console." Xavier Ruppen
2019-03-04 21:09 ` Yann E. MORIN
2019-03-04 21:32 ` Peter Korsgaard [this message]
2019-03-17 22:14 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s3miave.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox