I've looked at the code you supplied and this log, and the two
don't tie up. Could you supply the code around 0x60011200
please?
I'll have another look at it today. What I've discovered is that the
interrupt action gets overwritten. So the do_IRQ is not in error. No
I'll just have to find the place where the memory is changed.
greetings,
Mark.
600111d4: e59f00b4 ldr r0, 60011290 <do_IRQ+0x178>
600111d8: e1a01004 mov r1, r4
600111dc: e1a0200c mov r2, ip
600111e0: e1a03005 mov r3, r5
600111e4: eb003421 bl 6001e270 <printk>
600111e8: e594c000 ldr ip, [r4]
600111ec: e5941010 ldr r1, [r4, #16]
600111f0: e51b2028 ldr r2, [fp, -#40]
600111f4: e1a00005 mov r0, r5
600111f8: e1a0e00f mov lr, pc
600111fc: e1a0f00c mov pc, ip
60011200: e5944014 ldr r4, [r4, #20]
60011204: e3540000 cmp r4, #0
60011208: 1affffec bne 600111c0 <do_IRQ+0xa8>
6001120c: e3170201 tst r7, #268435456
60011210: 11a00005 movne r0, r5
60011214: 1b02347a blne 6009e404 <add_interrupt_randomness>
60011218: e10f3000 mrs r3, cpsr
6001121c: e3833080 orr r3, r3, #128
60011220: e129f003 msr cpsr, r3
60011224: e5d82000 ldrb r2, [r8]
60011228: e2022003 and r2, r2, #3
6001122c: e3520002 cmp r2, #2
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
