Hello Vladimir,
thank you for your bug report. I can confirm that one runs into trouble when giving L4Linux much more memory than in the currently available run-scripts. This seems to be no Pandaboard-specific issue. Although the symptoms are different on different platforms. I've opened a corresponding issue in our issue tracker at Github:
https://github.com/genodelabs/genode/issues/414
Is the usage of more than 500 MB (that seems to work) on the Pandaboard currently on the critical-path for you?
With regards to the kernel-assertion you've triggered after adding more memory to the Realview platform in Fiasco.OC/L4Re: such kernel internal faults can be analyzed much better by the developers of the Fiasco.OC kernel themselves. Have a look at the l4-hackers mailing-list which is used mainly by the Fiasco.OC developers:
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers/
Best regards Stefan
On 11.10.2012 14:06, v.shilkin wrote:
Bug of 1G memory use.
*Description:*
When allow system using more than 512M of memory, user level apps execution can cause ‘Segmentation fault’ or glibc error.
Reproduction:*
*On PandaBoard:*
_In bootstrap_: in /base-foc/contrib/l4/mk/platforms/pandaboard.conf/
if set
/PLATFORM_RAM_SIZE_MB = *1024*/
(whole physical memory present on PandaBoard)//
/ /
And if allow L4Linux using more than 512M memory:
when modify run script: ‘/ports-foc/run/linux_panda.run’:/__
<start name="vmlinux.1" priority="-1">
<binary name="l4linux"/> <resource name="RAM" quantum="796M"/> <config args="mem=*754M* l4x_rd=initrd.gz"> <block label="sda" /> </config></start>
*(754M* is given for example*)*
System boots up. But user level apps can cause ‘Segmentation fault’ or glibc error.
Error is stable on command ‘*find*’ on fresh-booted system.
*On**QEMU:***
To support 1G of memory on Realview platform file ‘/base-foc/contrib/l4/pkg/bootstrap/server/src/platform/rv.cc’/ (attached) was modified. (Address regions got from platform documentation.)
On system boot below error occurs:
/Assertion failed: 'idx < _nchips' [ret=0xf006f214]/
/ /Projects/l4bsdd/base-foc/contrib/kernel/fiasco/src/kern/irq_mgr_multi_chip.cpp:76 at f0007c00/
There is no such error if Fiasco.OC was built with –O1 gcc option (only with –O2), but L4Linux can’t boot anyway because of memory allocation error.
Best regards, Vladimir Shilkin
Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main