From: Bharat Kumar Gogada <bharatku@xilinx.com>
To: Mark Rutland <mark.rutland@arm.com>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
        Will Deacon <Will.Deacon@arm.com>,
        "james.morse@arm.com" <james.morse@arm.com>,
        "julien.thierry@arm.com" <julien.thierry@arm.com>,
        "punit.agrawal@arm.com" <punit.agrawal@arm.com>,
        "tbaicar@codeaurora.org" <tbaicar@codeaurora.org>,
        "mingo@kernel.org" <mingo@kernel.org>
Subject: RE: Linux Kernel handling AXI DECERR/SLVERR
Thread-Topic: Linux Kernel handling AXI DECERR/SLVERR
Thread-Index: AdN4sp3aDvoTQGI0SxmdlTRAbVFJCgAA808AAAE3PsA=
Date: Tue, 19 Dec 2017 11:28:49 +0000
Message-ID: <BLUPR0201MB150517EAFAF3A46B8A19489CA50F0@BLUPR0201MB1505.namprd02.prod.outlook.com>
References: <BLUPR0201MB1505A278D2EF1EABD80555EEA50F0@BLUPR0201MB1505.namprd02.prod.outlook.com>
 <20171219104500.5otagp7m7dqretd2@lakrids.cambridge.arm.com>
In-Reply-To: <20171219104500.5otagp7m7dqretd2@lakrids.cambridge.arm.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3c0d44b0-ead3-4190-441f-08d546d3acf8
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Dec 2017 11:28:49.5538
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 657af505-d5df-48d0-8300-c31994686c5c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0201MB1506
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id vBJBT2UW009539
Content-Length: 949
Lines: 22

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. 
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 ?

Regards,
Bharat