From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0151.outbound.protection.outlook.com [207.46.163.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 7DC302C007A for ; Wed, 5 Feb 2014 10:28:44 +1100 (EST) Message-ID: <1391556506.6733.193.camel@snotra.buserror.net> Subject: Re: Oops on shutdown : 3.11.0-5-powerpc-e500mc Ubuntu From: Scott Wood To: John Donnelly Date: Tue, 4 Feb 2014 17:28:26 -0600 In-Reply-To: References: <1391552655.6733.184.camel@snotra.buserror.net> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 Tue, 2014-02-04 at 16:45 -0600, John Donnelly wrote: > Hi Scott, > > This panic was in the kernel related to NFS , not u-boot; > Unfortunately I didn't catch the earlier console message/Oops but I > recall it being something similar. > > > Can you enlighten me what the errata addresses ? I A-004510 can cause memory corruption due to dirty cache lines being dropped. The workaround in U-Boot reconfigures the chip so that this can't happen. The reconfiguration lasts until a reboot, so it's still effective once you start Linux. It needs to happen while there's no other traffic on the bus, which is why the workaround is not done in Linux itself. What revision of what chip are you using, and what version of U-Boot? -Scott