kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
* serial: 8250: RX hang issue
@ 2011-11-21 16:10 Pradeep Kumar
  2012-01-25  4:41 ` Peter Teoh
  0 siblings, 1 reply; 2+ messages in thread
From: Pradeep Kumar @ 2011-11-21 16:10 UTC (permalink / raw)
  To: kernelnewbies

Hi All,
I am working on a mobile development platform and performing some stress
warm boot tests using UART debug console(which is using serial 8250 driver
for console).

I am getting device debug console UART RX hang after iterations > 1500.
after this issue am not* able to issue any command. Able to see logs
though.

Later I kept some debug prints in isr and able to see that device is able
to generate interrupts when some data is received. So I came to conclusion
that some malfunctioning is happening  in upper layer not sure which layer
has this problem. Can some one give some ideas at which layer I can check?

One more observation is when I perform a open and close calls on debug UART
port(in my case ttyS0) while device is in UART RX hang state, then I notice
the UART console RX again below active and able issue commands from UART
console itself.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111121/12b5399f/attachment.html 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* serial: 8250: RX hang issue
  2011-11-21 16:10 serial: 8250: RX hang issue Pradeep Kumar
@ 2012-01-25  4:41 ` Peter Teoh
  0 siblings, 0 replies; 2+ messages in thread
From: Peter Teoh @ 2012-01-25  4:41 UTC (permalink / raw)
  To: kernelnewbies

On Tue, Nov 22, 2011 at 12:10 AM, Pradeep Kumar <pradeepkernel@gmail.com>wrote:

> Hi All,
> I am working on a mobile development platform and performing some stress
> warm boot tests using UART debug console(which is using serial 8250 driver
> for console).
>
> I am getting device debug console UART RX hang after iterations > 1500.
> after this issue am not* able to issue any command. Able to see logs
> though.
>

I suspect the buffer has reached it limits....


>
> Later I kept some debug prints in isr and able to see that device is able
> to generate interrupts when some data is received. So I came to conclusion
> that some malfunctioning is happening  in upper layer not sure which layer
> has this problem. Can some one give some ideas at which layer I can check?
>
> One more observation is when I perform a open and close calls on debug
> UART port(in my case ttyS0) while device is in UART RX hang state, then I
> notice the UART console RX again below active and able issue commands from
> UART console itself.
>
> Open and close perhaps clear the buffer, and so the communication can
restart again?   I am not sure if the buffer at the host or client side is
the culprit, or both.   What ever it is, it could be that the round robbin
clearing of buffer is not working.


>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>


-- 
Regards,
Peter Teoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120125/700ef4c1/attachment.html 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-01-25  4:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-21 16:10 serial: 8250: RX hang issue Pradeep Kumar
2012-01-25  4:41 ` Peter Teoh

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).