search

SmallLonlyWolf / embox

Automatically exported from code.google.com/p/embox
0 stars 0 forks source link

x86 mmu is broken #695

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Use template x86/nonvga_debug. Add embox.arch.x86.mmu and embox.mem.mmap_mmu at 
runlevel 1. Also change runlevel to 1 of all embox.mem.* modules

What is the expected output? What do you see instead?
Embox kernel start
runlevel: init level is 0
    unit: initializing embox.driver.interrupt.i8259: done
    unit: initializing embox.kernel.task.task_resource: done
    unit: initializing embox.kernel.task.task_table: done
    unit: initializing embox.driver.clock.pit: done
    unit: initializing embox.kernel.task.kernel_task: 
Embox kernel start
runlevel: init level is 0
    unit: initializing embox.driver.interrupt.i8259: done
    unit: initializing embox.kernel.task.task_resource: done
    unit: initializing embox.kernel.task.task_table: done
    unit: initializing embox.driver.clock.pit: done
    unit: initializing embox.kernel.task.kernel_task: 
Embox kernel start
runlevel: init level is 0
    unit: initializing embox.driver.interrupt.i8259: done
    unit: initializing embox.kernel.task.task_resource: done
    unit: initializing embox.kernel.task.task_table: done
    unit: initializing embox.driver.clock.pit: done
    unit: initializing embox.kernel.task.kernel_task: 
Embox kernel start
...
And so on.

It gets caught in an endless loop after calling vmem_on() function (62 line, 
/mem/mmap/mmap_mmu.c)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by drakon.m...@gmail.com on 15 Jul 2014 at 11:43

GoogleCodeExporter commented 9 years ago 
Doesn't reproduce

Original comment by deryugin...@gmail.com on 13 Mar 2015 at 12:02