Re: [coLinux-users] Colinux Blue Screen Crashes

[Bob W. <bwh...@my...>]

>Henry N. Wrote on 1/7/12:

>What you can do is to check that the ndis-driver is >truly the problem.

>If you installs WinPcap and changes the coLinux config >from ndis-bridge
into pcap-bridge. Disappears this the >problem?

 

I have tried WinPCap and Slirp, both crash with memory corruption.

 

>An other candidate for memory leakages is the option >"setcobd=async". It
also crashes without this?

 

Yes it crashes.

 

>Can you give a command example for console to force >this bug on other
distributions? For example running >"netio" under Debian 6.0 Squeeze

 

It tried netio under Debian and it only runs for 4 or 5 minutes and does not
use much additional memory. Since the crash occurs at memory utilization
above 95% and this only got to 80% there was no crash. Can you suggest
another console program that can be run continuously to use up enough memory
to get above 95%.

 

>I see, that you have only 384 MB for the virtual >machine. Comes the crash
faster, if you use less memory >(for example 256)? Maybe it is a generally
problem with >memory.

 

I tried 256 and it crashed in about the same amount of time. The results of
all these tests were reported in the bug tracker as comments.

 

These things that you have asked me to try seem like a waste of time so far.
It would be better if somebody that understands colinux well looked at the
patterns in memory where the corruption is detected to see if they recognize
anything related to what colinux is doing.

 

Regards, 

Bob W.