On Tue, May 19, 2009 at 4:21 PM, Eric Millbrandt <emillbra...@dekaresearch.com> wrote: > -----Original Message----- > From: Wolfram Sang [mailto:w.s...@pengutronix.de] > Sent: Tuesday, May 19, 2009 16:57 > To: Robert Schwebel > Cc: Eric Millbrandt; linuxppc-dev@ozlabs.org > Subject: Re: mpc5200 fec error > > On Tue, May 19, 2009 at 10:36:45PM +0200, Robert Schwebel wrote: >> Wolfram, have you seen this mail? You recently tested -rt on 2.6.29, >> right? Did you only test that on the customer hardware or also on the >> phyCORE-MPC5200B? > > So far, I tried only on customer hardware, and that was 2.6.29.2-rt11. > With > that setup, I could work with NFS flawlessly, no real stress-testing > though. > Testing latest .3-rt is on my todo, will check the phyCOREs, too. > > Regards, > > Wolfram > > -- > Pengutronix e.K. | Wolfram Sang > | > Industrial Linux Solutions | http://www.pengutronix.de/ > | > > I am able to reproduce the error using 2.6.29.2-rt11. I was able to > mitigate the problem by raising the priority of the transmit irq. > However when running an NFS server on the pcm030 under high cpu load I > now get > > [ 132.477503] net eth0: FEC_IEVENT_RFIFO_ERROR > [ 132.892329] net eth0: FEC_IEVENT_RFIFO_ERROR > [ 133.884109] net eth0: FEC_IEVENT_RFIFO_ERROR > [ 134.876059] net eth0: FEC_IEVENT_RFIFO_ERROR > > Raising the priority of the rx irq does not seem to fix this problem > though.
Hi Eric, This error has been seen before in non-rt kernels. I haven't had the chance to track it down and kill it yet. I believe there are locking issues associated with it. g. > > > _________________________________________________________________________________________ > > This e-mail and the information, including any attachments, it contains are > intended to be a confidential communication only to the person or entity to > whom it is addressed and may contain information that is privileged. If the > reader of this message is not the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, please > immediately notify the sender and destroy the original message. > > Thank you. > > Please consider the environment before printing this email. > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev > -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
