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

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

Hello Baldyeti,

baldyeti wrote:
> PS: I have also observed the following error message:
> (besides the original CO_RC_ERROR_ERROR)
> 
> Linux version 2.6.22-co-0.7.2 (hn@hn-lt) (gcc version 4.1.2)
> #1 PREEMPT Fri Jan 18 21:44:04 UTC 2008
> 160MB LOWMEM available.
> Entering add_active_range(0, 0, 40960) 0 entries of 256 used
> Zone PFN ranges:
>    DMA             0 ->        0
>    Normal          0 ->    40960
> early_node_map[1] active PFN ranges
>      0:        0 ->    40960
> On node 0 totalpages: 40960
> colinux: Linux VM terminated
> colinux: BUG at 
> ...p/stable-0.7.2-snapshot/linux-2.6.22-source/mm/bootmem.c:151

static void __init free_bootmem_core(bootmem_data_t *bdata, unsigned
...
         BUG_ON(PFN_DOWN(addr + size) > bdata->node_low_pfn);  <=== trap

Full code: http://lxr.linux.no/linux/mm/bootmem.c#L150

The other was
> daemon: exit code 89a09401
> daemon: error - CO_RC_ERROR_ERROR, line 37, file 
> src/colinux/kernel/pages.c (77)

23: co_rc_t co_manager_get_page(struct co_manager *manager, co_pfn_t
...
31: if (*pfn >= manager->hostmem_pages) {		<=== trap
32:		/* Surprise! We have a bug! */

34:	co_debug_error("PFN too high! %ld >= %ld",
35: 			 *pfn, manager->hostmem_pages);

37:		return CO_RC(ERROR);

Full code:
http://colinux.svn.sourceforge.net/viewvc/colinux/tags/0.7.2/src/colinux/kernel/pages.c?view=markup

1. On this step the linux side was never run. We only are in the windows
driver. This helps a liddle more, where we need to search: Not in linux
kernel. It is inside the windows kernel driver.

2. Both errors says, that some will access a page behind the limit
(160MB in your case). The limit checkers traps into the error.

3. Both errors fails with an access to pfn and max pfn.

Was a variable overwritten? Why memory are changed? Or why the requested
pfn number are not in range of max pfn? Don't know. I'm a liddle out of
ideas.

Memory you have tested with memtest. So, the chips are ok.
What physicaly memory recource used your graphics card?
Have you other devices, that used memory regions over 2GB?
Limit the memory size to 1GB, /maxmem=1024 in C:\boot.ini. Better?

Interesting question: Is PAE currently enabled? Press keys LeftWin +
Pause. On System properties a text "Physical Adress Extension" is seen
or not?
Disable PAE in boot.ini. Or if PAE is enabled, enable it. Better?

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.

You not need to start linux completely, please trimm down parameters for
all test as follow:
  colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 mem=160

-- 
Henry N.