System: Win2000 SP4 with 1.5GB RAM, devel-coLinux-20100615.exe
When I set mem=640, the coLinux work fine
but I will got host crash when I set mem=645
btw: in the this host, It work fine with mem=800 before I upgrade from 2.6.22 to 2.6.33
Here is my command:
colinux-daemon.exe -t FLTK cocon=120x36 kernel=vmlinux mem=640 cobd0=..\root_fs cobd1=..\swap_fs cobd2=..\colinux_fs cobd30=..\tmp1_fs cobd31=..\tmp_fs eth0=slirp setcobd=async root=/dev/cobd0 ro elevator=deadline
For me mem=640 and mem=800 works on system with 1536 MB total RAM. Windows says in System overview, I have 1.5 GB. Tested with and without /PAE in Windows boot.ini.
Memory: 791296k/819200k available (2249k kernel code, 0k reserved, 756k data, 140k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfffe5000 - 0xfffff000 ( 104 kB)
colinux : 0xfe800000 - 0xffc00000 ( 20 MB)
vmalloc : 0xf2800000 - 0xfe7fe000 ( 191 MB)
lowmem : 0xc0000000 - 0xf2000000 ( 800 MB)
.init : 0xc12f0000 - 0xc1313000 ( 140 kB)
.data : 0xc1232640 - 0xc12ef728 ( 756 kB)
.text : 0xc1000000 - 0xc1232640 (2249 kB)
total used free shared buffers cached
Mem: 791620 15936 775684 0 1404 6244
-/+ buffers/cache: 8288 783332
Swap: 0 0 0
Of curse there exist a problem.
Tested some more with simple initrd:
colinux-daemon -t fltk kernel=vmlinux mem=648 initrd=initrd.gz root=/dev/ram0
656 = 290h : OK
655 = 28Fh : freeze
654 = 28Eh : freeze
653 = 28Dh : freeze
652 = 28Ch : OK
651 = 28Bh : freeze
650 = 28Ah : freeze
649 = 289h : freeze
648 = 288h : OK
647 = 287h : freeze
646 = 286h : freeze
645 = 285h : freeze
644 = 284h : OK
That seams me a problem with 4MB bounding. Please try a memory, that can div by 4 MB.
I try again today, it work fine with mem=652
The same bug exist also in kernel 184.108.40.206 and 220.127.116.11, and in the stable release 0.7.7.
A function on kernel start was accessing page table behind the physical memory limit.
SVN revision 1490 will fix it.
This bug was fixed in branch stable SVN revision 1491 now.
A new release 0.7.7.1 is available.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.