From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: serial console slow
Date: 9 Nov 2001 11:16:35 -0800 [thread overview]
Message-ID: <9sha2j$l5l$1@cesium.transmeta.com> (raw)
In-Reply-To: <20011109102140.A29288@elf.ucw.cz>
Followup to: <20011109102140.A29288@elf.ucw.cz>
By author: root <root@Elf.ucw.cz>
In newsgroup: linux.dev.kernel
>
> Hi!
>
> > I tried to boot my kernel using the serial console, using the
> > console=ttyS0,115200 (it does the same thing with 9600) ... it work great
> > until :
> >
> > Freeing unused kernel memory: 36k freed
> > serial console detected. Disabling virtual terminals.
> > console=/dev/ttyS0
> >
> > At this point the output of the serial line slow down dramaticly ... almost
> > to a halt ... I get 1 line every 30 seconds !!!
> >
> > why is this slow down occuring ? the part which is 100% kernel is going fast
> > and ok, but when it become console related ... it slows down ?
>
> Serial just got its control signals (it is now *userland* writing, and
> userland honours them), plus userland is probably opening/closing
> serial all the time. Bad.
> Pavel
I have had much better luck talking to /dev/console in userland.
IMNSHO this should *always* work; anything else is broken.
/dev/console currently *IS* broken to some degree, multi-console
hasn't worked properly for a long time, and you don't get job control
running of it because it isn't a tty, but I think it's a lot less
broken than things like the above...
(And dammit, I really would like to see console=tty0 console=ttyS0 to
actually give me both consoles -- in userland *and* in the kernel...)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-11-09 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 9:21 root
2001-11-09 19:16 ` H. Peter Anvin [this message]
2001-11-09 19:25 ` Miquel van Smoorenburg
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='9sha2j$l5l$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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®