Re: [lc-devel] hello

[Rodrigo S. de C. <rc...@im...>]

On Sat, May 17, 2003 at 04:24:35AM +0200, curious wrote:
> no, i don't have.
> 
> latest development patch corrupts filesystem though.
> i though it is porting to 21rc2-ac1 then i thought it is -20
> fault (because i fall back to -20)
> i did all of this on  my perfectly non-smp laptop ofcourse :)

It is important to know you are not compiling with preempt patch
before trying to figure out what the problem may be.

> 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.

> then i moved to pure 2.4.19 and apllied latest testing patch.
> no success.
> links caused kernel BUG @ filemap.c :/
> i learned to mount all ro, and only /tmp and /var rw after my
> first try when 21rc2-ac1+ccache
> totally damaged files which were never written to on ext2
> filesystem... (like libraries)
> 
> then i got a hint and set compcache=0M and it caused kernel only
> to hang.

You mean "compsize=". I just tested it with 0M here and it
worked. Probably something I fixed since 0.24pre5.

> 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.

> 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.

> i have no problems when i use 2.4.21rc2-ac1 kernel without
> ccache, so i exclde any kernel problems/hardware issues

Indeed it looks like something related to comp cache.

Best regards,
-- 
Rodrigo