l4-hackers

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

2827 discussions

nethub and l4linux
by Mikhail Savchenko 10 Nov '08

10 Nov '08

Are there any working samples of nethub with l4linux as it's broken for running with flips? There are interesting the menu.lst configuration issues for nethub and tun/tap infrastructure for l4linux setting up. Thank you.

1 0

question: is there any implementation of fiasco on s2410(samsung arm920tdmi)?
by zhhwu 10 Nov '08

10 Nov '08

hi all: i want to migrate a implementation of fiasco to s2410, is there any already existed? i find that there are implementations on SA1110 and PXA. And i find that the ARM project of Pistachio has status: discontinued. (why ?) best regards! zhhwu

3 2

L4 for Openmoko FreeRunner
by Shakthi Kannan 08 Nov '08

08 Nov '08

Hi, Where can I find documentation on using L4 with the Openmoko FreeRunner? I've seen this post for the Neo1973: http://lists.okl4.org/pipermail/developer/2007-December/000504.html Appreciate any pointers in this regard, Thanks! SK -- Shakthi Kannan http://www.shakthimaan.com

1 0

broken bootstrap, roottask and l4linux with different tools
by Valery V. Sedletski 03 Nov '08

03 Nov '08

hi all, I'm now trying to compile l4env and L4Linux under older Linux distribution (I moved to virtual machine -- VIrtual PC with RedHat 9.0 installed in it). The tools are updated -- I checked that versions of all tools are not lower than those mentioned in dev-overview.txt file. Only gcc is version 3.4.6 (on previous machine I have gcc 4.2.2), but I read it is OK. The problem is that bootstrap, roottask and l4linux kernel are not working. Bootstrap file is about 3 Mb long and is not starting by GRUB, it says "Invalid or unsupported executable format". I opened it under hex editor and it has ELF signature and some data at the beginning (probably, ELF header etc). Then goes a long run of zeroes and code is at the end. I peeked into linker script and saw that bootstrap is linked at addess 0x2d0000, which is also about 3 Mb. Maybe someone already encountered this problem? How to avoid extra zeroes? As I understand it depends on linker script, but why with different tools all is OK? (I have binutils version 2.13 and gcc 3.4.6, with 4.2.2 all is OK). And also roottask is sem-working. The simpliest configuration with pingpong test is working but when I start configuration with dm_phys, for example, DOpE with Nitpicker test: ROOT: task 7.00 at 01505f7a is trying to get page 00000000 which is reserved r --double page fault--------------------------------------IP: 0012804b [root.pager] (4.00) jdb: -- the task 7 is dm_phys. The problem is with roottask, not dm_phys because when I repalce roottassk with version, compiled with gcc 4.2.2 under Mandriva 2008.0 (I don't remember binutils version), it works. As I remember, similar error occures when a program must be started with loader to be fixed up, but was started by roottask, not the loader. But dm_phys is not reuired to be started with the loader server. Also, when I compiled l4linux with these tools, I got a pagefault at zero address with eip == address of LOG_printf() function. -- Linux starts and first tries write something to log server and traps. As I understand, two last errors are because of accessing data by zero pointer. Other binaries seem to work. What can be wrong with tools and how to avoid such effect? (Maybe someone had similar problems?) WBR, valery

2 1

L4 supporting iNotify ??
by Gianfranco Ricci 29 Oct '08

29 Oct '08

Hi at all, I am working on a project that makes it necessary to observe file system events.Therefore I plan to use the inotify subsystem from the kernel. Does L4 support inotify ?? Thanks in advance! Regards, Gianfranco

2 3

Re: Problems with l4linux
by Valery V. Sedletski 27 Oct '08

27 Oct '08

On Wed, 22 Oct 2008 19:12:59 +0200, Adam Lackorzynski wrote: > ...skipped... > >Ok. There's an option in the Fiasco configuration to let you set IOPL3 >(and thus lets you do cli/sti). This is an extra option because if you >enable it Linux can stop the machine. Anyway, that sould fix the X >problem. Now I switched on Fiasco option about IOPL 3 and an error with cli disappeared, but another problem -- GPF somewhere in Fiasco. The serial log is like this: loader | vmlinuz26: Starting application using libld-l4.s.so loader | [36mvmlinuz26,#f: Loading binary[m rtc | Date:23.10.2008 Time:08:17:15 loader | vmlinuz26,#f: Loading ldso loader | vmlinuz26,#f: Starting libld-l4.s.so at 000138e0 via 0000cbe8 l4lx | [34;1m======> L4Linux 2.6 starting... <========[0m l4lx | Linux version 2.6.26-l4-svn120-dirty2 (root@localhost) (gcc version 4 l4lx : .2.2 20071128 (prerelease) (4.2.2-3mdv2008.0)) #7 Thu Oct 23 21:07:12 l4lx : PETST 2008 l4lx | Binary name: vmlinuz26 l4lx | Linux kernel command line (8 args): mem=100M video=l4fb:refreshsleep: l4lx : 200 l4fb.nograb=1 load_ramdisk=1 ramdisk_size=40960 root=/dev/ram l4e l4lx : nv_rd=(nd)/tftpboot/drops/ramdisk/drops-fp.rd panicblink=0 l4lx | Image: 00400000 - 007b9000 [3812 KiB]. l4lx | Areas: Text: 00400000 - 006c3000 [2828kB] (a bit longer) l4lx | Data: 006c3000 - 006e46d8 [133kB] l4lx | Initdata: 006e8000 - 00726000 [248kB] l4lx | BSS: 00728000 - 007b8bb0 [578kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer0) l4lx | Tamer0 is 0f.03 l4lx | Using tamed mode. ROOT: Sending all ports (for cli/sti) to task #0d l4lx | Got 65536 out of 65536 I/O ports l4lx | Running at IOPL 3 l4lx | Connecting to l4io server. l4lx | l4lx_thread_create: Created thread 0f.04 (cpu0) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 006e6000 size = 266240 l4lx | sec-w-init: virt: 0x006e6000 to 0x00726fff [260 KiB] l4lx | sec-w-init: Number of physical regions: 1, 266240 Bytes l4lx | sec-w-init: 1: Phys: 0x012a0000 to 0x012e1000, Size: 266240 l4lx | l4env_linux_startup thread 4. l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 100MB l4lx | Main memory: virt: 0x00800000 to 0x06bfffff [102400 KiB] l4lx | Main memory: Number of physical regions: 1, 104857600 Bytes l4lx | Main memory: 1: Phys: 0x06400000 to 0x0c800000, Size: 104857600 l4lx | Filling lower ptabs... l4lx | mainmem = 800000 l4lx | Done (1060 entries). l4lx | l4env_register_pointer_section: addr = 00728000 size = 593920 l4lx | end: virt: 0x00728000 to 0x007b8fff [580 KiB] l4lx | end: Number of physical regions: 1, 593920 Bytes l4lx | end: 1: Phys: 0x006f2000 to 0x00783000, Size: 593920 l4lx | l4env_rd_path: (nd)/tftpboot/drops/ramdisk/drops-fp.rd l4lx | Loading: (nd)/tftpboot/drops/ramdisk/drops-fp.rd l4lx | INITRD: Size of RAMdisk is 40960KiB l4lx | RAMdisk from 10000000 to 12800000 [40960KiB] l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) [1;25r[25;1H [32m ---------------------------------------------------------IP: f003622b[m [32m--[mGeneral Protection [25;1H[32m[l4lx.main] (f.02) jdb: [m[K -- TRAP 000d at 0xf003622b. Here is a disassembly of Fiasco kernel: f0036224 <in_syscall>: f0036224: 59 pop %ecx f0036225: 5a pop %edx f0036226: 5e pop %esi f0036227: 5f pop %edi f0036228: 5b pop %ebx f0036229: 5d pop %ebp f003622a: 58 pop %eax f003622b: cf iret f003622c: 8d 74 26 00 lea 0x0(%esi),%esi f0036230 <entry_sys_id_nearest>: f0036230: 50 push %eax f0036231: b8 c4 37 05 f0 mov $0xf00537c4,%eax f0036236: eb c8 jmp f0036200 <all_syscalls> f0036238 <entry_sys_fpage_unmap>: f0036238: 50 push %eax f0036239: b8 c8 37 05 f0 mov $0xf00537c8,%eax f003623e: eb c0 jmp f0036200 <all_syscalls> So, this is iret instruction somewhere on return from a syscall, if I understood correctly. Maybe, my Fiasco config is wrong? globalconfig.h: /* * Automatically generated C config: don't edit * Fiasco kernel version: SVN * Thu Oct 23 21:11:17 2008 */ #define AUTOCONF_INCLUDED #define CONFIG_WARN_LEVEL 2 #define CONFIG_IA32_TARGET "Intel Pentium" #define CONFIG_POWERSAVE_GETCHAR 1 #define CONFIG_HOST_CC "gcc" #define CONFIG_IO_PROT 1 #define CONFIG_REGPARM3 1 #define CONFIG_BIT32 1 #define CONFIG_LABEL "" #define CONFIG_IO_PROT_IOPL_3 1 #define CONFIG_PERF_CNT 1 #define CONFIG_HANDLE_SEGMENTS 1 #define CONFIG_XARCH "ia32" #define CONFIG_WARN_ANY 1 #define CONFIG_CC "gcc" #define CONFIG_PF_PC 1 #define CONFIG_EXPERIMENTAL 1 #define CONFIG_HOST_CXX "g++" #define CONFIG_SCHED_PIT 1 #define CONFIG_ABI_V2 1 #define CONFIG_NO_FRAME_PTR 1 #define CONFIG_INLINE 1 #define CONFIG_SERIAL 1 #define CONFIG_DECEIT_BIT_DISABLES_SWITCH 1 #define CONFIG_GSTABS 1 #define CONFIG_ABI "v2" #define CONFIG_JDB 1 #define CONFIG_IA32 1 #define CONFIG_IA32_586 1 #define CONFIG_CXX "g++" >(My X version also tries to get ports 0-1024 (or similar) >before doing the iopl thing but AFAIK this has only been added shortly.) > -- so, in normal situation, it should not be (requesting access to some ports before doing iopl(3)), but if it takes the place, then for it to work, the Fiasco option mentioned must be enabled. But in normal situation, this option is not needed? And the question: what does cli instruction do? I guess this must trigger an I/O page fault for I/O pages to be mapped? Am I right? >> >> PS: When I did "modprobe serial_cs" udev created ttyS0..ttyS3 devices but still no comm port access. So, access to video >> >> and comm-ports don't work but network and disks are working. Why could it be? >> > >> >Sorry, no idea with the card. It doesn't say anything strange in dmesg? >> > >> >> Only that serial_cs module prints the message that it could not access >> high memory. I hope this error disappear after linux will get I/O >> privileges > >I guess not. Which address? Anyway, I guess it should ioremap those... > According to scanpci, Cardbus controller and serial (modem) card use these addresses: pci bus 0x0006 cardnum 0x09 function 0x00: vendor 0x104c device 0x8031 Texas Instruments PCIxx21/x515 Cardbus Controller STATUS 0x0210 COMMAND 0x0007 CLASS 0x06 0x07 0x00 REVISION 0x00 BIST 0x00 HEADER 0x82 LATENCY 0xa8 CACHE 0x08 BASE0 0xb8008000 addr 0xb8008000 MEM BASE1 0x020000a0 addr 0x020000a0 MEM BASE2 0xb00a0706 addr 0xb00a0700 MEM BASE3 0x88000000 addr 0x88000000 MEM BASE4 0x8bfff000 addr 0x8bfff000 MEM BASE5 0x90000000 addr 0x90000000 MEM BASEROM 0x000044fc addr 0x00000000 not-decode-enabled MAX_LAT 0x05 MIN_GNT 0xc0 INT_PIN 0x01 INT_LINE 0x0a BYTE_0 0xc0 BYTE_1 0x17 BYTE_2 0x07 BYTE_3 0x30 according to /proc/iomem: 88000000-8bffffff : PCI CardBus #07 90000000-93ffffff : PCI CardBus #07 b8008000-b8008fff : yenta_socket b8010000-b8010fff : pcmcia_socket0 And also it uses these I/O ports (according /proc/ioport): 03f8-0407 : pcmcia_socket0 03f8-03ff : serial 0400-0407 : serial 4400-44ff : PCI CardBus #07 4800-48ff : PCI CardBus #07 here 0x3f8-0x3ff is /dev/ttyS0 and 0x400-0x407 is /dev/ttyS1 WBR, valery

2 1

Problems with l4linux
by Valery V. Sedletski 23 Oct '08

23 Oct '08

>On Tue Oct 14, 2008 at 22:04:49 +1300, Valery V. Sedletski wrote: >> I have Mandriva 2008.0 distribution. >> I compiled l4linux and got some problems with it. Maybe anyone knows >> what's wrong with the configuration? >> First, the problem is with X11 (X.Org), when I'm launching X11 by >> typing startx, there is an error >> >> tal server error: >> xf86EnableIOPorts: failed to set IOPL for I/O (Invalid argument) >> >> I compiled in the L4con/DOpE stubs but X11 don't work. On ordinary >> Linux Kernel it works well. I tried to use a fbdev driver in X.Org. > >fbdev is a driver that will work. The problem is that X wants to have IO >privileges which L4Linux does not have. This is actually feature rather >than a bug. Why should X need IO privileges for just running the fbdev >driver? Anyway, add 'allow_cli' in the loader config script to the >L4Linux load line, and 'task modname "loader" allow_cli' to the roottask >cmdline and it should give L4Linux/X the rights it likes to have. I have these. My bootloader config is like this: title L4Linux 2.6 [console] kernel $(L4)\bootstrap modaddr 0x02000000 module $(L4)\fiasco $(FIASCOARGS) module $(L4)\sigma0 module $(L4)\roottask -symbols -lines task modname "loader" allow_cli task modname "bmodfs" attached 7 modules module $(L4)\fiasco_symbols module $(L4)\fiasco_lines module $(PN)\names module $(PN)\log --prio 0xA1 --buffer 0 module $(PN)\dm_phys module $(PN)\simple_ts -t 380 module $(PN)\rtc module $(PN)\l4io module $(PN)\bmodfs module $(PN)\libloader.s.so module $(PN)\libld-l4.s.so module $(PN)\run module $(CFG)\run.cfg module $(LX)\vmlinuz26 module $(CFG)\l4linux26.cfg module $(LX)\initrd.img module $(PN)\l4con module $(PN)\loader --fprov=BMODFS run.cfg l4linux26.cfg vbeset $(VMODE) and I have the following loader config file: task "vmlinuz26" "mem=1800M no-scroll video=l4fb:refreshsleep:200 l4fb.nograb=1 load_ramdisk=1 ramdisk_size=4096 root=/dev/sda9 l4env_rd=(cd)/lx/initrd.img panicblink=0" allow_cli all_sects_writable priority 0xA0 My system is on /dev/sda9 (a partition on SATA harddisk). I boot it from a CD-ROM with L4 files, linux kernel and initrd on it. Here, removing "all_sects_writable" makes no difference. What interesting, with these settings the system is loading, the only warning a system gives is a warning that can't sync hardware clock with system timer, iopl(3) call failed; and also I cannot start X11. But access to eg. disks works. >> Also, each time I access /dev/null, the message is displayed that >> access is denied. > >How do you try to access it? /dev/null should look like this: >0 crw-rw-rw- 1 root root 1, 3 Jan 1 00:00 /dev/null yes, it appeared that the permissions for /dev/null were crw-r--r--, so users, other than root, have not write permission My fault... but I thought it something related with X11 not starting. >> Third, I got PCMCIA GPRS modem to power up and register in a GSM >> network (power Led is on and Network available Led is flashing). This >> modem appears to an OS like ordinary PCMCIA comm port, but minicom >> does not react to AT commands, though, PCMCIA stack detected the card, >> but did not enabled ttyS0 and ttyS1 ports on the card. It seems I >> loaded all PCMCIA stack modules and hotplug support. Except for >> serial_cs module which warns that "no high memory space available!". >> When I did configuring the linux Kernel, the build system did not give >> me a possibility to specify high memory up to 4 Gb. What should I do >> with it? > >Is the modem really using ttyS0? ttyS0 is used by Fiasco for the serial >console and thus not available to L4Linux (or any other app). You can >specify '-noserial' on the Fiasco command line to disable the usage of >ttyS0. Yes, the modem has two comm ports that could be accessed equally. In normal Linux they are ttyS0 and ttyS1. I removed "-serial" option from bootstrap command line and changed "-serial" to "-noserial" in the command line of fiasco. But still no result. I created /dev/ttyS0 by "mknod /dev/ttyS0 c 4 64" and likewise for ttyS1. When I tried to launch minicom, it says that no such device or address. After I did "modprobe serial_cs", minicom started but it still does not react to AT commands, so it seems that serial driver don't work. Maybe, serial_cs is wrong driver or this is the result of having not all I/O privileges? >> Fourth, I thied a wifi MiniPCI card Intel PRO/Wireless 2200 to get >> working in l4linux. I tried to load all wifi modules like in ordinary >> Linux kernel on the same machine, but when I trying to make the >> network interface up, it says that device does not exists. When I >> check dmesg output, there is a message that a firmware could not be >> loaded. I unchecked the checkbox "Prevent the firmware from being >> built" and "Do not enable drivers which require firmware loading" and >> it seems that firmware must be built. The firmware is in /lib/firmware >> and is called ipw2200-bss.fw. What should I do to get firmware loaded? > >The FW_LOADER config option is not enabled. I guess this needs to be so. I had CONFIG_FW_LOADER enabled but there was "CONFIG_FW_LOADER=m", not "CONFIG_FW_LOADER=y". I changed this option to the latter and recompiled the kernel, but firmware still not loading. So, it won't help. The error is like this: Oct 17 15:10:49 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Oct 17 15:10:49 localhost kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation Oct 17 15:10:49 localhost kernel: __l4x_ioremap: Requested region at b8006000 [0x1000 Bytes] Oct 17 15:10:49 localhost kernel: __l4x_ioremap: Mapping physaddr b8006000 [0x1000 Bytes, b8006000+001000] to 3f58a000+000000 Oct 17 15:10:49 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Oct 17 15:10:49 localhost kernel: firmware: requesting ipw2200-bss.fw Oct 17 15:11:49 localhost kernel: ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 Oct 17 15:11:49 localhost kernel: ipw2200: Unable to load firmware: -2 Oct 17 15:11:49 localhost kernel: ipw2200: failed to register network device Oct 17 15:11:49 localhost kernel: ipw2200: probe of 0000:06:05.0 failed with error -5 -- This is from dmesg output. Maybe, I missed something other? >> And the last, I tried to build l4linux under l4linux itself. The build >> is generally working, except for when doing "make modules_install" >> depmod crashes. Should I report these errors or they are known >> problems? > >Is it depmod or something different? depmod should work as Debian >systems running it on every boot-up. Please report, I'll try to fix as I >can. Yes, I compiled the kernel and did "make modules_install". It copied modules to /lib/modules and started to make files describing the modules. Then a set of messages with call trace appeared and a message that "depmod killed". What is interesting, depmod worked when the number of modules was relatively small. But when it was more than 700 modules, it crashed. What should I do to report the error? The messages are at linux console, not on commport, so is there a way to copy these messages? (The only way I see is to copy the parts of messages from screen using gpm mouse server). WBR, valery

2 8

Boot Fiasco@ARM on QEMU
by Tsai, Tung-Chieh 21 Oct '08

21 Oct '08

Dear All, I'm try to boot fiasco kernel which is compiled to integrator(arm926) on QMEU. I see this thread : http://osdir.com/ml/micro-kernel.l4.devel/2007/msg00303.html So I guess it should be worked. But I got some problem, when I use the following command : qemu-system-arm -kernel fiasco.image -serial stdio -d in_asm there is no output on QEMU. I watch the log of QEMU, find that it fails to go to '_start_kernel' in 0xf0003000 from 'bootstrap_main' because there is nothing in 0xf0003000. As I know, there is no physical memory in QEMU's integratorcp emulation. It only put memory on 0x0 and 0x80000000. So I guess the way I try is wrong, there must be something I lost. Do I have to use some kind of bootloader like grub in ia32 or putting some file by initrd, mtdblock, etc... And couold anyone give some advice about how to run it on QEMU. Best Regards, Tsai, Tung-chieh

3 11

menu.lst
by Mikhail Savchenko 20 Oct '08

20 Oct '08

Hi ,there Can somebody introduce the examples of menu.lst for starting fiasco with working demo configuration of flips and nethub? Thank you

2 1

fiasco boot sequence on arm
by Qmo (Yi-Sheng) 19 Oct '08

19 Oct '08

Dear all, I am working on a project which porting fiasco to a ARM&DSP platform. Now I have questions about the fiasco boot sequence in arm side. First, when doing a workable kernel image, we should use the l4 package *[1]"bootstrap" (l4/pkg/bootstrap)* to encapsulate the needed modules, for example: roottask, sigma0, and the real fiasco kernel(it means the building image in kernel/fiasco/builddir/fiasco.image). And we find the file "l4/pkg/bootstrap/server/src/startup.cc", there are some source code lines like: #elif defined(ARCH_arm) typedef void (*startup_func)(void); * startup_func f = (startup_func)boot_info.kernel_start;* f(); #else the command line says that "setup the L4 kernel info page before booting the L4 microkernel", but we want to know what is the entry point about *boot_info.kernel_start*in the real fiasco kernel(fiasco.image) source codes? And we also find that there is also a file named *[2]bootstrap in kernel/fiasco/src/kern/arm/bootstrap.cpp*, this file seems to steup the memory mapping. So we guess the first bootstrap*[1]* is used to arrange the roottask, sigma0, etc... in the memory space, then jump to the second bootstrap*[2]*in fiasco kernel to setup the needed memory mapping, and finally give the control to the real fiasco kernel. We want to confirm the steps, or something is wrong? And the last question, what is the coding style about *IMPLEMENTATION [arm]: * in kernel/fiasco/src/kern/arm/ directory, is there any effect when compiling them? Thank you very much! Best Regards, Qmo

2 1

Jump to page:

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