From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11766] New: Console (getty) issues with systemd
Date: Tue, 09 Apr 2019 13:01:26 +0000 [thread overview]
Message-ID: <bug-11766-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11766
Bug ID: 11766
Summary: Console (getty) issues with systemd
Product: buildroot
Version: 2019.02.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: isak.tjernberg at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7976
--> https://bugs.busybox.net/attachment.cgi?id=7976&action=edit
Comparison between console-getty.service contents between 2018.11 and 2019.02.1
When using an image built with Buildroot for the Raspberry Pi 3 (64 bit) using
systemd as init system, the serial console reached through 3 of the GPIO pins
reports various errors and is generally unstable (misses characters
sporadically). One common error I get printed is: "Inappropriate ioctl for
device" from Getty.
This is on version 2019.02.1. The same config works fine with Buildroot
2018.11.
The error/issues goes away if I replace the contents in the file
/etc/systemd/system/getty.target.wants/console-getty.service with the content
in the same file from the image built with version 2018.11.
I can attach one file only, so the file contains the contents both from version
2018.11 (working) and 2019.02.1 (not working).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-04-09 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 13:01 bugzilla at busybox.net [this message]
2019-05-02 14:32 ` [Buildroot] [Bug 11766] Console (getty) issues with systemd bugzilla at busybox.net
2019-05-02 14:33 ` bugzilla at busybox.net
2019-07-20 18:05 ` bugzilla at busybox.net
2019-07-21 19:16 ` bugzilla at busybox.net
2019-07-21 21:03 ` bugzilla at busybox.net
2019-09-29 15:50 ` bugzilla at busybox.net
2019-12-10 20:02 ` bugzilla at busybox.net
2019-12-10 21:00 ` Adam Duskett
2019-12-10 21:39 ` bugzilla at busybox.net
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=bug-11766-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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