From: Dan Wilson <dwilson@dslextreme•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: 8543 console baud rate change problem
Date: Mon, 31 Mar 2008 09:56:42 -0700 [thread overview]
Message-ID: <47F117CA.3020901@dslextreme.com> (raw)
In-Reply-To: <47EEFB5B.3050700@fulcrummicro.com>
Dan Wilson wrote:
> We are using ELDK 4.1, linux kernel 2.6.22 on an 8543 board with a
> Layer 2 switch on it (i.e., the actual packet switching is done in an
> external chip, not by the 8543 itself). One of our customers has
> encountered a strange issue with system console baud rate changes.
> The system console is connected to a UART port on the 8543.
>
>
> Here is the sequence of events:
>
> + powercycle unit at 115200
>
> + have ping session going
> + establish telnet session
> + have L2 traffic traversing the switch
>
> + switch baud rate to any other baud rate beside 38400
> + hit a few returns
> + switch baud rate back to 115200 and no problem
>
> + switch baud rate to 38400
> + type a few char
> + switch baud rate back to 115200
> + console is not responsive
>
> + existing ping session is still going
> + L2 traffic is still OK
> + telnet session disconnected and can not reconnect;
> telnet session is being served by linux ip stack
>
> + Had to power cycle to get everything back
>
Just to follow up on this. We were able to determine that our customer
had shut off the normal telnet daemon and was using their own program to
handle telnet sessions. In addition, they weren't using agetty. We got
them to use agetty, and now things seem to be working for them.
Dan.
next prev parent reply other threads:[~2008-03-31 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 2:30 8543 console baud rate change problem Dan Wilson
2008-03-31 16:56 ` Dan Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 2:13 Dan Wilson
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=47F117CA.3020901@dslextreme.com \
--to=dwilson@dslextreme$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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