l4-hackers October 2012

l4-hackers@os.inf.tu-dresden.de

13 participants
10 discussions

1G memory for L4Linux on Panda
by Владимир Шилкин 01 Nov '12

01 Nov '12

Hello, When allow L4Linux using more than 512M of memory, user level apps execution can cause ‘Segmentation fault’ or glibc error. For example run 'find' command on fresh booted system. We use PandaBoard. To configure system use 1Gb RAM we set in src/l4/mk/platforms/pandaboard.conf PLATFORM_RAM_SIZE_MB = 1024 Best Regards, Vladimir

2 1

how to get Task
by 朱振 01 Nov '12

01 Nov '12

hi, I want to know the memory size that each Task uses,Is there any API can help me to get this ? Thanks

2 1

Page Fault on real hardware
by Wajidali Whowe 31 Oct '12

31 Oct '12

Dear all, I have been trying to run L4linux on a real hardware (x86 PC). Everything seems fine once I try the image with the qemu, however the following error appears on the real hardware: .. .. .. vmlinuz . | main thread will be 413 vmlinuz . | l4x_register_pointer_section: addr = 005e6000 size 929792 vmlinuz . | section-with-init: virt: 0x5e6000 to 0x6c8fff [908KiB] vmlinuz . | section-with-init: virt: .... .. .. .. vmlinuz . | Loading: rom/ramdiskfs.tar.gz vmlinuz . | INITRD: Size of RAMdisk is 32768KiB vmlinuz . | RAMdisk from 188800000 to 1a800000 [32768KiB] vmlinuz . | Page fault (non-resolved): pfa=0 pc=473569 Die message: Trap: 14 vmlinuz . | panic: going to sleep forever, bye Would you please have an idea or a suggestion for this problem? Best Regards

3 7

get memory size each task uses
by 朱振 30 Oct '12

30 Oct '12

hi, I want to know the memory size that each Task uses,Is there any API that can help me to get this ? Thanks

1 0

Re: FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 30 Oct '12

30 Oct '12

Hi all, apologies for the high cross-posting traffic. I left out the information on how to subscribe to the devroom's mailing list previously: https://lists.fosdem.org/listinfo/microkernel-devroom Please, limit the discussion regarding the devroom's organization, respectively your proposals to the above list instead of replying to all organizations in this mail-header. Thank you in advance Stefan On 29.10.2012 13:01, Stefan Kalkowski wrote: > FOSDEM 2013 - Microkernels / Component-based OSes devroom > *CALL FOR PARTICIPATION* > http://fosdem.org/2013 > > The developers of several free and open-source component- and/or > microkernel-based operating systems will meet at FOSDEM 2013 in > Brussels, Belgium and will share a developer room. > > The devroom is currently looking for content in the form of talks > related to the area of component- and/or microkernel-based operating > systems. Possible topics include, but are not limited to: > > * OS introduction to developers of other OS > * Subsystems and architecture > * Hardware and device drivers > * Tools and languages > * Release engineering and testing > * Experience and learning from mistakes > * Technical challenges > * Community and life with an OS-project > * Academia and education > > Please send your talk proposal(s) no later than by 2012-12-15 to: > > microkernel-devroom at lists.fosdem.org > > Make sure to include the following in your proposal: > > * title of your talk (will be printed in the FOSDEM booklet) > * your full name (will be printed in the FOSDEM booklet) > * a short abstract > * duration of your talk (please, no longer than 45 minutes) > > The final devroom schedule (along with accepted talks) will be announced > on the above mailing list on 2012-12-22. Moreover, the speakers will be > notified via e-mail. The schedule will be also published on the FOSDEM > web and in the FOSDEM booklet after 2013-01-10. > > If you do not want to give a talk yourself, you may still send > suggestions for what else you would like to see, or do in the devroom. > Please send your suggestions to the above mailing list. > > The devroom is scheduled for Saturday of February 2. The seating > capacity of the room is 74 seats. Any changes will be announced in the > above mailing list. > -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 0

FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 29 Oct '12

29 Oct '12

FOSDEM 2013 - Microkernels / Component-based OSes devroom *CALL FOR PARTICIPATION* http://fosdem.org/2013 The developers of several free and open-source component- and/or microkernel-based operating systems will meet at FOSDEM 2013 in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks related to the area of component- and/or microkernel-based operating systems. Possible topics include, but are not limited to: * OS introduction to developers of other OS * Subsystems and architecture * Hardware and device drivers * Tools and languages * Release engineering and testing * Experience and learning from mistakes * Technical challenges * Community and life with an OS-project * Academia and education Please send your talk proposal(s) no later than by 2012-12-15 to: microkernel-devroom at lists.fosdem.org Make sure to include the following in your proposal: * title of your talk (will be printed in the FOSDEM booklet) * your full name (will be printed in the FOSDEM booklet) * a short abstract * duration of your talk (please, no longer than 45 minutes) The final devroom schedule (along with accepted talks) will be announced on the above mailing list on 2012-12-22. Moreover, the speakers will be notified via e-mail. The schedule will be also published on the FOSDEM web and in the FOSDEM booklet after 2013-01-10. If you do not want to give a talk yourself, you may still send suggestions for what else you would like to see, or do in the devroom. Please send your suggestions to the above mailing list. The devroom is scheduled for Saturday of February 2. The seating capacity of the room is 74 seats. Any changes will be announced in the above mailing list.

1 0

In l4vcpu_irq_restore function don't use l4vcpu_irq_disable(vcpu)
by Ildar Ismagilov 17 Oct '12

17 Oct '12

In function l4vcpu_irq_restore on l4/pkg/libvcpu/include/vcpu.h file: L4_CV L4_INLINE void l4vcpu_irq_restore(l4_vcpu_state_t *vcpu, l4vcpu_irq_state_t s, l4_utcb_t *utcb, l4vcpu_event_hndl_t do_event_work_cb, l4vcpu_setup_ipc_t setup_ipc) L4_NOTHROW { if (s & L4_VCPU_F_IRQ) l4vcpu_irq_enable(vcpu, utcb, do_event_work_cb, setup_ipc); } why don't call l4vcpu_irq_disable(vcpu) if "s" variable don't include L4_VCPU_F_IRQ flag? possible should be so: L4_CV L4_INLINE void l4vcpu_irq_restore(l4_vcpu_state_t *vcpu, l4vcpu_irq_state_t s, l4_utcb_t *utcb, l4vcpu_event_hndl_t do_event_work_cb, l4vcpu_setup_ipc_t setup_ipc) L4_NOTHROW { if (s & L4_VCPU_F_IRQ) l4vcpu_irq_enable(vcpu, utcb, do_event_work_cb, setup_ipc); else l4vcpu_irq_disable(vcpu); } -- Best regards Ildar

3 2

Build of ipcmon under Ubuntu 12.04
by Dustin Oprea 11 Oct '12

11 Oct '12

I'm currently stuck on building due to the ipcmon subproject and a "__sprintf_chk" error under Ubuntu 12.04: /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L741': (.text+0x4088): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x45c3): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x473b): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x4833): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `d_print_mod_list': (.text+0x62e9): undefined reference to `__sprintf_chk' make[3]: *** [ipcmon] Error 1 make[3]: Leaving directory `/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2' make[2]: *** [/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2] Error 2 make[2]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server' make: *** [server] Error 2 I tried disabling the substitution. According to the GCC documentation, any one of three separate options will do it: -fstack-protector Emit extra code to check for buffer overflows, such as stack smashing attacks. This is done by adding a guard variable to functions with vulnerable objects. This includes functions that call alloca, and functions with buffers larger than 8 bytes. The guards are initialized when a function is entered and then checked when the function exits. If a guard check fails, an error message is printed and the program exits. NOTE: In Ubuntu 6.10 and later versions this option is enabled by default for C, C++, ObjC, ObjC++, if none of -fno-stack-protector, -nostdlib, nor -ffreestanding are found. So, I added all three of the options (at the bottom) to binary.inc: CXXFLAGS+= $(BID_CFLAGS_GSTAB) $(BID_CFLAGS_OMIT_FP) CXXFLAGS+= $(CXXFLAGS_$(OSYSTEM)) CXXFLAGS+= $(CXXFLAGS_$(@:.o=.cc)) $(CXXFLAGS_$(@:.o=.cc)_$(OSYSTEM)) CXXFLAGS+= $(CXXFLAGS_$(@:.o=.cpp)) $(CXXFLAGS_$(@:.o=.cpp)_$(OSYSTEM)) CXXFLAGS+= $(OPTS) $(filter-out -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes,$(WARNINGS)) CXXFLAGS+= -fno-common -fno-stack-protector -nostdlib -ffreestanding I also added the same options on to the back of CFLAGS, just to be thorough. This is the output. As you can see, they make it into the command-line (there's some duplication due to our redundant adds), but I'm still getting the same error: ... Compiling ipcmon-server.o LD_PRELOAD=/home/dustin/tudos.build/l4/tool/gendep/libgendep.so GENDEP_TARGET=ipcmon-server.o GENDEP_BINARY=cc1 gcc -m32 -c -DLOG_TAG=\"ipcmon\" -DUSE_UCLIBC=y -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/dustin/tudos.build/l4/pkg/ipcmon/idl/OBJ-x86-l4v2 -I/home/dustin/tudos.build/l4/include/x86/l4v2 -I/home/dustin/tudos.build/l4/include/l4v2 -I/home/dustin/tudos.build/l4/include/x86 -I/home/dustin/tudos.build/l4/include -I/home/dustin/tudos/l4/../dice/include -I/home/drops/include/x86/l4v2 -I/home/drops/include/l4v2 -I/home/drops/include/x86 -I/home/drops/include -nostdinc -I/home/dustin/tudos.build/l4/include/x86/uclibc -I/home/dustin/tudos.build/l4/include/uclibc -I/home/dustin/tudos.build/l4/include/uclibc++ -I/home/drops/include/x86/uclibc -I/home/drops/include/uclibc -I/home/drops/include/uclibc++ -I/usr/lib/gcc/i686-linux-gnu/4.6/include -I/usr/lib/gcc/i686-linux-gnu/4.6/include-fixed -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common -fno-stack-protector -nostdlib -ffreestanding -fno-stack-protector -g /home/dustin/tudos.build/l4/pkg/ipcmon/idl/OBJ-x86-l4v2/ipcmon-server.c -o ipcmon-server.o ==> Linking ipcmon LD_PRELOAD=/home/dustin/tudos.build/l4/tool/gendep/libgendep.so GENDEP_TARGET=ipcmon GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld ld -m elf_i386 -o ipcmon /home/dustin/tudos.build/l4/lib/x86_586/crt0.o components.o capdescriptor.o capmanager.o blacklist.o whitelist.o ipcmon-server.o -Ttext=0x1000000 --hash-style=sysv -L/home/dustin/tudos.build/l4/lib/x86_586/l4v2 -L/home/dustin/tudos.build/l4/lib/x86_586 -L/home/dustin/tudos.build/l4/lib -L/home/drops/lib/x86_586/l4v2 -L/home/drops/lib/x86_586 -L/home/drops/lib -T/home/dustin/tudos.build/l4/lib/x86_586/main_stat.ld -lparsecmdline -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -luc_c++ -lc++start.o /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a -lmain -lcxx_base -nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i686-linux-gnu/4.6/libgcc_eh.a /usr/lib/gcc/i686-linux-gnu/4.6/libgcc.a -luc_c -ll4sys -ll4util -luc_be_minimal_io -Ttext=0x1000000 --warn-common -gc-sections /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L741': (.text+0x4088): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x45c3): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x473b): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x4833): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `d_print_mod_list': (.text+0x62e9): undefined reference to `__sprintf_chk' make[3]: *** [ipcmon] Error 1 make[3]: Leaving directory `/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2' make[2]: *** [/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2] Error 2 make[2]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server' make: *** [server] Error 2 Then, I built a test program, which builds perfectly: #include <stdio.h> void main() { char message[100]; __sprintf_chk(message, 0, 100, "Test."); printf("Out: %s\n", message); } The output: $ gcc -o sprintfchk_test sprintfchk_test.c $ ./sprintfchk_test Out: Test. I then thought "maybe it's the GCC version", since your list of dependencies indicates GCC 3 (my version is 4.6.3). So, I tried 3.0.4, 3.1.0, and 3.4.6, but none of them would build due to hard build errors (clearly, I'm missing some required flags). I'd appreciate some help with this error. Obviously, I'd prefer Ubuntu, but what distributions would you suggest for building? Dustin

3 2

Re: Build of ipcmon under Ubuntu 12.04
by Dustin Oprea 11 Oct '12

11 Oct '12

Bjoern: I've already run through the process at the L4RE link, and got the "hello" example booting in a VirtualBox instance. However, I want a full-environment.. I want a command-prompt. I'd also like to build the DOpE GUI (just to be complete). All I see there is useful only for module development and kernel development, but no instructions on how to get a full system running. Where do I go for help on that? These ambiguities are one of the reasons it has taken me so long to sit down and work on DROPS. There are many paths that seem similar to an outsider. Perhaps the group can take that old website down, for the further clarity to the outsiders and the peace-of-mind of the insiders? Dustin On Thu, Oct 11, 2012 at 11:05 AM, Björn Döbel <doebel(a)os.inf.tu-dresden.de>wrote: > Am Thu, 11 Oct 2012 10:33:51 -0400 > schrieb Dustin Oprea <myselfasunder(a)gmail.com>: > > > Thank you, Björn. > > > > I followed the directions and checked-out repomgr, which, in turn, > > downloaded what I have. The instructions are on this page: > > > > http://os.inf.tu-dresden.de/drops/download.html > > This page has been last modified 5 years ago! ;) Please use the links > below: > > > > http://os.inf.tu-dresden.de/fiasco > > > http://os.inf.tu-dresden.de/l4re > > > Bjoern > > -- > Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org > TU Dresden, OS Chair Phone: +49 351 463 38 799 > Noethnitzer Str. 46 Fax: +49 351 463 38 284 > 01187 Dresden, Germany WWW: http://www.tudos.org/~doebel > -- > "Futbol no es en simple juego. Es una arma de la revolucion!" >

2 1

About ARM11 support
by james 10 Oct '12

10 Oct '12

Hi hackers, Afaik, fiasco does not support ARM11 architecture. I wonder whether it is in progress. James --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers October 2012