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

[Henry N. <Hen...@Ar...>]

baldyeti wrote:
>> 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...

I have only a german view:
http://home.arcor.de/henryn/colinux/screenshoots/Device-manager-recource-memory.png

Press keys LeftWinMenu + Pause
Register: Hardware
Button: Device Manager
Menu: View
Pulldownmenu: Recources sorted from type

Than open the tree memory or RAM

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

Ok. I think, is a problem between 1GB and 2GB. Perhaps with the 128MB
shared memory. Set the limit some steps highter. Go stepwide highter
starts with 1536 (2GB-512BM), than 1792 (2048-256) and last 1920 (2048-128).

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

/noexecute=alwaysoff is no longer needed. It is solved any time.
Because /nopae also crashes, yoiu can remove it away an use PAE defaults.

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

The XML should be only text format, if the daemon properly closed the
file (without BSOD crash). Have you removed the older output from
crashing, before starts the debug daemon appends?

> Anyway it had the following:
> 
> 	PFN too high! 523367 >= 491520
> and
> 	PFN too high! 523444 >= 491520

For left value have no idea.
The right value seems me ok. 491520 * 4K = 2013265920 Bytes (1920 MB)
This are the 2GB minus your graphic card.

-- 
Henry N.