Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762038AbdLSKpJ (ORCPT ); Tue, 19 Dec 2017 05:45:09 -0500 Received: from foss.arm.com ([217.140.101.70]:34864 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761989AbdLSKpI (ORCPT ); Tue, 19 Dec 2017 05:45:08 -0500 Date: Tue, 19 Dec 2017 10:45:00 +0000 From: Mark Rutland To: Bharat Kumar Gogada Cc: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "catalin.marinas@arm.com" , Will Deacon , "james.morse@arm.com" , "julien.thierry@arm.com" , "punit.agrawal@arm.com" , "tbaicar@codeaurora.org" , "mingo@kernel.org" Subject: Re: Linux Kernel handling AXI DECERR/SLVERR Message-ID: <20171219104500.5otagp7m7dqretd2@lakrids.cambridge.arm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 532 Lines: 18 On Tue, Dec 19, 2017 at 10:23:25AM +0000, Bharat Kumar Gogada wrote: > Hi All, Hi, > When Linux is booted on ARM64 platform and an access to peripheral returns > DECERR or SLVERR on AXI. > > In the above error cases how would Linux kernel handle these faults ? Will it > hang/recover ? I believe that on contemporary CPUs these will result in an SError. As SErrors are asynchronous, and (in the absence of RAS extensions) their cause cannot be determined, these are treated as fatal, and the kernel will panic(). Thanks, Mark.