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

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

baldyeti wrote:
>> Debugs on startup are enabled for DebugView.
>> If my idea works, you should see exactly this line:
>> "... big Range[2] 0x0.01000000 0x0.77000000"
>>
>> and some lines later two or more of:
>> "... co_winnt_new_mdl_bucket] FixRange used 0x1000000 0x77000000"
> 
> I see the second one (FixRange) repeated numerous times in the
> rather verbose log, but not the 1st one (BigRange).

DebugView is totaly ok. No errors, no "Bug: ...", very good.

"big Range" can not see on coLinux starts.
You can only see it at driver load:
  colinux-daemon.exe --remove-driver
  colinux-daemon.exe --install-driver

"FixRange" is the usage of "big range" finder on startup. So it is no
problem, that you not have seen it in log. It is still working.

>> All other 'Range' should automaticly ignored.
>> No errors with 'pfn to big' or 'pfn out of range' should be have now (in
>> colinux-debug only, not in DebugView).
> 
> I am still seeing "Bug: PFN too high! 521536 >= 491520" but didn't
> you tell me that one was safe to ignore?

Yes, you can double ignore this. ;-)
1. This was an false/positive on co_os_map.
2. In the new code don't exist such text. There exist a new text "Bug:
PFN out of range", and this should not ignore.

The debug xml contains an old plus new debug (file was append).
Behind the text "Daemon compiled on Thu Mar  6 00:31:32 2008" all is ok,
no more errors.

Thanks. I will cleanup the code next weekend.

-- 
Henry N.