From: mtx <metux@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: unable to open initial console (ENODEV) (WAS: problem w/ kernel init (rootfs vs initial console / init process))
Date: Sun, 10 Sep 2017 17:02:56 +0200 [thread overview]
Message-ID: <74bc1cea-03e5-3c72-bdfd-b893587f2163@gmx.de> (raw)
In-Reply-To: <ed912df6-390f-989f-1ddc-7759a2989141@gmx.de>
On 10.09.2017 11:09, mtx wrote:
> it tries to open the initial console, before even attempt to mount the > root fs, which obviously is doomed to fail. (directly passing root=>
via cmdline - no initrd etc)
Solved it. For the record: the uart2 node was still disabled, so the
kernel did allocate a console for the port, but no tty_driver assigned.
tty_lookup_driver() (tty_io.c) is called on opening tty devices (such as
/dev/console). it asks console_device() (in printk.c), which scans the
consoles list for one with a tty_driver.
As my DT left the console's uart port disabled, the corresponding device
wasn't initialized, thus leaving the console w/o assigned tty_driver.
BTW: maybe we should think about some logic which spits out a warning,
or maybe implement an own special tty_driver for /dev/console, which
goes to the active console(s), just like printk() does.
--mtx
prev parent reply other threads:[~2017-09-10 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 9:09 problem w/ kernel init (rootfs vs initial console / init process) mtx
2017-09-10 15:02 ` mtx [this message]
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=74bc1cea-03e5-3c72-bdfd-b893587f2163@gmx.de \
--to=metux@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®