LKML Archive on
help / color / mirror / Atom feed
From: David Lang <>
To: Andy Kennedy <>
Subject: Re: Serial console issues.
Date: Mon, 12 Feb 2007 12:56:21 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0702121255100.6630@qynat.qvtvafvgr.pbz> (raw)
In-Reply-To: <>

On Mon, 12 Feb 2007, Andy Kennedy wrote:

> For those of you who are on BusyBox's mailing list, you've already seen this 
> -- I was sent here for help.
> Specs:
> Linux:  2.6.18
> Bootloader:  SysLinux
> Init:  BusyBox (ver 1.4.0) init.
> Kernel command line: console=ttyS0,115200,n,8,1
> System: VersaLogic 568 (STD80/STD32 Bus, i386 based computer)
> Issue:  Booting on "System" I get perfect printk's to the serial console. 
> When the init takes over (from within an initrd), the console begins to miss 
> characters.  I can still send write commands through the console, however, 
> the output of these commands is garbled.  The really odd part is when the 
> init releases control (is killed by Linux), or when a printk is issued, the 
> console prints perfectly again.  The next really strange part about this is 
> that changing "System" to my laptop -- no problems PERIOD. 
> The BusyBox list directed me to LKML as this is a wider base of users that 
> may have experienced the same problem and could provide me an answer.

I've seen this happen when you accidently have multple programs attached to the 
same console (even with the text-mode vga consoles)

double check that nothing else is trying to use that serial port

David Lang

  reply	other threads:[~2007-02-12 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 20:39 Andy Kennedy
2007-02-12 20:56 ` David Lang [this message]
2007-02-13 20:20   ` Andy Kennedy
2007-02-14 23:11 akennedy
2007-02-15  0:24 ` Alan
2007-02-15  0:39 akennedy
2007-02-15 10:49 ` Russell King

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0702121255100.6630@qynat.qvtvafvgr.pbz \ \ \ \
    --subject='Re: Serial console issues.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).