[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Patch for stability under heavy IRQ load
On Wednesday 06 September 2006 09:57, Brettschneider Falk wrote:
> Alejandro Lucero wrote:
> > I have not answered since my problems goes on. As I comment,
> > I had not signals
> > during the tests so I suspected this did not resolv my
> > problem. However, I
> > got some system crashes when I killed processes under big
> > load interrupt and
> > this is not happening now.
> Alejandro, you wrote in a previous reply:
> > > > I did not have time lastly, but I had detected the problem was always
> > > > returning from sys_execve but, at first sight, without signals
> Can you explain this more in detail? I'm trying to understand what you're
> doing there.
I did the RTLinux port to microblaze/uClinux. It works but under some heavy
tests system crashes. The testbench is:
- 500us periodic RT task
- ping flood from another machine
- endless shell script doing some 'ls -l' commands on a NFS mounted directory
I'm using the addresses 0x1000 to 0x4000 (related with LMB and not used by
uClinux) to log system calls entries, system calls exits and context
switches. The entry.S file has been modified to do it and to check some
erroneous values as a system call number greater then 250 which will stop the
machine. A counter tells me where was the address of the last entry and then
I can know what was the last thing done by the OS. After a lot of tests I
know this is always after a sys_execve and it shows the system call returns
to the address of the brki instruction of previous process frame (destroyed
during the normal execve work). The problem is I don't know if this is the
point (I have re-read carefully the code and I cant see any track) or this
situation is created from a previous error on vfork.
I have not a lot of time to work on this, so I use some time during the nights
but it is not enough until now.
I think at this point this could be more a problem of the RTLinux port instead
of a uClinux one, but if there's someone with the same problems and without
RTlinux working, then things change.
Is it the case for you?
> CU, F@lk
> microblaze-uclinux mailing list
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
+34 665 68 71 68
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/