Re: [lc-devel] hello

[curious <cu...@pb...>]

On Fri, 16 May 2003, Rodrigo Souza de Castro wrote:

> It is important to know you are not compiling with preempt patch
> before trying to figure out what the problem may be.
unfortunatelly it's not this case (i apply agains vanilla)

> > then i concluded -20 is also causing problems or it's your patch
> > so i tried to use last stable 0.23 on -20
> > it gave me same results (i tried to execute links and it oopsed)
> Strange. So I guess only executing a binary oops the kernel, right? If
> you do have the oops in your log files (decoded to function names, of
> course), please send me it. And some basic information about your
> system configuration.
unfortunatelly i can only reproduce bug and have oops
non-decoded :(

btw. effects are nonpredictable to _some_ extent
i.e. links crash, but sometimes machine just hangs, sometimes
gives oops, sometimes segfault...
it might be linked to corruption of _filesystem_
after running for a while i got seriously damaged filesys, and i
couldn't predict damages.

lunks are compressed with upx, so they decompress to /tmp (which
was ext2 /tmp or /dev/shm a bit later (when i thought it is only
ext2/3 issue) /dev/shm didn't helped though, so i assume it
might be faulty decompression ...

btw, i can't find any params in /proc/sys/vm/ about compcache
(i.e. comp. algorithm mentioned in docs)

> You mean "compsize=". I just tested it with 0M here and it
> worked. Probably something I fixed since 0.24pre5.
no, i mean when i start links machine just hanged :)

ah, an hint - on negative memory system (when swap exceeds free
ram) and/or when swapping out cost (writing to device) is higher
than cpu cost pages should be allways swapped out compressed,
not only when cpu is idle.

> > now i am trying to compile 2.4.19 with cvs version, and check.
>
> I will send you, in a private email, a patch for 2.4.20 that I am
> testing before releasing. So you can try it out and give me a feedback
> about these corruptions. Maybe it is something related to your tight
> memory configuration.
just got it. cancelling cvs compile and compiling .20

> > then i'll start off first stable release with 2.4.19 to check wheter
> > this is some new feature not working, or .19 mismerge then i'll try
> > to use .18 branch of patches...
>
> Yes, trying 2.4.18 with the latest testing patch is probably a good
> idea to check out what is going on.
ok, so it'll be next after .20 i got from you (if it'll not
solve this problem ofcourse :)

thanks for support

--