I have tried ext4 with 2.6.33-rc8. ext4 is indeed working as module but again as read-only ;)

trying read-write I get:

EXT4-fs (sda4): Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF

No crashes with 2.6.33-rc8 since last one.

Thank you.

On Fri, Mar 5, 2010 at 20:44, Henry Nestler <henry.ne@arcor.de> wrote:
Hello Agustin,

ext4 is enabled as module. Maybe you needs to unpack modules manualy and run "depmod". Some older builds was created with wrong format in the file "modules.dep" fom my new depmod. The path list was without "/lib/modules/2.6.33-co-0.8.0" I have adjusted today.

Please check that you truly not have a "crash dump" in your directory "C:\WINDOWS\Minidump\". For the BSOD I need the stack backtrace from WinDbg.exe to fix it. Please read section "Howto use Windows crash dump" in the file doc/debugging in source or debugging.txt in your installation.

Have you rebootet Windows after replaceing the driver? This problem I have some times seen at work, by replacing linux.sys with same or newer version - all with kernel 2.6.22.
Running colinux-debug-daemon or running colinux-daemon with option "-v n" where "n > 0" can also crash some times on shutdown (very rarely).

I ask, because the linux.sys was not changed between kernel 2.6.22 and 2.6.33, and BSOD I have long not seen.
Have you some special kernel options in the coLinux config?
How many RAM you have in Windows and how many is for coLinux? Is PAE (Physical Adress Extension) enabled? You will see it with Key Win+Pause. Not try to use more as 800MB. If you use to many lowram, then the kernel has not enouth virrtual memory. I have not checket the total limit for this kernel.
You can see the sizes at boot, for example:
    vmalloc : 0xc8800000 - 0xfe7fe000   ( 863 MB)



At 05.03.2010 19:46, aguspiza wrote:
I test it and after more than 5 hours working I got BSOD (IRQ_LESS_OR_EQUAL). It is indeed much slower that 2.6.26.8, and it is not compiled with ext4fs ;) On the good side udev works!!

I do not have a crash dump. But it that helps I am running AMD Athlon 64 3Ghz with WinXP SP3. I have been running colinux 0.8.0 as service for years with kernel 2.6.22 and 2.6.25 and I have never seen a BSOD.

Congrats for your impresive work.

Thank you.

On Fri, Mar 5, 2010 at 18:39, Henry Nestler <henry.ne@arcor.de> wrote:
Aguspiza wrote:
I have seen that you are working on kernel 2.6.33-rc8, I was going to test it but your warning about data corruption scares me.

[...]

I have read that udev is working on colinux kernel 2.6.33-rc8 and I would like to make the jump, do you think it is ready?

The text about filesystem corruption was from early beginning with crashing kernel - depend on the problem of host memory mapping. The memory problem is fixed with a slow alternate. All memory allocations are much slower not, for example on spawning new task.

It's ready for beta testers. I have no crashes and no BSOD since 2.6.33-rc6 one month ago. I have short tested all basic functions, but have no long time tests. I don't know how it works in different environments. If more people would test it and report good state, I would feel me better.