On 31 January 2015 at 12:34, Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > [ 172.923553] Unhandled fault: external abort on non-linefetch (0x1018) at 0xb6f87028 > [ 172.930664] In-band Error seen by MPU at address 0 Also, why is this error so uninformative? A synchronous abort should at least mention the _physical_ address, type of access, etc. Anyhow, since checking the firewalls/APs to see if you have permission will probably only get you yet another fault if things are walled off, the robust way of dealing with this sort of situation is by probing the device with a read while trapping bus faults. This also handles modules that are unreachable for other reasons, e.g. being disabled by eFuse. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
