From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8746] New: At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error
Date: Thu, 03 Mar 2016 22:09:59 +0000 [thread overview]
Message-ID: <bug-8746-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8746
Bug ID: 8746
Summary: At startup system stops with 'cannot set terminal
process group (-1): Inappropriate ioctl for device'
error
Product: buildroot
Version: 2015.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: rdbirt at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
After updating from buildroot 2015.02 I am seeing this error on system startup:
.
.
.
EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:1.
devtmpfs: mounted
Freeing unused kernel memory: 228K (c07db000 - c0814000)
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
sh-4.3#
The same error occurs with 2016.02-rc2. I am running this on a Wandboard quad
with kernel 3.18.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-03-03 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:09 bugzilla at busybox.net [this message]
2016-03-08 8:27 ` [Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error bugzilla at busybox.net
2016-03-09 1:16 ` bugzilla at busybox.net
2016-03-09 1:17 ` bugzilla at busybox.net
2016-03-10 14:55 ` bugzilla at busybox.net
2016-03-10 17:36 ` bugzilla at busybox.net
2016-03-10 20:34 ` 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-8746-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.