9 May
2013
9 May
'13
9:31 a.m.
On Thu, May 09, 2013 at 10:27:53AM +0100, Aparna Mandke wrote:
looks like some other issue. 4f69d0: d2800013 mov x19, #0x0 // #0 4f69d4: b9402260 ldr w0, [x19,#32]
So it is trying to access - 0x32 address and that is why L1 translation fault. Problem is somewhere else.
Can you reproduce this easily? Is it an application that you run and crashes consistently?
The strange thing is that the fault address should be reported as 32 rather than some high 0xffffffff874c0120 value. In your kernel message, x19 is indeed 0xffffffff874c0100 which does not match the previous mov x19, #0.
--
Catalin