From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Jun Sun" <jsun@mvista.com>, "H . J . Lu" <hjl@lucon.org>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: Strange behavior of serial console under 2.4.9
Date: Fri, 19 Oct 2001 13:10:39 -0400 [thread overview]
Message-ID: <015a01c158c0$fa562800$3501010a@ltc.com> (raw)
In-Reply-To: 3BD05A9A.BD06491C@mvista.com
Let's try that again...
Agreed - I've seen it once where it spit 16 chars, long pause, 16 more
chars, etc. This was due to the serial driver not getting interrupts.
Regards,
Brad
----- Original Message -----
From: "Jun Sun" <jsun@mvista.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: <linux-mips@oss.sgi.com>
Sent: Friday, October 19, 2001 12:53 PM
Subject: Re: Strange behavior of serial console under 2.4.9
> "H . J . Lu" wrote:
> >
> > The serial console under 2.4.9 is very strange. It is very slow. I have
> > no such problem with 2.4.3/2.4.5. Telnet is fine.
> >
>
> That is usually a symptom when the serial interrupts are not correctly
> delivered.
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Jun Sun <jsun@mvista.com>, "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: Strange behavior of serial console under 2.4.9
Date: Fri, 19 Oct 2001 13:10:39 -0400 [thread overview]
Message-ID: <015a01c158c0$fa562800$3501010a@ltc.com> (raw)
Message-ID: <20011019171039.n2-80ueuULyM9S7d9FXHowj2-HFZRen4H4-O_Pn8pZk@z> (raw)
In-Reply-To: 3BD05A9A.BD06491C@mvista.com
Let's try that again...
Agreed - I've seen it once where it spit 16 chars, long pause, 16 more
chars, etc. This was due to the serial driver not getting interrupts.
Regards,
Brad
----- Original Message -----
From: "Jun Sun" <jsun@mvista.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: <linux-mips@oss.sgi.com>
Sent: Friday, October 19, 2001 12:53 PM
Subject: Re: Strange behavior of serial console under 2.4.9
> "H . J . Lu" wrote:
> >
> > The serial console under 2.4.9 is very strange. It is very slow. I have
> > no such problem with 2.4.3/2.4.5. Telnet is fine.
> >
>
> That is usually a symptom when the serial interrupts are not correctly
> delivered.
next prev parent reply other threads:[~2001-10-19 17:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 1:57 Strange behavior of serial console under 2.4.9 H . J . Lu
2001-10-19 2:11 ` Bradley D. LaRonde
2001-10-19 2:11 ` Bradley D. LaRonde
2001-10-19 2:40 ` H . J . Lu
2001-10-19 13:26 ` Maciej W. Rozycki
2001-10-19 13:54 ` Bradley D. LaRonde
2001-10-19 13:54 ` Bradley D. LaRonde
2001-10-19 15:47 ` Ralf Baechle
2001-10-26 16:12 ` Backspace on Virtual Console causes oops Wayne Gowcher
2001-10-26 17:30 ` Gleb O. Raiko
2001-10-26 18:37 ` Wayne Gowcher
2001-10-29 8:26 ` Gleb O. Raiko
2001-10-29 18:21 ` James Simmons
2001-10-26 18:05 ` Pete Popov
2001-10-26 18:11 ` James Simmons
2001-11-13 20:09 ` ld error " linking PIC files with non-PIC files " Wayne Gowcher
2001-11-14 0:18 ` Ralf Baechle
[not found] ` <000a01c170d0$e8662000$101d690a@huawei.com>
2001-11-19 9:05 ` Ralf Baechle
2001-10-19 16:53 ` Strange behavior of serial console under 2.4.9 Jun Sun
2001-10-19 17:10 ` Bradley D. LaRonde [this message]
2001-10-19 17:10 ` Bradley D. LaRonde
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='015a01c158c0$fa562800$3501010a@ltc.com' \
--to=brad@ltc.com \
--cc=hjl@lucon.org \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
/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