From: "Matvejchikov Ilya" <matvejchikov@gmail.com>
To: Myron.Dixon@l-3com.com
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org, "Franca,
Jose \(NSN - PT/Portugal - MiniMD\)" <jose.franca@nsn.com>
Subject: Re: SKB corruption on heavy traffic
Date: Sat, 3 May 2008 18:07:48 +0400 [thread overview]
Message-ID: <8496f91a0805030707q136a7d5cv6e9472997c041cff@mail.gmail.com> (raw)
In-Reply-To: <F83A28966A0FAF41897D75586AFBBF5134A1FC@gns-mail.GNS.L-3COM.COM>
[-- Attachment #1: Type: text/plain, Size: 4998 bytes --]
Hi all!
The same problem! I've tried 2.4.xx and 2.6.xx kernels. Nothing changed!
BUT. After many days of fucking with fs_enet driver I've found a
stable (as I see) solution. The bugs I've had:
- kernel oopses
- SKB data corruption
- BDs status corruption
- SKB ring full message
- too many RX errors
- may be something else :)
For now I have a 2.4.35 fs_enet driver that works on heavy load
24/7... I don't know what happens with my 8260 board, but with this
code it be very stable. I supposed that there are some errors in 8260
CPM core, but errata don't know about it :)
I've append an attachment with my 2.4.35 kernel patch. Sorry for a big
file and not for only fs_enet file. Moreover I've used CPM111 errata
microcode and NAPI in fs_enet driver.
If you have any questions I'm glad to hear it.
2008/5/2 <Myron.Dixon@l-3com.com>:
> We have experience a very similar problem using a 2.4.18 kernel on an 8260 ppc processor.
> We have a telecomunication product that for some time only used the fec for TCP/IP ethernet
> traffic only and worked just fine.
>
> After we upgraded our product to implement TDM data over IP we started to notice an occasional
> kernel oops. We began to evaluate all of our products and determined that only some of the units
> exhibted this behaviour at various rates of occurrence. Further evaluation revealed that the pointers
> located in dpram pointing to the fec's buffer descriptors were some how getting corrupted.
> Note that the 8260 has 4 internal scc/fccs and we use all four for various aspects of our application
> and each shares dpram for pointers to buffer descriptors that reside in sdram. However, only the
> fec that is used for IP experiences this buffer descriptor corruption and, then, apparently, only under
> heavy traffic load. We spent about six months evaluating this problem including contacting freescale,
> but never found a solution. We finally, decided to use an external ethernet chip on a daughter card
> for our IP channel.
>
> It is, however, our belief that our problem relates to a possible bug in the 8260 CPM, but have yet to
> absolutely prove this.
>
> If we are experiencing the same problem (and potentially others) and there is a solution we would be
> very interested, as, we are not happy about the daughter card solution.
>
>
> Myron L. Dixon
> Sr. Software Engineer
> L-3 Communications, GNS
> 1519 Grundy's Lane
> Bristol, PA 19007
> Phone: 215 957 3739
> Fax: 215 957 3790
> email: Myron.Dixon@L-3Com.com
>
> -----Original Message-----
> From: linuxppc-dev-bounces+myron.dixon=l-3com.com@ozlabs.org [mailto:linuxppc-dev-bounces+myron.dixon=l-3com.com@ozlabs.org] On Behalf Of Franca, Jose (NSN - PT/Portugal - MiniMD)
> Sent: Wednesday, April 30, 2008 5:07 AM
> To: linuxppc-dev@ozlabs.org; linuxppc-embedded@ozlabs.org
> Subject: FW: SKB corruption on heavy traffic
>
> From our latest debugs we found that the problem occurs mainly on skbuff code. After some variable time kfree or kalloc result in kernel oops.
>
> -----Original Message-----
> From: Franca, Jose (NSN - PT/Portugal - MiniMD)
> Sent: quarta-feira, 30 de Abril de 2008 9:44
> To: 'ext Scott Wood'
> Cc:
> Subject: RE: SKB corruption on heavy traffic
>
> Hello!
>
> Thank you for replying!
> It't quite dificult to say if the problem exists without our changes, since the all software is dependent on this changes so to work with the hardware. I can't answer to that right now on that, but I forgot to add one thing: we have ring buffer full problems on our fcc_enet driver from time to time. So, I think the problem could be on linux configurations (related to hw) because there is a lot of posts on the web related to problems similar to this (none of them has really solved the bottom problem).
>
> Regards,
> Filipe
>
> -----Original Message-----
> From: ext Scott Wood [mailto:scottwood@freescale.com]
> Sent: terça-feira, 29 de Abril de 2008 20:15
> To: Franca, Jose (NSN - PT/Portugal - MiniMD)
> Cc: linuxppc-dev@ozlabs.org; linuxppc-embedded@ozlabs.org
> Subject: Re: SKB corruption on heavy traffic
>
> On Tue, Apr 29, 2008 at 07:39:07PM +0100, Franca, Jose (NSN - PT/Portugal - MiniMD) wrote:
> > We are developing a MPC8247 based telecom board (512MB), using linux
> > 2.4 with some proprietary changes on IP stack and we are facing some
> > problems when we have heavy traffic on our Ethernet interfaces...
>
> Do you see these problems without the proprietary changes, and with a current kernel?
>
> -Scott
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
[-- Attachment #2: linux-2.4.35-m82-2.patch.gz --]
[-- Type: application/x-gzip, Size: 21860 bytes --]
next prev parent reply other threads:[~2008-05-03 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 9:07 FW: SKB corruption on heavy traffic Franca, Jose (NSN - PT/Portugal - MiniMD)
2008-04-30 12:25 ` Gerhard Pircher
2008-04-30 13:03 ` Franca, Jose (NSN - PT/Portugal - MiniMD)
2008-04-30 19:20 ` Gerhard Pircher
2008-05-01 20:55 ` Myron.Dixon
2008-05-03 14:07 ` Matvejchikov Ilya [this message]
2008-05-05 8:54 ` Franca, Jose (NSN - PT/Portugal - MiniMD)
-- strict thread matches above, loose matches on Subject: below --
2008-04-29 18:39 Franca, Jose (NSN - PT/Portugal - MiniMD)
2008-04-29 19:15 ` Scott Wood
2008-04-30 8:43 ` Franca, Jose (NSN - PT/Portugal - MiniMD)
2008-04-30 15:00 ` Scott Wood
2008-04-30 15:07 ` Franca, Jose (NSN - PT/Portugal - MiniMD)
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=8496f91a0805030707q136a7d5cv6e9472997c041cff@mail.gmail.com \
--to=matvejchikov@gmail.com \
--cc=Myron.Dixon@l-3com.com \
--cc=jose.franca@nsn.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
/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).