[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SV: [microblaze-uclinux] crash of PetaLinux RC3 (kernel 2.6)
I am seeing similar behaviour.
A simple test application receiving and sending UDP packages over
Ethernet using the emac in fifo mode "hangs" after a few minutes. The
task seems to be stuck on the rtid instruction of the "_interrupt"
interrupt handling code (which contains "restore_context").
The r14 register contains the address of the rtid instruction itself, so
the rtid keeps reloading the PC, pointing back to itself.
Usually the rest of the system is still alive when this has occurred.
Sometimes the IP stack is "deaf", transmission still works, and incoming
packages are counted by the emac driver but does not make it up trough
the stack. Occasionally the whole system crashes.
Does anyone have an idea what could be causing this?
>my user application which is heavily IRQ-driven kills Linux after a few
>minutes anywhere. The same one is rock-stable when using it with
>I wanted to know where it crashed, so, in a first attempt, I did:
> xload mhs system.mhs
> connect mb mdm
> rrd pc
>and can see it's 0x80001f2c. Next I checked the file
linux-2.6.x/System.map >and it's within restore_context which is at
0x80001ebc. The offset is 28 >bytes, so I suspect it crashed at "lwi
r12, r1, PT_R12".
>I do use the latest patches known from this thread
>Do you have an idea what to do now?
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/