From: foo@porto.bmb.uga.edu
To: linux-kernel@vger.kernel.org
Subject: Re: more about serial console
Date: Tue, 15 Jun 2004 14:42:29 -0400 [thread overview]
Message-ID: <20040615184229.GA13604@porto.bmb.uga.edu> (raw)
In-Reply-To: <20040615000436.GA12516@porto.bmb.uga.edu>
On Mon, Jun 14, 2004 at 08:04:36PM -0400, foo@porto.bmb.uga.edu wrote:
> The other weird thing I have seen is with the serial console. After
> init loads the net bonding module and the network comes up, the serial
> console output stops, as though I had typed ^s. If I type a character
> (doesn't seem to matter what), instead of that character printing I see
> the next character of console output. I have to hold down a key for a
> few seconds to get the next few lines of output, then it starts printing
> on its own again. I've seen this with 2.6.7-rc3-bk4 and 2.6.6, not with
> 2.6.5 (I booted 2.6.6 by accident yesterday, I don't know how it does
> with NFS).
More experience with 2.6.7-rc3-bk6: this is basically the same, although
the console stalled twice during one boot, once after mounting all the
filesystems and then again after the ethernet comes up (as always).
Also, I was wrong about getting one character of output for each that I
type - it looks like I get 16 characters (if that many are available to
be printed, seemingly).
-ryan
next prev parent reply other threads:[~2004-06-15 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 0:04 NFS problem with recent 2.6 kernels (also serial console weirdness) foo
2004-06-15 18:42 ` foo [this message]
2004-06-15 18:52 ` more about serial console Russell King
2004-06-15 19:00 ` foo
2004-06-16 19:20 ` NFS problem with recent 2.6 kernels (also serial console weirdness) foo
2004-06-17 1:43 ` foo
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=20040615184229.GA13604@porto.bmb.uga.edu \
--to=foo@porto.bmb.uga.edu \
--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®