From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yx0-f178.google.com (mail-yx0-f178.google.com [209.85.210.178]) by ozlabs.org (Postfix) with ESMTP id 26627B7B8B for ; Thu, 15 Oct 2009 04:07:57 +1100 (EST) Received: by yxe8 with SMTP id 8so11382502yxe.17 for ; Wed, 14 Oct 2009 10:07:55 -0700 (PDT) MIME-Version: 1.0 Sender: glikely@secretlab.ca In-Reply-To: <1255538154.26753.13.camel@allano> References: <1255538154.26753.13.camel@allano> From: Grant Likely Date: Wed, 14 Oct 2009 11:07:35 -0600 Message-ID: Subject: Re: MPC5200B panics with high ethernet rx traffic To: Asier Llano Palacios Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Oct 14, 2009 at 10:35 AM, Asier Llano Palacios 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.