Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.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:56:31 -0700	[thread overview]
Message-ID: <4D42F53F.1010201@mlbassoc.com> (raw)
In-Reply-To: <20110128165100.656AAD42A99@gemini.denx.de>

[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]

On 01/28/2011 09: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.
>
>> 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.

Wolfgang has it spot-on - both the console login and dbus are
fighting over the console device.

I've been using the equivalent of this patch for months and it
solves the problem just fine.  (Sorry I didn't report it, it
wasn't high on my list)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: no-stdin-for-dbus.patch --]
[-- Type: text/plain, Size: 651 bytes --]

Disconnect console from dbus - otherwise, serial console is unusable
if X session is running.

diff -ur x11-common.ORIG/etc/X11/Xsession x11-common/etc/X11/Xsession
--- x11-common.ORIG/etc/X11/Xsession	2010-08-06 06:43:51.000000000 -0600
+++ x11-common/etc/X11/Xsession	2010-07-23 12:12:00.000000000 -0600
@@ -2,7 +2,7 @@
 
 if [ -x /usr/bin/dbus-launch ]; then
     # As this is the X session script, always start a new DBus session.
-    eval `dbus-launch --sh-syntax --exit-with-session`
+    eval `dbus-launch --sh-syntax --exit-with-session </dev/null`
     echo "D-BUS per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
 fi

  reply	other threads:[~2011-01-28 16:56 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 [this message]
2011-01-28 17:51             ` Richard Purdie
2011-01-28 17:16           ` Darren Hart
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=4D42F53F.1010201@mlbassoc.com \
    --to=gary@mlbassoc.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