Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762302AbdLSLiy (ORCPT ); Tue, 19 Dec 2017 06:38:54 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:35624 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751578AbdLSLix (ORCPT ); Tue, 19 Dec 2017 06:38:53 -0500 Date: Tue, 19 Dec 2017 11:38:48 +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: <20171219113848.6dpb3fosbznguala@lakrids.cambridge.arm.com> References: <20171219104500.5otagp7m7dqretd2@lakrids.cambridge.arm.com> 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: 750 Lines: 19 On Tue, Dec 19, 2017 at 11:28:49AM +0000, Bharat Kumar Gogada wrote: > In our case the peripheral returns SLVERR first time and we see the following print but kernel do not hang. > [ 231.484186] Unhandled fault: synchronous external abort (0x92000210) at 0x0000007f9241f880 > Bus error > > And from simulation we know that subsequent access to peripheral > returns OKAY response, however we see subsequent access fail with same > above bus error when we boot Linux. > > Is there a way to handle these synchronous abort gracefully in Linux > or are these fatal ? We don't currently have any mechanism to handle these, though it might be possible for synchronous aborts. Do you know why the device is returning SLVERR in this case? Thanks, Mark.