From: Henry N. <hen...@ar...> - 2012-03-26 20:48:24
|
Hello Lorne, please go into source code and get the file doc/debugging. There is written how to analyse the windows crash dumps. We need the stack backtrace. After you have such, please attach it on a new created bug report on sourceforge. Please also attach your configuration. 5-10% is not often. More reproducing would be better. Maybe play with the options. Try less memory, try the initrd. So other developer can also reproduce this bug. -- Henry N. -Urspr. Mitteilung- Betreff: [coLinux-users] Crashing problem Von: Lorne Sturtevant <dr...@sh...> Datum: 26.03.2012 21:53 I've been having a problem with coLinux crashing on me. The crash happens as soon as I start coLinux, but it only happens about 5%-10% of the time. I'm running coLinux on WinXP SP3. When it crashes, it most often just reboots the host PC. Very rarely it will blue screen instead. I've done some searching on the mailing list already and found some posts about PAE causing a problem. I did some experiments and I can get coLinux to start without crashing by turning PAE off. If I boot Windows with the parameters /nopae /noexecute=alwaysoff, then I can't reproduce the crash. I've also experimented with the other parameters to /noexecute, but alwaysoff is the only one that works since it's the only one that truely disables PAE. Unfortunately, I cannot run the system with PAE off. I need PAE on so DEP is enabled. So my questions are: Is it possible to run with PAE on? Is there any other things I can try try and fix the crash? I'm willing to get into the code to try and track down this bug and fix it. Where should I get started? -- Lorne Sturtevant Sum Ergo Cogito ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Lorne S. <dr...@sh...> - 2012-03-26 21:05:08
|
On 03/26/2012 02:48 PM, Henry N. wrote: > Hello Lorne, > > please go into source code and get the file doc/debugging. There is written how to analyse the windows crash dumps. We need the stack backtrace. After you have such, please attach it on a new created bug report on sourceforge. > Please also attach your configuration. > > 5-10% is not often. More reproducing would be better. Maybe play with the options. Try less memory, try the initrd. So other developer can also reproduce this bug. I'll start there. From what I understand though, crash dumps will only be produced when the crash is a blue screen, not a reboot. Is that correct? Only <5% of my crashes are blue screens. Rebooting is far far more likely. -- Lorne Sturtevant Sum Ergo Cogito |
From: Lorne S. <dr...@sh...> - 2012-03-28 19:39:49
|
On 03/26/2012 02:48 PM, Henry N. wrote: > Hello Lorne, > > please go into source code and get the file doc/debugging. There is written how to analyse the windows crash dumps. We need the stack backtrace. After you have such, please attach it on a new created bug report on sourceforge. > Please also attach your configuration. > > 5-10% is not often. More reproducing would be better. Maybe play with the options. Try less memory, try the initrd. So other developer can also reproduce this bug. I've created a bug report for this crash. It's bug 3512516. Let me know if there's anything else you require to help track this down. This is very high priority for me right now, so I'll be able to help with this as much as I can. -- Lorne Sturtevant Sum Ergo Cogito |