Re: [coLinux-users] 0.7.2 less reliable on dual core?

[baldyeti <e_...@ho...>]

> What physicaly memory recource used your graphics card?

It's an integrated controller, using 128 MB of shared RAM.

> Have you other devices, that used memory regions over 2GB?

Sorry, don't know where to look...

> Limit the memory size to 1GB, /maxmem=1024 in C:\boot.ini. Better?

Actually that seemed to help indeed. I'll do another longer
test, but that wouldn't really be a satisfactory solution,
would it? Note that this is a single 2GB chip (plus memtest
has not pointed to faulty RAM anyway)

> Disable PAE in boot.ini. Or if PAE is enabled, enable it. Better?

PAE was enabled. I had to include "/nopae /noexecute=alwaysoff" to
disable it. At first (over 24h) this seemed to help but unfortunately
it crashed again later on. Directly after rebooting I started lots
of application to have over 1GB taken, and colinux failed after 2 or
3 successfull launches...

> The output from line 34 would be interesting. Fails it with constant or
> random values? Is it one count over the range, or totaly badly?
> Start
>   colinux-debug-daemon.exe -p -d -s prints=31,misc=31 -f debug.xml
> Than start colinux.
> If the error comes again, grep for the text "PFN too high" and lets see
> values here.

Weird file format that one ?!? There's semi-binary data at first
then an empty xml section at the end. Anyway it had the following:

	PFN too high! 523367 >= 491520
and
	PFN too high! 523444 >= 491520

> You not need to start linux completely, please trimm down parameters for
> all test as follow:
>   colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 mem=160

Thanks for your time,

--bald