lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 20 Dec 2017 10:33:43 +0000
From:   Bharat Kumar Gogada <>
To:     Mark Rutland <>
CC:     "" <>,
        "" <>,
        Will Deacon <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>
Subject: RE: Linux Kernel handling AXI DECERR/SLVERR

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 abort.
Since currently there is no mechanism to handle, if once synchronous abort is received from a peripheral,
consecutive access will show up same error even peripheral responds with OKAY ?
What are the possible ways for handling these ?

Do you know why the device is returning SLVERR in this case?
There is an error being detected by the device.


Powered by blists - more mailing lists