> Yes, that sounds familiar. Most likely, the value of the MDIO bus
> control register got clobbered and not reset when the FEC was reset.
I recall that I wondered about the RFIFO-error case back then. The manual states
===
Receive FIFO Error - indicates error occurred within the RX FIFO. When
[ed: quoting repaired]
On Wed, May 20, 2009 at 11:26 AM, Eric Millbrandt
wrote:
> Grant Likely wrote:
> > Yes, that sounds familiar. Most likely, the value of the MDIO bus
> > control register got clobbered and not reset when the FEC was reset.
> > Try adding this line to the beginning of mpc52xx
-Original Message-
From: Grant Likely [mailto:grant.lik...@secretlab.ca]
Sent: Wednesday, May 20, 2009 12:49
To: Eric Millbrandt
Cc: Jon Smirl; Wolfram Sang; linuxppc-dev@ozlabs.org
Subject: Re: mpc5200 fec error
On Wed, May 20, 2009 at 10:41 AM, Eric Millbrandt
wrote:
> It looks l
On Wed, May 20, 2009 at 10:41 AM, Eric Millbrandt
wrote:
> It looks like the phy is never getting reset properly after the
> FEC_IEVENT_RFIFO_ERROR. I threw some printk's into the fec mdio driver
Yes, that sounds familiar. Most likely, the value of the MDIO bus
control register got clobbered a
> On Wed, May 20, 2009 at 9:42 AM, Eric Millbrandt
> wrote:
>>> > 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
On Wed, May 20, 2009 at 11:28 AM, Eric Millbrandt
wrote:
> -Original Message-
> From: Jon Smirl [mailto:jonsm...@gmail.com]
> Sent: Wednesday, May 20, 2009 11:15
> To: Eric Millbrandt
> Cc: Wolfram Sang; Grant Likely; linuxppc-dev@ozlabs.org
> Subject: Re: mpc5200 fe
-Original Message-
From: Jon Smirl [mailto:jonsm...@gmail.com]
Sent: Wednesday, May 20, 2009 11:15
To: Eric Millbrandt
Cc: Wolfram Sang; Grant Likely; linuxppc-dev@ozlabs.org
Subject: Re: mpc5200 fec error
On Wed, May 20, 2009 at 9:42 AM, Eric Millbrandt
wrote:
>> > I a
On Wed, May 20, 2009 at 9:42 AM, Eric Millbrandt
wrote:
>> > 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
>> >
>>
> > 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.89
> > 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.8
On Tue, May 19, 2009 at 4:21 PM, Eric Millbrandt
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
-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 s
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.
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?
rsc
On Mon, May 18, 2009 at 01:36:27PM -0400, Eric Millbrandt wrote:
> Hello all,
>
>
>
> I am testing a 2.6.29.3 (with preempt_rt patch
14 matches
Mail list logo
