Re: [coLinux-users] Vista SP1 - complete failure

[Henry N. <hen...@ar...>]

Can you run "colinux-daemon --status-driver" ?

Perhaps we can check it by forcing parameter errors. Please run the
follow tests by step and check your mouse after every step. We need to
know on what step the problems begins. Abnormal exist of colinux-daemom
are ok in that testings.

"colinux-daemon mem=32 kernel=missing.file"
Lets only driver init, no loading kernel.

"colinux-daemon -v 3 mem=32 kernel=missing.file"
The same with more debugs.

"colinux-daemon -v 3 -d mem=32 kernel=vmlinux root=/dev/dummy"
Loads and starts the kernel. Exits before mount filesystem. No console.

"colinux-daemon -v 3 -t nt mem=32 kernel=vmlinux root=/dev/dummy"
The same with NT console.

"colinux-daemon -v 3 mem=32 kernel=vmlinux root=/dev/dummy"
The same with FLTK console.

"colinux-daemon -v 3 -d mem=32 kernel=vmlinux initrd=initrd.gz
root=/dev/ram0 init=/sbin/halt"
Starts RAMdisk and shuting down Linux automaticly, without console.

"colinux-daemon -v 3 mem=32 kernel=vmlinux initrd=initrd.gz
root=/dev/ram0 init=/sbin/halt"
The same with FLTK console.

"colinux-daemon mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0
init=/sbin/halt"
The same with less error checks.

-- 
Henry


Jonathan Deitch wrote:
>  Ok,
> 
> Still no go.  I cannot get a dump from colinux; when I try and run the
> debug setup, the system goes blackscreen and reboots.  No bluescreen.
> 
> I tried completely disabling the page file, same behavior.
> 
> When the problem occurs, I do not see ANY runaway (or abnormal) cpu or
> memory usage.
> 
> Anyone got any other ideas?  I'm rapidly reaching the point where I'm
> going to be given no choice by my employer but to abandon colinux as
> vista incompatible and find another solution.
> 
> - Jonathan
> 
> Jason Alonso wrote:
>> On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote:
>>   
>>> Jonathan Deitch wrote:
>>>     
>>>> However - and this is the puzzling part - when the system goes into the
>>>> slow-mode, there is no abnormal CPU load.  Yep, that's right ... no high
>>>> CPU in either task manager, or top.
>>>>
>>>> Both colinux and Vista are still usable - they're just very very slow
>>>> with a 4-5 second leg between any action and system response.
>>>>       
>> Sounds familiar...
>>
>>   
>>> Than I have an idea: The cpu has a buggy or a special timer chip? I have
>>> read some about buggy TSC, and Windows has shipped an update for such
>>> chips in a service pack.
>>>     
>> How about an alternative theory?  Is your page file usage changing?
>> If so, you can configure your taskman process list to show you memory
>> usage and/or VM size.  If something spirals out of control (and it
>> will take a little while to do so), your system will start swapping
>> memory with disk until it's painfully slow.  coLinux, however, should
>> not be torturing you with memory leaks.
>>
>> It's not as esoteric a theory as buggy system timer handling, but it's
>> a simple test.
>>
>> Cheers,
>> Jason
>>