Help Needed: input overrun(s)

s.maiti at tcs.com s.maiti at tcs.com
Thu May 11 22:56:24 EST 2006


Thanks very much for your reply. It's seems you have already developed the 
MCC driver. Are you using channels 32 to 96? Have you made any changes in 
the dp ram allocation for uart or ethernet driver?
Please help me...

Thanks and regards,
Souvik Maiti
Tata Consultancy Services Limited
Mailto: s.maiti at tcs.com
Website: http://www.tcs.com



"Rune Torgersen" <runet at innovsys.com> 
05/10/2006 08:45 PM

To
"Stevan Ignjatovic" <stevan at iritel.com>, <s.maiti at tcs.com>
cc
<linuxppc-embedded at ozlabs.org>
Subject
RE: Help Needed: input overrun(s)






> -----Original Message-----
> From: Stevan Ignjatovic
> Hello,
> 
> > console we are receiving a print "ttyS: 1 input overrun(s)" 
> along with 
> > other prints of the driver and resulting in scrambled output. 
> > Can anyone suggest why this is happening? Is the driver 
> affecting the uart 
> > driver?
> 
> As far as UART driver is concerned, it could be affected if 
> you did not
> carefully allocate some resources. Are you using MCC1 or MCC2? Channel
> specific parameters of MCC1 (channels 0-127) are at the 
> beginning of the
> DPRAM (channel CH_NUM at address 64*CH_NUM). UART driver (as well as
> ethernet driver) allocates its buffer descriptors with
> m8260_cpm_dpalloc. I think that allocating with this function 
> starts at
> the beginning of the DPRAM, so you might have overwritten 
> UART's buffer
> descriptors. So, use MCC2 if you can. If you use some BRGs in your MCC
> driver you should check that as well. 

We have a MCC driver that we see the same happening on. It only occurs
under heavy load (top sows us usig 20-40 % cpu in interrupt).
I am pretty confident that we are not overwriting uart DPRAM. (MCC1 only
uses the middle 64 channels, skipping over the first 32 where the
conflict witht he UARTS are)

I have not seen it corrupt anything, so we have more or less ignored it.
Our theory is that it happens when the CPM gets overloaded.
It would be nice to actually fix it though....

ForwardSourceID:NT00006D1A 
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060511/0de4b416/attachment.htm 


More information about the Linuxppc-embedded mailing list