From: Arun Dharankar <ADharankar@ATTBI.Com>
To: Richard Williams <richard_williams@stratexnet.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Serial console ports on systems with no console connected.
Date: Tue, 9 Jul 2002 19:45:19 -0400 [thread overview]
Message-ID: <200207091945.19620.ADharankar@ATTBI.Com> (raw)
In-Reply-To: <8D7C5F56B409554D9D46AC22195807F3156BEB@exchwenz01.smtp.dmcwave.co.nz>
Thanks for your reply, Richard!
This is definitely not so in my case, there is very little output
generated. Also have the serial port speed set at 115200, I
dont believe this is buffer overrun issue.
Anyway, I could work around the problem by checking for
the previous buffer's state and drop the characters. Would be
nice to get to the root cause.
Best regards,
-Arun.
On Tuesday 09 July 2002 06:08 pm, Richard Williams wrote:
> I've had a board hang in the same place before. Can't remember exactly the
> circumstances but it was triggered by me turning on a lot of debug messages
> in kernel modules.
>
> Perhaps buffer overrun on the console port?
>
> Regards,
> Richard
>
> -----Original Message-----
> From: Arun Dharankar [mailto:ADharankar@ATTBI.Com]
> Sent: Wednesday, 10 July 2002 12:08 a.m.
> To: Wolfgang Denk
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: Re: Serial console ports on systems with no console connected.
>
>
>
> Hello, and thanks for your reply!
>
> The board has SCC4 and SMC1 based serial ports. I have
> tried both of these as console ports under Linux and PPCBOOT.
> PPCBOOT code is unmodified (as it is from the distribution) for
> SCC4 and SMC1 code. The Linux code is unmodified for
> SMC1, and I see this behavior in case of both these serial
> ports.
>
> The place where the BDI shows the PC to hang is in
> serial_putc(...) waiting for the transmit buffer to be drained by the
> 8260:
>
> /* Wait for last character to go.
> */
> while (tbdf->cbd_sc & BD_SC_READY)
> ;
>
> Ofcourse, when the cable is present, things work well.
>
> Though I dont see any code path, or from hardware perspective
> what could be wrong, I am open to any guesses/hints at
> debugging it.
>
>
> Best regards,
> -Arun.
>
> On Tuesday 09 July 2002 01:14 am, Wolfgang Denk wrote:
> > In message <200207082127.16518.ADharankar@ATTBI.Com> you wrote:
> > > This question is common to both ppcboot and ppc-linux.
> > > The ppcboot I am using is 1.1.5 and Linux kernel 2.4.18.
> > >
> > > If there is no console connected to the serial console port,
> > > is it true that a thread sending output to it hangs? If this is
> >
> > No, this is NOT true.
> >
> > Why should it? There is no flow control used - neither in the PPCBoot
> > nor in the Linux UART drivers...
> >
> > > I have a MPC8260ADS based board, and see the above
> >
> > ...at least not in the standard MPC8xx and MPC8260 UART drivers.
> >
> > > behavior under ppcboot. Under Linux using a BDI debugger
> > > the thread sending output to the console hangs. Perhaps
> >
> > You must be doing something wrong.
> >
> > Wolfgang Denk
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-09 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 22:08 Serial console ports on systems with no console connected Richard Williams
2002-07-09 23:45 ` Arun Dharankar [this message]
2002-07-10 6:47 ` Murray Jensen
2002-07-10 11:41 ` Jerry Van Baren
2002-07-11 1:53 ` Arun Dharankar
2002-07-21 19:10 ` Arun Dharankar
2002-07-22 7:03 ` Wolfgang Denk
[not found] <ADharankar@ATTBI.Com>
[not found] ` <200207252058.04074.ADharankar@ATTBI.Com>
2002-07-26 2:22 ` Murray Jensen
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 1:27 Arun Dharankar
2002-07-09 5:14 ` Wolfgang Denk
2002-07-09 12:08 ` Arun Dharankar
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=200207091945.19620.ADharankar@ATTBI.Com \
--to=adharankar@attbi.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=richard_williams@stratexnet.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;
as well as URLs for NNTP newsgroup(s).