Hi, can u guide how to debug this and have an fix/workaround for this. i see softlockup_tick and many funtions in the trace message. how to pinpoint where it got struck.
On Sun, Jun 27, 2010 at 9:47 PM, Harishkumar V <[email protected]>wrote: > hi, > > oh is it, can u explain, how to find out it.....which portion of the code. > i see only this, > > > handle_IRQ_event+0x28/0x74 > LR is at handle_level_irq+0x94/0xec > pc : [<c008cc30>] lr : [<c008e18c>] psr: 48000113 > sp : c7eede90 ip : c7eedeb0 fp : c7eedeac > r10: 0000001d r9 : c0638ba8 r8 : 00000000 > r7 : 0000005c r6 : 00000000 r5 : 0000005c r4 : c7a1b360 > r3 : 00000000 r2 : 0000006e r1 : c7a1b360 r0 : 0000005c > Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user > Control: 10c5387d Table: 87f48018 DAC: 00000015 > [<c003b370>] (show_regs+0x0/0x50) from [<c008c738>] > (softlockup_tick+0x108/0x148) > r5:00000104 r4:000000c7 > > On Sun, Jun 27, 2010 at 6:36 PM, Michael Blizek < > [email protected]> wrote: > >> Hi! >> >> On 14:09 Sun 27 Jun , Harishkumar V wrote: >> > MMU is available in ARM. >> > >> > if the same(cpu softlockup) exists on x86, how to handle this, u told in >> > earlier mail, >> > >> > "This is only the stack trace of the softlockup check, not the code >> which >> > got stuck", how to find out at which point, the code got struck, in x86. >> >> Usually the stack trace that you have sent already contains the code which >> got >> stuck... >> >> -Michi >> -- >> programing a layer 3+4 network protocol for mesh networks >> see http://michaelblizek.twilightparadox.com >> >> > > > -- > Thanks and Regards, > Harish Kumar. V > -- Thanks and Regards, Harish Kumar. V
