From: Darren Hart <dvhart@linux.intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org
Subject: Re: Serial console unusable with poky-image-sdk
Date: Fri, 28 Jan 2011 09:16:33 -0800 [thread overview]
Message-ID: <4D42F9F1.3020002@linux.intel.com> (raw)
In-Reply-To: <20110128165100.656AAD42A99@gemini.denx.de>
On 01/28/2011 08:51 AM, Wolfgang Denk wrote:
> Dear Darren Hart,
>
> In message<4D42F269.1080005@linux.intel.com> you wrote:
>>
>> The serial console would show all the output of the boot process and
>> then present a getty. It would accept my login and my password, but as
>> soon as I was logged in, things went weird. Only every Nth character I
>> typed made it to the console, where N was somewhere between 2 and 30.
>
> Indeed. And the reason for this behaviour is that you have two
> processes reading from the console, so it depends on the scheduling
> which of hem receives which characters.
>
>> I believe this had something to do with the automatic consoles the
>> kernel will setup based on the console= parameters. By default, the last
>
> No, it does not. You can test it by shutting down X11 (try:
> "/etc/init.d/xserver-nodm stop"); this will also terminate the
> dbus-launch process, and your login shell immediately works fine.
>
> Or try out the patch I posted.
I'm not running X11, this is just a poky-image-minimal.
>
>> What I haven't been able to explain yet is why just omitting the getty
>> from the tty doesn't result in console on the serial port due to the
>> kernel's automatic console thing. So clearly there are some gaps in my
>> explanation here, but please try this approach and let me know what your
>> results are. Based on that, we can dig a bit more and figure out how to
>> best setup the console= directives on the default images.
>
> THere is no problem with the console= settings. It's two processes
> reading from a single input stream. This can never work. Try it ut if
> you don't believe me.
Agreed on the two processes thing, that's clear. I believe the console=
settings impact which processes are started and which read from which
console devices.
And again, I can't try your patch, because I'm not running X.
Perhaps we are seeing similar problems caused by different things.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-01-28 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 11:11 Serial console unusable with poky-image-sdk Wolfgang Denk
2011-01-27 11:42 ` Wolfgang Denk
2011-01-27 22:33 ` Darren Hart
2011-01-28 7:05 ` Wolfgang Denk
2011-01-28 16:44 ` Darren Hart
2011-01-28 16:51 ` Wolfgang Denk
2011-01-28 16:56 ` Gary Thomas
2011-01-28 17:51 ` Richard Purdie
2011-01-28 17:16 ` Darren Hart [this message]
2011-01-28 17:20 ` Richard Purdie
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=4D42F9F1.3020002@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=wd@denx.de \
/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