I have the same problem as Jonathan in my ARM Linux installation.
The memory violation error happens occasionally -- not always.
The systems runs well enough to do a lot of useful work,but
eventually it dies under stress test. Programs like sed and
portmap seem to always have memory violation during init.
I have been thinking this either has to do with glibc ld-linux.so or
kernel level caching problem. Upgrading glibc to 2.0.106 was something
I have been trying to do for a long time. My build of 2.0.106 glibc
builds fine, but then at run time the dynamic linker always gives out
IO_2_1_stdin not found error. Very wierd. Turning cache completely off
in the kernel doesn't remedy the situation either.
Some people apparently have a solidly working 2.1.X kernel. Can anyone
elaborate on the version of the toolchain they use to create kernel,
glibc stuff, and other binaries? Can anyone upload a working tree image
somewhere?
It would also help to hear from people (other than Russell and Philip)
what their experiences are with 2.1.X kernels.
Sorry to have so many requests, but I am a little desperate here.
Thanks.
--
Hwa-Jin Bae
PSO Systems Inc
mailto:[EMAIL PROTECTED]
http://www.pso.com
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
