linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Asier Llano Palacios <a.llano@ziv.es>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: MPC5200B panics with high ethernet rx traffic
Date: Wed, 14 Oct 2009 11:07:35 -0600	[thread overview]
Message-ID: <fa686aa40910141007i3ec0e636yac62a5cccde8b44b@mail.gmail.com> (raw)
In-Reply-To: <1255538154.26753.13.camel@allano>

On Wed, Oct 14, 2009 at 10:35 AM, Asier Llano Palacios <a.llano@ziv.es> wrote:
> Hi,
>
> I've found a very simple way to create a kernel panic, that's happening
> to our MPC5200B based boards. The issue was that when our boards
> received a burst of ethernet packets had a kernel panic.

This looks familiar.  Look in drivers/net/fec_mpc52xx.c and find the
function mpc52xx_fec_reset().  Remove the calls to phy_stop(),
phy_write() and phy_start().  See if that helps.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      reply	other threads:[~2009-10-14 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 16:35 MPC5200B panics with high ethernet rx traffic Asier Llano Palacios
2009-10-14 17:07 ` Grant Likely [this message]

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=fa686aa40910141007i3ec0e636yac62a5cccde8b44b@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=a.llano@ziv.es \
    --cc=linuxppc-dev@lists.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).