* Matthijs van Duin matthijsvand...@gmail.com [150530 08:24]:
On 29 May 2015 at 17:50, Tony Lindgren t...@atomide.com wrote:
I believe some TI kernels use strongly-ordered mappings, mainline
kernel does not. Which kernel version are you using?
Normally I periodically rebuild based on
On 1 June 2015 at 19:58, Tony Lindgren t...@atomide.com wrote:
I think these kernels are missing the configuration for l3-noc
driver?
Yup. Since I'm pretty sure I have all the necessary info I was hoping
look into that... somewhere in my copious spare time...
I tried it on omap4 that has
* Matthijs van Duin matthijsvand...@gmail.com [150601 13:34]:
On 1 June 2015 at 19:58, Tony Lindgren t...@atomide.com wrote:
I think these kernels are missing the configuration for l3-noc
driver?
Yup. Since I'm pretty sure I have all the necessary info I was hoping
look into that...
On 1 June 2015 at 22:52, Tony Lindgren t...@atomide.com wrote:
OK that must be the case I've seen then. Probably that happens
when a device is not clocked.
It happens for any interconnect error reported as a result of
instruction fetch, but that is itself not a very common occurrence and
On 29 May 2015 at 17:50, Tony Lindgren t...@atomide.com wrote:
I believe some TI kernels use strongly-ordered mappings, mainline
kernel does not. Which kernel version are you using?
Normally I periodically rebuild based on Robert C Nelson's -bone
kernel (but with heavily customized config). I
* Matthijs van Duin matthijsvand...@gmail.com [150528 18:37]:
On 29 May 2015 at 02:58, Matthijs van Duin matthijsvand...@gmail.com wrote:
It is only guaranteed to happen immediately (before the next
instruction is executed) if the error occurs before the posting-point
of the write. However,
* Tony Lindgren t...@atomide.com [150529 08:52]:
* Matthijs van Duin matthijsvand...@gmail.com [150528 18:37]:
On 29 May 2015 at 02:58, Matthijs van Duin matthijsvand...@gmail.com
wrote:
It is only guaranteed to happen immediately (before the next
instruction is executed) if the error
* Matthijs van Duin matthijsvand...@gmail.com [150528 13:28]:
On 28 May 2015 at 18:01, Tony Lindgren t...@atomide.com wrote:
For failed device access you get an interrupt
Well for failed reads you get a bus error, and catching those (e.g.
using the existing exception mechanism used to catch
On 28 May 2015 at 18:01, Tony Lindgren t...@atomide.com wrote:
For failed device access you get an interrupt
Well for failed reads you get a bus error, and catching those (e.g.
using the existing exception mechanism used to catch MMU faults) is
the whole issue.
Though now that you mention it,
On Friday 29 May 2015 00:24:13 Tony Lindgren wrote:
* Matthijs van Duin matthijsvand...@gmail.com [150528 13:28]:
On 28 May 2015 at 18:01, Tony Lindgren t...@atomide.com wrote:
For failed device access you get an interrupt
Well for failed reads you get a bus error, and catching those
On 29 May 2015 at 02:58, Matthijs van Duin matthijsvand...@gmail.com wrote:
It is only guaranteed to happen immediately (before the next
instruction is executed) if the error occurs before the posting-point
of the write. However, in that case the error is reported in-band to
the cpu, resulting
* Pali Rohár pali.ro...@gmail.com [150528 15:29]:
On Friday 29 May 2015 00:24:13 Tony Lindgren wrote:
* Matthijs van Duin matthijsvand...@gmail.com [150528 13:28]:
On 28 May 2015 at 18:01, Tony Lindgren t...@atomide.com wrote:
For failed device access you get an interrupt
Well for
On 29 May 2015 at 00:24, Tony Lindgren t...@atomide.com wrote:
Hmm I believe the interrupt happens immediately trying to access an
invalid device. But maybe I'm thinking about just errors if a device
is not powered or clocked.
It is only guaranteed to happen immediately (before the next
On Wednesday 11 February 2015 14:40:33 Nishanth Menon wrote:
On Wed, Feb 11, 2015 at 2:28 PM, Pali Rohár pali.ro...@gmail.com wrote:
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
On 11 February 2015 at 13:39, Pali Rohár pali.ro...@gmail.com
wrote:
Anyhow, since checking
* Pali Rohár pali.ro...@gmail.com [150528 00:39]:
On Wednesday 11 February 2015 14:40:33 Nishanth Menon wrote:
On Wed, Feb 11, 2015 at 2:28 PM, Pali Rohár pali.ro...@gmail.com wrote:
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
On 11 February 2015 at 13:39, Pali Rohár
On 18 February 2015 at 22:14, Pali Rohár pali.ro...@gmail.com wrote:
Can you help us with above problem? How to catch external abort
on non-linefetch in kernel driver and prevent kernel panic?
Actually it's a synchronous bus error that you want to catch, which
however is misreported by linux as
Hi,
On Thu, Feb 19, 2015 at 07:20:41PM +0100, Pali Rohár wrote:
Anyway, in Nokia Harmattan N9/N950 2.6.32 kernel is this patch:
+/* Do we need runtime check ? */
+#if __LINUX_ARM_ARCH__ 6
{ do_bad, SIGBUS, 0, external abort on
linefetch },
+#else
+
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
On 11 February 2015 at 13:39, Pali Rohár pali.ro...@gmail.com wrote:
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
On Wednesday 11 February 2015 21:40:33 Nishanth Menon wrote:
On Wed, Feb 11, 2015 at 2:28 PM, Pali Rohár
pali.ro...@gmail.com wrote:
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin
wrote:
On 11 February 2015 at 13:39, Pali Rohár
pali.ro...@gmail.com
wrote:
Anyhow, since
On 11 February 2015 at 13:39, Pali Rohár pali.ro...@gmail.com wrote:
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
On Wednesday 11 February 2015 21:43:42 Pavel Machek wrote:
Hi!
On Sun 2015-02-01 09:56:28, Pali Rohár wrote:
On Sunday 01 February 2015 02:36:06 Matthijs van Duin wrote:
On 31 January 2015 at 20:06, Pali Rohár
pali.ro...@gmail.com
wrote:
I have configured two testing N900
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
On 11 February 2015 at 13:39, Pali Rohár pali.ro...@gmail.com
wrote:
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
Hi!
On Sun 2015-02-01 09:56:28, Pali Rohár wrote:
On Sunday 01 February 2015 02:36:06 Matthijs van Duin wrote:
On 31 January 2015 at 20:06, Pali Rohár pali.ro...@gmail.com
wrote:
I have configured two testing N900 devices. One with signed
bootloader which enable omap aes support and
* Pali Rohár pali.ro...@gmail.com [150211 12:32]:
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
On 11 February 2015 at 13:39, Pali Rohár pali.ro...@gmail.com
wrote:
Anyhow, since checking the firewalls/APs to see if you have
permission will probably only get you yet
On Wed, Feb 11, 2015 at 2:28 PM, Pali Rohár pali.ro...@gmail.com wrote:
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
On 11 February 2015 at 13:39, Pali Rohár pali.ro...@gmail.com
wrote:
Anyhow, since checking the firewalls/APs to see if you have
permission will probably
On Saturday 31 January 2015 16:13:39 Matthijs van Duin wrote:
On 31 January 2015 at 12:34, Pali Rohár pali.ro...@gmail.com
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
On Sunday 01 February 2015 02:36:06 Matthijs van Duin wrote:
On 31 January 2015 at 20:06, Pali Rohár pali.ro...@gmail.com
wrote:
I have configured two testing N900 devices. One with signed
bootloader which enable omap aes support and one device with
signed bootloader which does not enable
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren wrote:
I asked Pali to send me his copy of the updated NOLO
bootloader, so that I can test this. I just checked the
omap
On 31 January 2015 at 12:34, Pali Rohár pali.ro...@gmail.com 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
On Saturday 31 January 2015 15:38:28 Matthijs van Duin wrote:
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren
wrote:
I asked Pali to send me his copy of the updated
On Saturday 31 January 2015 16:13:39 Matthijs van Duin wrote:
On 31 January 2015 at 12:34, Pali Rohár pali.ro...@gmail.com
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
On 31 January 2015 at 20:06, Pali Rohár pali.ro...@gmail.com wrote:
Just to note that above error output is from device where is
signed X-Loader which *enable* omap aes support.
So it looks like it is not possible to dump registers which
should tell you if kernel has permission or not (in L3
On Saturday 17 January 2015 18:41:26 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150117 09:32]:
On Saturday 17 January 2015 18:04:11 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150117 01:21]:
Hello, after playing with aes and non-aes version of
bootloaders I
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren
wrote:
I asked Pali to send me his copy of the updated NOLO
bootloader, so that I can test this. I just checked the
On Wednesday 26 November 2014 18:54:12 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [141125 13:33]:
On Tuesday 25 November 2014 22:08:17 Pali Rohár wrote:
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec
* Pali Rohár pali.ro...@gmail.com [150117 01:21]:
Hello, after playing with aes and non-aes version of bootloaders
I found out that code which configure L3 firewall must be in
signed X-Loader part. So probably we cannot change configuration
at runtime...
Tony,
any idea how to dump
On Saturday 17 January 2015 18:04:11 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150117 01:21]:
Hello, after playing with aes and non-aes version of
bootloaders I found out that code which configure L3
firewall must be in signed X-Loader part. So probably we
cannot change
* Pali Rohár pali.ro...@gmail.com [150117 09:32]:
On Saturday 17 January 2015 18:04:11 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150117 01:21]:
Hello, after playing with aes and non-aes version of
bootloaders I found out that code which configure L3
firewall must be in
* Pali Rohár pali.ro...@gmail.com [141125 13:33]:
On Tuesday 25 November 2014 22:08:17 Pali Rohár wrote:
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren
wrote:
I
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren
wrote:
I asked Pali to send me his copy of the updated NOLO
bootloader, so that I can test this. I just checked the
On Tuesday 25 November 2014 22:08:17 Pali Rohár wrote:
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren
wrote:
I asked Pali to send me his copy of the updated NOLO
On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren wrote:
I asked Pali to send me his copy of the updated NOLO
bootloader, so that I can test this. I just checked the
omap
On Sat, Dec 07, 2013 at 08:51:04AM -0800, Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [131207 05:58]:
On Saturday 07 December 2013 14:48:20 Sebastian Reichel wrote:
On Sat, Dec 07, 2013 at 09:18:32AM +0100, Pali Rohár wrote:
On Saturday 07 December 2013 01:00:27 Sebastian
* Sebastian Reichel s...@ring0.de [131207 10:51]:
On Sat, Dec 07, 2013 at 08:51:04AM -0800, Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [131207 05:58]:
On Saturday 07 December 2013 14:48:20 Sebastian Reichel wrote:
On Sat, Dec 07, 2013 at 09:18:32AM +0100, Pali Rohár wrote:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren wrote:
I asked Pali to send me his copy of the updated NOLO bootloader,
so that I can test this. I just checked the omap documentation
(I only have access to the public one) and crypto related stuff
is not documented for the
* Sebastian Reichel s...@ring0.de [131207 15:04]:
On Sat, Dec 07, 2013 at 01:11:37PM -0800, Tony Lindgren wrote:
I asked Pali to send me his copy of the updated NOLO bootloader,
so that I can test this. I just checked the omap documentation
(I only have access to the public one) and
46 matches
Mail list logo
