- l4-hackers - example.com Site

Failed Assertion @ auto/kmem.h:162
by Julian Grizzard 27 Nov '05

27 Nov '05

All, I'm upgrading my Fiasco/L4Linux setup to the latest CVS version. My machine is a Pentium IV with 1 Gig RAM. Using the same configuration that worked before, I've run into an assertion problem when the system boots with the latest CVS. Below is the contents of menu.lst, L4 kernel configuration (globalconfig.out), and the boot log showing the assertion error. Further, I cannot enter the kernel debugger with "k"; instead, the offending address changes to 0xf0014fc7 with the same assertion thus failing to enter the debugger. Any idea what is wrong? Thanks! Julian ################ menu.lst ################## title L4Linux-2.6 root (hd0,0) kernel /boot/l4/rmgr -sigma0 task modname "bmodfs" module module module modaddr 0x02000000 module /boot/l4/main -nokdb -nowait -serial -comport 1 module /boot/l4/sigma0 module /boot/l4/names module /boot/l4/log module /boot/l4/dm_phys module /boot/l4/simple_ts -t 300 #module /boot/l4/rtc module /boot/l4/l4io --noirq module /boot/l4/l4exec module /boot/l4/bmodfs module /boot/l4/libloader.s.so module /boot/l4/run-script module /boot/vmlinuz26 module /boot/l4/loader --fprov=BMODFS run-script ############## /boot/l4/run-script ############### sleep 2 task "vmlinuz26" "noreplacement mem=64M root=/dev/hda1" ################ globalconfig.out ################ # # Automatically generated, don't edit # # Generated on: linux1 # At: Thu, 24 Nov 2005 18:22:02 +0000 # Linux version 2.6.8-2-686 (horms(a)tabatha.lab.ultramonkey.org) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Thu May 19 17:53:30 JST 2005 # # Main menu # CONFIG_EXPERIMENTAL=y # # Target System Options # # # Target Platform # CONFIG_PF_PC=y CONFIG_PF_UX=n CONFIG_PF_SA1100=n CONFIG_PF_XSCALE=n CONFIG_PF_ISG=n # # Target CPU Family # CONFIG_IA32=y CONFIG_ARM=n CONFIG_AMD64=n # # Target processor # CONFIG_IA32_486=n CONFIG_IA32_586=n CONFIG_IA32_686=n CONFIG_IA32_P2=n CONFIG_IA32_P3=n CONFIG_IA32_P4=y CONFIG_IA32_PM=n CONFIG_IA32_K6=n CONFIG_IA32_K7=n CONFIG_IA32_K8=n # # Target processor # CONFIG_AMD64_K8=n CONFIG_REGPARM3=y # # Kernel Options # # # Kernel ABI Version # CONFIG_ABI_V2=y CONFIG_ABI_X0=n # # ABI Extensions # CONFIG_DECEIT_BIT_DISABLES_SWITCH=y CONFIG_KIP_SYSCALLS=n CONFIG_MULTI_IRQ_ATTACH=n CONFIG_EXCEPTION_IPC=y CONFIG_SYSCALL_ITER=y CONFIG_HANDLE_SEGMENTS=y CONFIG_LOCAL_IPC=n CONFIG_ACTIVATION_IPC=n CONFIG_PL0_HACK=n CONFIG_ASSEMBLER_IPC_SHORTCUT=n CONFIG_SMALL_SPACES=n CONFIG_CONTEXT_4K=y # # Scheduling Timer # CONFIG_SCHED_PIT=y CONFIG_SCHED_RTC=n CONFIG_SCHED_APIC=n CONFIG_ONE_SHOT=n CONFIG_SYNC_TSC=n CONFIG_FINE_GRAINED_CPUTIME=n CONFIG_IO_PROT=n CONFIG_UX_CON=n CONFIG_UX_NET=n # # Kernel Debugging # CONFIG_INLINE=y CONFIG_NDEBUG=n CONFIG_PROFILE=n CONFIG_NO_FRAME_PTR=n CONFIG_STACK_DEPTH=n CONFIG_LIST_ALLOC_SANITY=n CONFIG_BEFORE_IRET_SANITY=n CONFIG_GSTABS=y CONFIG_POWERSAVE_GETCHAR=y CONFIG_SERIAL=y CONFIG_KDB=y CONFIG_JDB=y CONFIG_JDB_LOGGING=n CONFIG_JDB_ACCOUNTING=n CONFIG_JDB_MISC=n CONFIG_WATCHDOG=y # # Runtime warning level # CONFIG_WARN_NONE=n CONFIG_WARN_ANY=y # # Compiling and Building # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_VERBOSE=n CONFIG_MAINTAINER_MODE=n # # Derived symbols # CONFIG_BIT32=y CONFIG_XARCH="ia32" CONFIG_IA32_TARGET="Intel Pentium 4" CONFIG_WARN_LEVEL=2 CONFIG_BIT64=n CONFIG_PERF_CNT=y CONFIG_ABI="v2" # # That's all, folks! ################# BOOT LOG ################# [Multiboot-elf, <0x100000:0x20e18:0x0>, <0x121e20:0x49fc:0xa4784>, shtab=0x1 cb2f8, entry=0x100000] modaddr 0x02000000 Setting module load address to 0x2000000 module /boot/l4/main -nokdb -nowait -serial -comport 1 [Multiboot-module @ 0x2000000, 0x591ac bytes] module /boot/l4/sigma0 [Multiboot-module @ 0x205a000, 0xe94b bytes] module /boot/l4/names [Multiboot-module @ 0x2069000, 0x2a831 bytes] module /boot/l4/log [Multiboot-module @ 0x2094000, 0x26a93 bytes] module /boot/l4/dm_phys [Multiboot-module @ 0x20bb000, 0x5f2b2 bytes] module /boot/l4/simple_ts -t 300 [Multiboot-module @ 0x211b000, 0x2ef4f bytes] module /boot/l4/l4io --noirq [Multiboot-module @ 0x214a000, 0x1d1360 bytes] module /boot/l4/l4exec [Multiboot-module @ 0x231c000, 0xf4b72 bytes] module /boot/l4/bmodfs [Multiboot-module @ 0x2411000, 0x88b4c bytes] module /boot/l4/libloader.s.so [Multiboot-module @ 0x249a000, 0x88c3f bytes] module /boot/l4/run-script [Multiboot-module @ 0x2523000, 0x40 bytes] module /boot/vmlinuz26 [Multiboot-module @ 0x2524000, 0xd967f6 bytes] module /boot/l4/loader --fprov=BMODFS run-script [Multiboot-module @ 0x32bb000, 0xc8ed6 bytes] Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Tue Nov 22 22:45:10 2005 compiled with gcc 3.3.5 for Intel Pentium 4 Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling CPU: GenuineIntel (F:2:7:9) Model: Pentium 4 (Northwood/Prestonia) at 2519 MHz 128 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 8 KB L1 D Cache (4-way associative, 64 bytes per line) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) Assertion failed: 'Mem_layout::Tcbs_end == Mem_layout::Tcbs + (Config::thread_block_size * Config::max_threads())' in auto/kmem.h:162 at f0007cb1 Return reboots, "k" enters L4 kernel debugger... <k> Assertion failed: 'Mem_layout::Tcbs_end == Mem_layout::Tcbs + (Config::thread_block_size * Config::max_threads())' in auto/kmem.h:162 at f0014fc7 Return reboots, "k" enters L4 kernel debugger...

2 2

L4Linux on fiasco UX problem
by Jugwan Eom 24 Nov '05

24 Nov '05

Hi, I tried runnig L4Linux on fiasco UX but it didn't work. I enabled three options for the L4Linux. (Exception IPC / Inter-task ex-regs syscall / Handle and preserve segments) I have no idea why l4linux causes the trap. Anyone could help me? Followings are log and disassembling of vmlinux. Thanks in advance. ------------------------------------------------------------------------------------ $ ./lx con /home/zugwan/boot/fiasco_ux/fiasco -m 256 -symbols /home/zugwan/boot/fiasco_ux/Symbols -lines /home/zugwan/boot/fiasco_ux/Lines -rmgr /home/zugwan/boot/l4bin/rmgr-ux -symbols -lines -sigma0 /home/zugwan/boot/l4bin/sigma0-ux -fb_program /home/zugwan/boot/fiasco_ux/ux_con -irq0 /home/zugwan/boot/fiasco_ux/irq0 -t 32768 -G 640x480@16 -l /home/zugwan/boot/l4bin/names -l /home/zugwan/boot/l4bin/log -l /home/zugwan/boot/l4bin/dm_phys -l /home/zugwan/boot/l4bin/simple_ts -l /home/zugwan/boot/l4bin/fuxfprov -n9 -l /home/zugwan/boot/l4bin/rtc-ux -n10 -l /home/zugwan/boot/l4bin/l4exec -l /home/zugwan/boot/l4bin/con-ux -n12 -l /home/zugwan/boot/l4bin/loader /home/zugwan/boot/l4bin/run /home/zugwan/boot/cfg/l4linux26.ux Fiasco-UX on Linux 2.6.10-5-386 (i686) Native Syscall Map: 0x1600 Mapped 256 MB Memory + 4096 KB Framebuffer + 4 MB Input Area on FD 3 Loading Module 0x00090000-0x00094dc0 [/home/zugwan/boot/l4bin/sigma0-ux] Loading Module 0x00100000-0x001c61c0 [/home/zugwan/boot/l4bin/rmgr-ux] Copying Module 0x0ea66000-0x0ea843d6 [/home/zugwan/boot/fiasco_ux/Symbols] Copying Module 0x0ea33000-0x0ea6518f [/home/zugwan/boot/fiasco_ux/Lines] Copying Module 0x0ea08000-0x0ea327ac [/home/zugwan/boot/l4bin/names] Copying Module 0x0e9e1000-0x0ea0745f [/home/zugwan/boot/l4bin/log] Copying Module 0x0e982000-0x0e9e000d [/home/zugwan/boot/l4bin/dm_phys] Copying Module 0x0e953000-0x0e981b65 [/home/zugwan/boot/l4bin/simple_ts] Copying Module 0x0e8b1000-0x0e95281f [/home/zugwan/boot/l4bin/fuxfprov] Copying Module 0x0e88e000-0x0e8b0273 [/home/zugwan/boot/l4bin/rtc-ux] Copying Module 0x0e7a1000-0x0e88dd64 [/home/zugwan/boot/l4bin/l4exec] Copying Module 0x0e6d9000-0x0e7a0c7f [/home/zugwan/boot/l4bin/con-ux] Copying Module 0x0e619000-0x0e6d8a04 [/home/zugwan/boot/l4bin/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Nov 24 08:46:52 2005 compiled with gcc 3.4.4 for Intel Pentium Starting Framebuffer: 640x480@16 CPU: GenuineIntel (F:4:1:0) Model: Pentium 4E (Prescott/Nocona) at 3190 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K \uffff-ops T Cache (8-way associative) 16 KB L1 D Cache (8-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 68kB for maintenance structures. RMGR: Hello! running on Fiasco bootloader loaded 9 modules at 0e619000-0ea843d7 L4 symbols at 0e5fa000-0e6183d8 (120kB), lines at 0e5c7000-0e5f918f (200kB) total RAM size = 261120 KB (reported by bootloader) received 239300 KB RAM from sigma0 1128 KB reserved for RMGR received no I/O ports attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 a b c d e f ] RMGR: Starting tasks. #05: loading "/home/zugwan/boot/l4bin/names " from 0ea08000-0ea327ac to [ 00240000-002467ea 00247000-00253000 ] starting at entry 00240000 via trampoline page code 0000c464 symbols at 0ea86000-0ea88000 (8kB), lines at 0ea81000-0ea86000 (20kB) #06: loading "/home/zugwan/boot/l4bin/log" from 0e9e1000-0ea0745f to [ 00400000-00406c11 00407000-00439510 ] starting at entry 00400000 via trampoline page code 0000d460 symbols at 0ea7f000-0ea81000 (8kB), lines at 0ea7a000-0ea7f000 (20kB) #07: loading "/home/zugwan/boot/l4bin/dm_phys " from 0e982000-0e9e000d to [ 01500000-01511baa 01512000-015193d0 ] starting at entry 01500000 via trampoline page code 0000e468 symbols at 0ea76000-0ea7a000 (16kB), lines at 0ea6a000-0ea76000 (48kB) #08: loading "/home/zugwan/boot/l4bin/simple_ts " from 0e953000-0e981b65 to [ 01400000-01407ede 01408000-01413830 ] starting at entry 01400000 via trampoline page code 0000f468 symbols at 0ea68000-0ea6a000 (8kB), lines at 0ea62000-0ea68000 (24kB) #09: loading "/home/zugwan/boot/l4bin/fuxfprov" from 0e8b1000-0e95281f to [ 00500000-00521c96 00522000-0053e000 ] starting at entry 00500000 via trampoline page code 00010468 symbols at 0ea5d000-0ea62000 (20kB), lines at 0ea4a000-0ea5d000 (76kB) #0a: loading "/home/zugwan/boot/l4bin/rtc-ux" from 0e88e000-0e8b0273 to [ 01080000-01084abd 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 00011464 symbols at 0ea48000-0ea4a000 (8kB), lines at 0ea44000-0ea48000 (16kB) #0b: loading "/home/zugwan/boot/l4bin/l4exec" from 0e7a1000-0e88dd64 to [ 01100000-01127dee 01128000-01132000 ] starting at entry 01100000 via trampoline page code 00012464 symbols at 0ea3c000-0ea44000 (32kB), lines at 0ea24000-0ea3c000 (96kB) #0c: loading "/home/zugwan/boot/l4bin/con-ux " from 0e6d9000-0e7a0c7f to [ 00b00000-00b23fe2 00b24000-00b2f000 ] starting at entry 00b00000 via trampoline page code 00013464 symbols at 0ea1d000-0ea24000 (28kB), lines at 0ea05000-0ea1d000 (96kB) #0d: loading "/home/zugwan/boot/l4bin/loader /home/zugwan/boot/l4bin/run /home/zugwan/boot/cfg/l4linux26.ux" from 0e619000-0e6d8a04 to [ 01300000-01325306 01326000-01338000 ] starting at entry 01300000 via trampoline page code 000144a4 symbols at 0e9ff000-0ea05000 (24kB), lines at 0e9e9000-0e9ff000 (88kB) simplets| Configured for 64 tasks. fuxfprov| OSKit support: using 128KB at 0x00100000 as heap (growing) fuxfprov| File provider started, registered as 9.02 exec | OSKit support: using 4096KB at 0x00400000 as heap (growing) con | OSKit support: using 128KB at 0x00100000 as heap con | Character size is 8x14, font has 256 characters con | VESA reports 640x480@16 1280bpl (0000) [4096kB] con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 con | Found Fiasco/UX con | Found VHW descriptor, provider is 24195 con | Mapping I/O UX video mem c0000000 => 00400000+000000 [4096kB] con | Using MMXEXT for colorspace transform con | map_inputmemory: paddr = 0xc0400000 con | Input memory page mapped to 0x00c00000 loader | OSKit support: using 128KB at 0x00100000 as heap loader | Can't map tbuf status page (map=00004000, error=00 result=00004000) con | Started input interrupt thread C.03! con | Running as C.02. Video mode is 640x480@16. fuxfprov| open "/home/zugwan/boot/l4bin/run" by D.02 loader | "/home/zugwan/boot/l4bin/run" is a valid binary image loader | Setting libpath to /home/zugwan/boot/l4bin/ exec | run: Loading exec | run: Merging psec 01312000-01314000 with psec 0130d000-01313000 exec | run: Saved 14133 bytes of symbols exec | libloader.s.so: Loading fuxfprov| open "/home/zugwan/boot/l4bin//libloader.s.so" by B.02 exec | libloader.s.so: Saved 21533 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 00004ff0 => 00014ff0 exec | libloader.s.so: Setting section flag 0800 exec | run: Setting section flag 0800 loader | run: Starting l4env-style application loader | run,#e: Starting at l4loader_init (000156a0) exec | run: Linking exec | run: Relocating entry 01300000 => 01300000 exec | run: Packed 25941 bytes of symbols exec | run: Packed 96567 bytes of lines loader | run,#e: Continue at l4env_init (000156b0, libloader.s.so) fuxfprov| open "/home/zugwan/boot/cfg/l4linux26.ux" by D.02 loader | sleeping for 1000 ms run | OSKit support: using 256KB at 0x00040000 as heap (growing) con | vc_loop(): vc[1] running as C.04 con | vc_open_out(): vc[1] 640x480@16, gmode:0x15 run | contxt_init(): 640x462, cols:80, lines:33, sb_lines:1033 fuxfprov| open "/home/zugwan/boot/lx/vmlinuz26.ux" by D.02 exec | vmlinuz26.ux: Loading exec | vmlinuz26.ux: Interpreter section found, contains "/usr/lib/libc.so.1 exec : " exec | vmlinuz26.ux: Saved 756346 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 00004ff0 => 00014ff0 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26.ux: Setting section flag 0800 loader | vmlinuz26.ux: Starting l4env-style application loader | vmlinuz26.ux,#f: Starting at l4loader_init (000156a0) exec | vmlinuz26.ux: Linking exec | vmlinuz26.ux: Relocating entry 00400000 => 00400000 exec | vmlinuz26.ux: Packed 600616 bytes of symbols exec | vmlinuz26.ux: Packed 1616968 bytes of lines loader | vmlinuz26.ux,#f: Continue at l4env_init (000156b0, libloader.s.so) l4lx | crt0_construction called. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Binary name: vmlinuz26.ux l4lx | Kernel command line (8 args): mem=44M noreplacement root=1:0 load_ram l4lx : disk=1 ramdisk_size=16384 l4env_rd=/home/zugwan/boot/rd/rd1 panicblin l4lx : k=0 lang=us l4lx | Image: 00400000 - 0068a1a0 [2600 KiB]. l4lx | Areas: Text: 00400000 - 005b5000 [1748kB] (a bit longer) l4lx | Data: 005b5000 - 005f04cc [237kB] l4lx | Initdata: 005f4000 - 00618000 [144kB] l4lx | BSS: 00618008 - 0068a1a0 [456kB] l4lx | l4lx_thread_create: Created thread 0f.03 (server) l4lx | main thread will be 0f.03 l4lx | l4env_register_pointer_section: addr = 005f2000 size = 159744 l4lx | sec-w-init: virt: 0x005f2000 to 0x00618fff [156 KiB] l4lx | sec-w-init: Number of physical regions: 1, 159744 Bytes l4lx | sec-w-init: 1: Phys: 0x00f69000 to 0x00f90000, Size: 159744 l4lx | l4env_linux_startup thread 3. l4lx | main thread: received startup message. l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 44MB l4lx | Main memory: virt: 0x00800000 to 0x033fffff [45056 KiB] l4lx | Main memory: Number of physical regions: 1, 46137344 Bytes l4lx | Main memory: 1: Phys: 0x0b800000 to 0x0e400000, Size: 46137344 l4lx | Filling lower ptabs... l4lx | Main thread running, waiting... l4lx | Done (1263 entries). l4lx | l4env_rd_path: /home/zugwan/boot/rd/rd1 l4lx | Loading: /home/zugwan/boot/rd/rd1 fuxfprov| open "/home/zugwan/boot/rd/rd1" by F.03 l4lx | INITRD: Size of RAMdisk is 16384KiB l4lx | RAMdisk from 03400000 to 04400000 [16384KiB] l4lx | l4lx_thread_create: Created thread 0f.04 (timer.i0) KERNEL: f.3 (tcb=00000000203c1800) killed: Unhandled trap ip:60965b EAX 00000001 EBX 00000001 ECX 0107fe80 EDX 00000cfb ESI 00000000 EDI 00828000 EBP 00829fa4 ESP 00829f98 EIP 0060965b EFLAGS 00010046 CS 0002 SS 007b DS 007b ES 007b FS 0000 GS 0007 trap 13 (General Protection), error 00000000, from user mode (internal event regarding GDT entry no. 0x00) --------------------------------------------------------------------------------------------------- /home/zugwan/l4/l4linux-2.6/vmlinux: file format elf32-i386 Disassembly of section .text: Disassembly of section .plt: Disassembly of section .init.text: 006095db <pci_sanity_check+0x3b>: pci_sanity_check(): /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:193 6095db: 83 c4 18 add $0x18,%esp 6095de: 85 c0 test %eax,%eax 6095e0: 75 e4 jne 6095c6 <pci_sanity_check+0x26> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:195 6095e2: 8b 45 f0 mov 0xfffffff0(%ebp),%eax 6095e5: 3d 00 06 00 00 cmp $0x600,%eax 6095ea: 0f 94 c2 sete %dl 6095ed: 3d 00 03 00 00 cmp $0x300,%eax 6095f2: 0f 94 c0 sete %al 6095f5: 09 d0 or %edx,%eax 6095f7: a8 01 test $0x1,%al 6095f9: 75 2c jne 609627 <pci_sanity_check+0x87> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:198 6095fb: 56 push %esi 6095fc: 6a 02 push $0x2 6095fe: 6a 00 push $0x0 609600: 53 push %ebx 609601: 6a 00 push $0x0 609603: 6a 00 push $0x0 609605: ff 17 call *(%edi) 609607: 83 c4 18 add $0x18,%esp 60960a: 85 c0 test %eax,%eax 60960c: 75 b8 jne 6095c6 <pci_sanity_check+0x26> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:200 60960e: 8b 45 f0 mov 0xfffffff0(%ebp),%eax 609611: 3d 86 80 00 00 cmp $0x8086,%eax 609616: 0f 94 c2 sete %dl 609619: 3d 11 0e 00 00 cmp $0xe11,%eax 60961e: 0f 94 c0 sete %al 609621: 09 d0 or %edx,%eax 609623: a8 01 test $0x1,%al 609625: 74 9f je 6095c6 <pci_sanity_check+0x26> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:201 609627: b8 01 00 00 00 mov $0x1,%eax /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:206 60962c: 8d 65 f4 lea 0xfffffff4(%ebp),%esp 60962f: 5b pop %ebx 609630: 5e pop %esi 609631: 5f pop %edi 609632: 5d pop %ebp 609633: c3 ret /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:205 609634: 31 c0 xor %eax,%eax 609636: eb f4 jmp 60962c <pci_sanity_check+0x8c> 609638: 90 nop 609639: 8d b4 26 00 00 00 00 lea 0x0(%esi),%esi 00609640 <pci_check_type1>: pci_check_type1(): /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:209 609640: 55 push %ebp 609641: 89 e5 mov %esp,%ebp 609643: 56 push %esi 609644: 53 push %ebx 609645: 51 push %ecx /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:214 609646: e8 a5 7c df ff call 4012f0 <l4x_local_save_flags> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:212 60964b: 31 f6 xor %esi,%esi /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:214 60964d: 89 c3 mov %eax,%ebx 60964f: e8 7c 7c df ff call 4012d0 <l4x_local_irq_disable> /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:395 609654: b0 01 mov $0x1,%al 609656: ba fb 0c 00 00 mov $0xcfb,%edx 60965b: ee out %al,(%dx) /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:397 60965c: b2 f8 mov $0xf8,%dl 60965e: ed in (%dx),%eax 60965f: 89 45 f4 mov %eax,0xfffffff4(%ebp) 609662: b8 00 00 00 80 mov $0x80000000,%eax 609667: ef out %eax,(%dx) 609668: ed in (%dx),%eax 609669: 3d 00 00 00 80 cmp $0x80000000,%eax 60966e: 74 20 je 609690 <pci_check_type1+0x50> 609670: ba f8 0c 00 00 mov $0xcf8,%edx 609675: 8b 45 f4 mov 0xfffffff4(%ebp),%eax 609678: ef out %eax,(%dx) /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:223 609679: 53 push %ebx 60967a: e8 81 7c df ff call 401300 <l4x_local_irq_restore> 60967f: 58 pop %eax /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:226 609680: 8d 65 f8 lea 0xfffffff8(%ebp),%esp 609683: 89 f0 mov %esi,%eax 609685: 5b pop %ebx 609686: 5e pop %esi 609687: 5d pop %ebp 609688: c3 ret 609689: 8d b4 26 00 00 00 00 lea 0x0(%esi),%esi /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:397 609690: 68 58 82 5c 00 push $0x5c8258 609695: e8 06 ff ff ff call 6095a0 <pci_sanity_check> 60969a: 5a pop %edx 60969b: 85 c0 test %eax,%eax 60969d: 74 d1 je 609670 <pci_check_type1+0x30> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:220 60969f: 66 be 01 00 mov $0x1,%si 6096a3: eb cb jmp 609670 <pci_check_type1+0x30> 6096a5: 8d 74 26 00 lea 0x0(%esi),%esi 6096a9: 8d bc 27 00 00 00 00 lea 0x0(%edi),%edi 006096b0 <pci_check_type2>: pci_check_type2(): /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:229 6096b0: 55 push %ebp 6096b1: 89 e5 mov %esp,%ebp 6096b3: 57 push %edi 6096b4: 56 push %esi 6096b5: 53 push %ebx /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:233 6096b6: e8 35 7c df ff call 4012f0 <l4x_local_save_flags> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:231 6096bb: 31 f6 xor %esi,%esi /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:233 6096bd: 89 c3 mov %eax,%ebx 6096bf: e8 0c 7c df ff call 4012d0 <l4x_local_irq_disable> /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:395 6096c4: 31 c0 xor %eax,%eax 6096c6: ba fb 0c 00 00 mov $0xcfb,%edx 6096cb: ee out %al,(%dx) 6096cc: bf f8 0c 00 00 mov $0xcf8,%edi 6096d1: 89 fa mov %edi,%edx 6096d3: ee out %al,(%dx) 6096d4: b9 fa 0c 00 00 mov $0xcfa,%ecx 6096d9: 89 ca mov %ecx,%edx Disassembly of section .altinstr_replacement: Disassembly of section .exit.text:

2 1

ANNOUNCE: Qualcomm uses L4!
by Gernot Heiser 23 Nov '05

23 Nov '05

NICTA today announced a collaborative effort with QUALCOMM Incorporated to use NICTA versions of the L4 Microkernel and the Iguana operating system together with select versions of QUALCOMM's Mobile Station)TM) chipsets. See http://www.ertos.nicta.com.au/press/051124_L4_Qualcomm_vfinal.pdf for the full press release. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

ANNOUNCE: NICTA embedded OS framework released
by Gernot Heiser 23 Nov '05

23 Nov '05

The NICTA ERTOS team is pleased to announce the fist official release of its embedded OS framework, consisting of: * NICTA::Pistachio-embedded, the first kernel conforming to the L4-embedded API. NICTA::Pistachio is based on L4Ka::Pistachio; * Iguana, an L4-based OS personality developed specifically for embedded systems; * Kenge, a set of packages for building microkernel-based systems; * Wombat, a de-privileged (para-virtualised) Linux server running on top of L4/Iguana. Presently the full package works on ARM and x86 platforms. MIPS64 is fully supported except for Wombat (which is due for release shortly) and an Alpha version is not far behind. The system is very mature (in commercial deployment); NICTA::Pistachio-embedded is the fastest and most mature L4 kernel on ARM. See also the http://www.ertos.nicta.com.au/Research/news/. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

Re: What happens on timeslice overrun?
by Udo A. Steinberg 23 Nov '05

23 Nov '05

On Sun, 14 Aug 2005 22:16:09 +0200 Rene Wittmann (RW) wrote: RW> I have 2 questions on the RT part in DROPS: RW> RW> 1.) I have 2 RT working threads, each with 3 timeslices: RW> Thread 1: period=10ms RW> ts1=30ms prio1=50 RW> ts2=10ms prio2=30 RW> ts3=20ms prio3=50 RW> RW> Thread 2: period=10ms RW> ts1=20ms prio1=40 RW> ts2=5ms prio2=30 RW> ts3=10ms prio3=40 RW> RW> Assume both threads are ready at the same time. RW> So thread 1 starts and does its work until it RW> releases the voluntarily or it's preempted by RW> its preempter-thread. So say it releases RW> voluntarily after 20ms. When you say "it's preempted by its preempter thread", do you mean the situation when a preempter with a higher priority than the current thread receives a preemption IPC from the kernel and thus preempts the current thread? RW> Who will get the left 10ms? I guess nobody. When a thread is preempted (that means it gets involuntarily descheduled), the remaining time quantum is saved and later restored when the thread is scheduled again. If the thread yields its scheduling context (that means it voluntarily gives it away), the time quantum is no longer available to the thread. A yield can happen in two ways depending on the target thread id specified: 1) if the target ID is the NIL_ID, then the thread yields its active scheduling context to noone - the time is effectively gone. This is what next_reservation does. Note that the kernel checks the user-specified ID, to guard against the case where a thread wants to yield its active scheduling context and the time quantum on that scheduling context expires simultaneously. 2) if the target ID is a valid thread ID in the system, then the action depends on whether the specified thread is ready to run: a) if it is, then the current thread donates the current scheduling context to the specified thread and that thread then becomes the current thread. This is similar to what happens during a donating IPC. b) if the specified thread is not ready, then the current scheduling context is gone, similar to 1) RW> Or can I assign my left time to a specific RW> thread, say ts2 of thread 1, that is has 20ms RW> after recognizing that ts1 was finished 10ms RW> earlier?I could do with l4_rt_change_timeslice(), RW> but this would probably not work for the the RW> current period! (or yes?) A thread can yield the current scheduling context to another thread as described in 2a) above. Note that the thread will yield the current scheduling context (which may not necessarily be the thread's own active scheduling context). As an example consider: A sends a donating IPC to B, now B runs on A's scheduling context. If B yields to C, then C will run on A's time and B will not donate its own scheduling context. If the current scheduling context is in fact the active scheduling context of the donating thread, then realize that the donating thread will likely encounter a timeslice overrun soon after the yield (the donatee will consume the time quantum until it runs out). If you'd rather avoid that, then the donatee will have to yield the scheduling context back to the owner (the original donator) who then has to yield it to noone. Changes to the time quantum of a scheduling context are only visible the next time that scheduling context becomes the current scheduling context. That means if you change the current scheduling context, then the change will not be visible immediately. RW> 2.) Consider we have a deadline miss. And we say RW> l4_rt_next_period(): would it wait for the beginning RW> of the next (which means: RW> period 1: deadline miss RW> period 2: call next period (because we think we're RW> still in period 1)+ wait to end of period RW> period 3: normal work) RW> Or do I have to care that we do not call RW> l4_rt_next_period() in case of a deadline miss? If your thread misses its deadline right before it wanted to call l4_rt_next_period, then l4_rt_next_period blocks the thread until the end of the new period started due to the deadline miss. Since this is likely not what the thread intended to do, it's the preempter's job to handle that situation, e.g. by ex_regs'ing the thread out of it's l4_rt_next_period call. RW> BTW: I compiled the fiasco-kernel with apic+one shot RW> mode. But this should not be relevant for my question. It is indeed not relevant. -Udo.

3 11

how do I...
by Michael Scheibel 22 Nov '05

22 Nov '05

Good evening, I am currently playing around with L4Linux+DOpE and would like to 1. Start and kill L4 processes at runtime (fprov-l4 and run-l4 do not work). 2. Disable the DOpE mouse pointer in the L4Linux console window. 3. Resize the L4Linux console window without just stretching it. 3. Play Quake :) (where do I get it?) Any hints highly appreciated. Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel(a)sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.

4 12

Building Fiasco-UX
by Marko Wolf 21 Nov '05

21 Nov '05

Hi, since several weeks (including now) I can't compile the FIASCO UX target without patching the ../build/auto/std_macros.h file from your CVS. I think it has something to do with the inline definition since the following patch in std_macros.h solves it. #ifndef noinline #define noinline noinline #endif Unfortunately, I have to apply it for every new UX build. Is it a bug or I'm doing something wrong? Best regards Marko PS: The default kernel config (+UX, +UX_CON, +UX_NET) is attached. ----------------------------------------------------------------------------- - ... Making kernel_thread.o /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:104: error: Syntaxfehler before `)' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ISO C++ forbids declaration of `init_switch_time' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: declaration of `int Context::init_switch_time()' outside of class is not definition /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:117: error: ISO C++ forbids declaration of `init_workload' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:119: error: Syntaxfehler before `while' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ISO C++ forbids declaration of `puts' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ` int puts' redeclared as different kind of symbol /usr/include/stdio.h:589: error: previous declaration of `int puts(const char*) ' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: invalid conversion from `const char*' to `int' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:127: error: ISO C++ forbids declaration of `ready_dequeue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: ISO C++ forbids declaration of `sched' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp: In function `int sched()': /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: Syntaxfehler before `->' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:129: error: ISO C++ forbids declaration of `ready_enqueue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:131: error: ISO C++ forbids declaration of `kill_all' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: ISO C++ forbids declaration of `threading_system_active' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: conflicting types for `int Helping_lock::threading_system_active' auto/helping_lock.h:24: error: previous declaration as `bool Helping_lock::threading_system_active' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ISO C++ forbids declaration of `exit' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ` int exit' redeclared as different kind of symbol /usr/include/stdlib.h:640: error: previous declaration of `void exit(int)' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:136: error: Syntaxfehler before `}' token make[2]: *** [kernel_thread.o] Fehler 1 make[2]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make[1]: *** [all] Fehler 2 make[1]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make: *** [all] Fehler 2 -------------------------------------------------------

1 0

[Emscb] Building Fiasco-UX
by Marko Wolf 21 Nov '05

21 Nov '05

Hallo, schon seit längerem (einschließlich der aktuellen Version) von Fiasco bekommen ich und andere beim Kompilieren (w/ gcc 3.3.6) (nur) zum Fiasco-UX Target immer nachfolgende Fehlermeldung, welche vermutlich an einer fehlenden inline Definition liegt. Zumindest müssen wir das ..build/auto/std_macros.h bei jedem UX-Build immer wie folgt patchen: #ifndef noinline #define noinline noinline #endif Gibt es da eine bessere Lösung oder machen wir etwas falsch? Viele Grüße Marko PS: Default Kernel-Config (+UX, +UX_CON, +UX_NET) im Anhang. ------------------------------------------------------------------------------ ... Making kernel_thread.o /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:104: error: Syntaxfehler before `)' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ISO C++ forbids declaration of `init_switch_time' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: declaration of `int Context::init_switch_time()' outside of class is not definition /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:117: error: ISO C++ forbids declaration of `init_workload' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:119: error: Syntaxfehler before `while' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ISO C++ forbids declaration of `puts' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ` int puts' redeclared as different kind of symbol /usr/include/stdio.h:589: error: previous declaration of `int puts(const char*) ' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: invalid conversion from `const char*' to `int' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:127: error: ISO C++ forbids declaration of `ready_dequeue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: ISO C++ forbids declaration of `sched' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp: In function `int sched()': /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: Syntaxfehler before `->' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:129: error: ISO C++ forbids declaration of `ready_enqueue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:131: error: ISO C++ forbids declaration of `kill_all' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: ISO C++ forbids declaration of `threading_system_active' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: conflicting types for `int Helping_lock::threading_system_active' auto/helping_lock.h:24: error: previous declaration as `bool Helping_lock::threading_system_active' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ISO C++ forbids declaration of `exit' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ` int exit' redeclared as different kind of symbol /usr/include/stdlib.h:640: error: previous declaration of `void exit(int)' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:136: error: Syntaxfehler before `}' token make[2]: *** [kernel_thread.o] Fehler 1 make[2]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make[1]: *** [all] Fehler 2 make[1]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make: *** [all] Fehler 2 _______________________________________________ Emscb mailing list Emscb(a)lists.tc.internet-sicherheit.de http://lists.tc.internet-sicherheit.de/mailman/listinfo/emscb

2 1

which libc
by Christoph Mueller 09 Nov '05

09 Nov '05

Hello, I came across dietlibc and uClibc. What is the difference between them? Which one should I use? Thanks, Christoph

2 1

Re: L4Linux without Con or DoPe?
by Marcel Selhorst 06 Nov '05

06 Nov '05

Hi Frank, I tried a lot of things now, but I am not able to get L4Linux working with the VESA-fb and without l4fb through Con/Dope. If I boot Fiasco and L4Linux without l4fb and using vbeset, I see nothing. If I boot Fiasco and L4Linux without l4fb and not using vbeset, I see the log below. (grepped via serial console) If I compile in the VGA-console, l4linux runs smoothly, but I don't get the VESA-fb running... Attaching commandline options to the l4linux-kernel (e.g., vga=791 or video=vesa...) does actually do nothing. Any further ideas? Attached you'll find my .config-file. Thanks in advance and best regards, Marcel Selhorst *loader | vmlinuz26,#d: Starting at l4loader_init (000164d0) *exec | vmlinuz26: Linking *exec | vmlinuz26: Relocating entry 00400000 => 00400000 *exec | vmlinuz26: Packed 721705 bytes of symbols *exec | vmlinuz26: Packed 2050734 bytes of lines *loader | vmlinuz26,#d: Continue at l4env_init (000164e0, libloader.s.so) *l4lx | crt0_construction called. *l4lx | ======> L4Linux 2.6 starting... <======== *l4lx | Binary name: vmlinuz26 *l4lx | Kernel command line (9 args): mem=128M noreplacement root=1:0 load_ra *l4lx : mdisk=1 ramdisk_size=56000 l4env_rd=ramdisk.gz panicblink=0 lang=de v *l4lx : ga=791 *l4lx | My DMphys is at 06.00 *l4lx | My region mapper is at 0d.00 *l4lx | My code starts at 0x00400000 and ends at 0x00740188 [3328 KiB]. *l4lx | Semaphore thread ID: 0d.01 *l4lx | Areas: *l4lx | Text: 00400000 - 00649000 [2340kB] (a bit longer) *l4lx | Data: 00649000 - 006a3388 [360kB] *l4lx | Initdata: 006a6000 - 006d5000 [188kB] *l4lx | BSS: 006d5008 - 00740188 [428kB] *l4lx | l4lx_thread_create: Created thread 0d.03 (server) *l4lx | main thread will be 0d.03 *l4lx | l4env_register_pointer_section: addr = 00400000 size = 3407872 *l4lx | with-init: virt: 0x00400000 to 0x0073ffff [3328 KiB] *l4lx | Noncontinuous region for with-init *l4lx | Probably region overflow for with-init?! *l4lx | with-init: Number of physical regions: 6, 3407872 Bytes *l4lx | with-init: 1: Phys: 0x01415000 to 0x01497000, Size: 532480 *l4lx | with-init: 2: Phys: 0x01150000 to 0x01220000, Size: 851968 *l4lx | with-init: 3: Phys: 0x01355000 to 0x01400000, Size: 700416 *l4lx | with-init: 4: Phys: 0x01259000 to 0x01300000, Size: 684032 *l4lx | with-init: 5: Phys: 0x001ca000 to 0x00240000, Size: 483328 *l4lx | with-init: 6: Phys: 0x010da000 to 0x01100000, Size: 155648 *l4lx | l4env_linux_startup thread 3. *l4lx | main thread: received startup message. *l4lx | setup_l4env_memory: Forcing superpages for main memory *l4lx | Main memory size: 128MB *l4lx | Mainmem DS id: 68 *l4lx | mainmem: virt: 0x00800000 to 0x087fffff [131072 KiB] *l4lx | Main thread running, waiting... *l4lx | mainmem: Number of physical regions: 1, 134217728 Bytes *l4lx | mainmem: 1: Phys: 0x0a800000 to 0x12800000, Size: 134217728 *l4lx | Filling lower ptabs... *l4lx | Done (1047 entries). *l4lx | l4env_rd_path: ramdisk.gz *l4lx | Loading: ramdisk.gz *l4lx | INITRD: Size of RAMdisk is 55000KiB *l4lx | RAMdisk from 08800000 to 0bdb6000 [55000KiB] *l4lx | l4lx_thread_create: Created thread 0d.04 (timer.i0) *l4lx | l4lx_thread_create: Created thread 0d.05 (IRQ12) *l4lx | l4lx_thread_create: Created thread 0d.06 (IRQ15) *l4lx | l4lx_thread_create: Created thread 0d.07 (IRQ1) *l4lx | l4lx_thread_create: Created thread 0d.08 (IRQ11) Frank Mehnert schrieb: > On Friday 28 October 2005 10:45, you wrote: > >>Hi Frank, >> >> >>>Should be possible. Just enable the framebuffer but not l4fb. Where is >>>the problem? >> >>I tried that, but the linux console is just blank and the only output I get >>is from fiasco... > > > Please send me your .config file. > > Frank # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-l4 # Sat Nov 5 15:59:28 2005 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_L4DIR="/Daten/CVS/fiasco/l4" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 # CONFIG_L4_USERPRIV_ONLY is not set CONFIG_L4_EXTERNAL_RTC=y CONFIG_L4_L4ENV_MEMSIZE=32 # CONFIG_L4_TAMED is not set CONFIG_L4_MK_CPU_X86="586" # CONFIG_L4_IRQ_OMEGA0 is not set # # Stub drivers # CONFIG_L4_BLK_DRV=y # CONFIG_L4_FB_DRIVER is not set # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set # CONFIG_L4_SERIAL is not set # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Debuggin options # # CONFIG_L4_DEBUG is not set # # # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_HOTPLUG is not set CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODULE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=y # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_LBD is not set # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_CMD640 is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_SHARE_IRQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # CONFIG_SCSI=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # # CONFIG_BLK_DEV_SD is not set # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set # CONFIG_BLK_DEV_SR is not set # CONFIG_CHR_DEV_SG is not set # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set CONFIG_SCSI_SATA=y # CONFIG_SCSI_SATA_AHCI is not set # CONFIG_SCSI_SATA_SVW is not set CONFIG_SCSI_ATA_PIIX=y # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_PROMISE is not set # CONFIG_SCSI_SATA_QSTOR is not set # CONFIG_SCSI_SATA_SX4 is not set # CONFIG_SCSI_SATA_SIL is not set # CONFIG_SCSI_SATA_SIS is not set # CONFIG_SCSI_SATA_ULI is not set # CONFIG_SCSI_SATA_VIA is not set # CONFIG_SCSI_SATA_VITESSE is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_CPQFCTS is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_NCR53C406A is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS is not set # CONFIG_SCSI_QLOGIC_ISP is not set # CONFIG_SCSI_QLOGIC_FC is not set # CONFIG_SCSI_QLOGIC_1280 is not set CONFIG_SCSI_QLA2XXX=y # CONFIG_SCSI_QLA21XX is not set # CONFIG_SCSI_QLA22XX is not set # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set # CONFIG_SCSI_QLA24XX is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_SEAGATE is not set # CONFIG_SCSI_SYM53C416 is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_ULTRASTOR is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_DM=y CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_SPI is not set # CONFIG_FUSION_FC is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set # CONFIG_EL16 is not set CONFIG_EL3=y # CONFIG_3C515 is not set # CONFIG_VORTEX is not set # CONFIG_TYPHOON is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y # CONFIG_DE2104X is not set CONFIG_TULIP=y # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y CONFIG_PCNET32=y # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set # CONFIG_CS89x0 is not set # CONFIG_DGRS is not set CONFIG_EEPRO100=y # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y CONFIG_8139CP=y CONFIG_8139TOO=y CONFIG_8139TOO_PIO=y # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000_NAPI is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SKGE is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set CONFIG_BNX2=y # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set CONFIG_SERIO_PCIPS2=y CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=y # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # # I2C support # # CONFIG_I2C is not set # CONFIG_I2C_SENSOR is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=y # CONFIG_HWMON_DEBUG_CHIP is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set CONFIG_FB_MODE_HELPERS=y # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # SN Devices # # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set CONFIG_NFS_V4=y # CONFIG_NFS_DIRECTIO is not set # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_RPCSEC_GSS_KRB5=y # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set CONFIG_FRAME_POINTER=y # CONFIG_EARLY_PRINTK is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y

2 1

Unofficial and experimental release of Kaffe on DROPS/L4
by Alexander Boettcher 06 Nov '05

06 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, at [1] you can find a snapshot of a packet, which contains the latest working Kaffe version (without RTSJ experimental extensions) running on top of DROPS. I'm in contact with Dalibor and Jim in order to merge the DROPS/L4 port in the current cvs version of kaffe.org. However, I already got a request for Kaffe on DROPS, therefore I provide it this way for interested people until it is available from kaffe.org. The packet contains a complete snapshot of the sources of kaffe.org (October this year) and not only the port specific files, because the latest cvs version of kaffe.org doesn't build with the DROPS/L4 port :-(. Please note, the state of the port must be considered as experimental. My port specific code are licensed under GPL and I provide it with no warranty. A README is available at [2]. Best regards, Alexander Boettcher. [1] http://wwwos.inf.tu-dresden.de/~ab764283/kaffe.tar.bz2 - 8,4 MB [2] http://wwwos.inf.tu-dresden.de/~ab764283/README.drops [3] http://wwwos.inf.tu-dresden.de/~ab764283/kaffe.tar.bz2.sig -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDbfuEqjRK9KYzJbMRAu8uAJsEaafL9wEM5SWiXzxGShpNt1yjTACgm8nh Bdq8HK/t5MrU8jLsjN19PTM= =y9fd -----END PGP SIGNATURE-----

1 0

l4linux26 @ fiasco-ux w/ dietlibc
by Marko Wolf 02 Nov '05

02 Nov '05

Hi! I tried running l4linux26 on fiasco-ux compiled from the actual CVS with the dietlibc using the following script: fiasco -t 32768 \ -G800x600@16 \ -m 512 \ -R roottask \ -l names \ -l log \ -l dm_phys \ -l simple_ts -t 380 \ -l fuxfprov -n9 \ -l rtc-ux -n10 \ -l l4exec \ -l l4dope-ux \ -l "loader run l4linux26.cfg" Unfortunatly, l4linux causes a null pointer exceptions (see attached log). I tried various kernel compiler options with always the same error. Any idea for the reason or what I can try else? Thanks a lot Marko PS: By the way, Im using gcc 3.3.6

3 12

fiasco for ARM
by Shakthi Kannan 31 Oct '05

31 Oct '05

Greetings! Couple of questions: 1. Will we be getting an announcement in the mailing list when fiasco moves with uclibc and dietlibc without oskit support? 2. What is the current status of fiasco for ARM (cores 9 and above)? The FAQ mentions only about x86 with i486 and above, but, I found some ARM relevant code in l4sys/include-x2/L4API-l4x2/l4/arm. Is there anyone working with fiasco for ARM? Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

4 4

L4Linux without Con or DoPe?
by Marcel Selhorst 28 Oct '05

28 Oct '05

Hi Hackers, is there a way to use L4Linux without Con or Dope? In detail, I want to boot L4Linux and give a Linux-framebuffer (not the l4fb!) the control of the videocard, so that the console has direct hw-access. Best regards, Marcel Selhorst

2 2

bootstrap + module
by Christoph Mueller 27 Oct '05

27 Oct '05

Hello, I am reusing some code from dde_linux/examples/sound. But I use bootstrap instead of rmgr. Where do I find correct syntax for menu.lst to specify an additional module (sample.pcm) for my server? The syntax from dde_linux/examples/sound/menu.lst uses RMGR. I think, I have to give a parameter to bootstrap that I can access the additional module in my server. syntax from example: >title sounddrv-foo > kernel (nd)/tftpboot/USER/rmgr -sigma0 task modname "sounddrv-foo" module > module (nd)/tftpboot/USER/fiasco -nowait -nokdb >... what i tried: >title l4snd - l4env >kernel $(P)/bootstrap -sigma0 task modname "l4snd" module >modaddr 0x01500000 >module $(P)/fiasco $(FIASCOARGS) >module $(P)/sigma0 >module $(P)/roottask >module $(P)/names -verbose 2 >module $(P)/log >module $(P)/dm_phys >module $(P)/l4io --noirq >module $(P)/l4snd >modaddr 0x01000000 >module $(P)/snd.pcm sample1 l4env_multiboot_info->mods_count is zero. (I assume no module was assigned to my server.) Thanks, Christoph

3 2

Re: Capability Authentication
by Marcus Völp 21 Oct '05

21 Oct '05

Hi, this is a reply to an email I found in the l4-hurd mail archive [http://lists.gnu.org/archive/html/l4-hurd/2005-10/msg00020.html] I'm not on the list, sorry. On Fri, 2005-10-07 at 23:01 -0400, Jonathan S. Shapiro wrote: >/ > > And, do we need the second one / >/ > > to be provided by idl4? I say, usually the server will not trust its / >/ > > client and this it's useless, as the server will not use the new handle./ >/ / >/ You are making an incorrect assumption. In general, what you say is/ >/ true, but if the server can authenticate the validity of a capability,/ >/ there is no reason not to use it./ ... The more general solution comes from something we call a "constructor". A "foo constructor" is a server that knows how to create new copies of the "foo" program. Every constructor inserts a unique, unforgeable, and undisclosable capability into the process structure of the process that it creates. This capability is called the "brand". Each constructor uses a different brand from all other constructors. In EROS, there is a kernel capability that performs (approximately) the following operation: interface ProcessTool extends key { bool identify(entry_cap_t someProc, cap_t brand); } Given an entry capability to a process and a second capability, the kernel checks whether the second capability is equal to the existing brand in the process. If so, it returns true, else it returns false. By construction, only constructors hold ProcessTool capabilities. However, if you hold a capability to a foo constructor, and you also hold an entry capability, you can turn to the foo constructor and ask "is this an entry capability to some process that you created?" That is: is it an entry capability to an authentic instance of "foo"? This authentication pattern is enormously important for many of the security arrangements that we are able to achieve in EROS. One of my largest concerns about L4sec is that the L4sec team does not (yet) see that this operation is important. Without an operation like this, it is impossible (or at least, we do not see how) to build robust third-party trust contracts. Jonathan, yes so far L4.Sec does not support such an operation. We thought about (I think Bernard Kauer and Marcus Brinkmann already had a discussion on this topic on l4-hackers) adding a compare operation on endpoints which allows you to match identity of two endpoint capability (compare permissions provided). So far we are not sure whether such an operation is really needed or whether you want to construct systems the way you do. The fundamental issue is that a potentially trusted capability is handed to a server by a not completely trusted source (the client C). We thought briefly about two general solutions to this problem: 1) obtain a version of this capability from a trusted source, or, 2) prepare and defend against potential misbehavior of the invoked server. ad 1: This solution assumes a network of trusted "name"-servers and protocols that require the client C in order to share a capability with some other process S that it establishes this sharing with the target of the capability (D). C can do so by giving its name to S to D and asking D to share the rights S can then request a capability to D from its trusted nameservers and ask for the shared capability provided it trusts D. Please keep in mind that we did not build such a system yet and that it is only a preliminary and potentially not working solution. ad 2: Alternatively the server can prepare to defend against misbehavior of D. In L4.Sec the receiver of an IPC controls the location where an incoming message is placed. Thus it can select an area of its address space so that even if D replies with bogus content, S is not harmed. It remains, however, the problem of blocking S. An easy way to defend against blocking attacks is to fork of a thread for this particular client's request and let it invoke the pot. untrusted capability on behalf of the client. Other thread invoking the same server are not affected by this blocking. Again please keep in mind that both are preliminary solutions. We have still to construct a system on top of L4.Sec. Also please note that L4.Sec is not a fixed API but has experimental status and that we welcome both suggestions for improvement and requirements. However, you will find that features will be added only if they cannot be implemented on top of L4.Sec with a reasonable effort. This is one of the fundamental rules which in my opinion contributed to the success of L4. So please apologize my stubbornness in this point. Compare might be such a feature which will get added if we find no way to achieve what Jonathan listed in his mail. Best regards Marcus Völp -- Marcus Völp TU-Dresden Department of Computer Science Institute for System Architecture Tel: +49 (351) 463-38350 Fax: +49 (351) 463-38284

4 7

Module arguments
by Marcel Selhorst 20 Oct '05

20 Oct '05

Hello L4-Hackers, I have a problem regarding the loading of modules: If I want to load a module and put the regarding entry into the menu.lst including parameters for the module, the module cannot be found in the memory. For example, I have the entry: module (nd)/hddencrypter --with-password-dialog or module (nd)/ramdisk --with-password-dialog (the --with-password-dialog is an argument, which forces GRUB to prompt for a password and afterwards replaces the --with-password-dialog with a new parameter --password='xxx'. This is needed for the harddisc encrypter in order to get the password for decrypting the configuration file). But whenever I put a parameter behind a module, the loader isn't able to locate the entry inside the memory (probably because it compares the whole string?). l4lx | l4env_rd_path: ramdisk l4lx | Loading: ramdisk bmodfs | [B.2] generic_fprov/examples/bmodfs/dm.c:135:dm_open(): bmodfs | Error: Object 'ramdisk' not found! l4lx | Couldn't load RAM disk from fprov! Are there any ideas on how to solve this? Best regards, Marcel Selhorst

2 7

L4.Sec Preliminary Microkernel Reference Manual
by Bernhard Kauer 19 Oct '05

19 Oct '05

The operating system's group at Technische Universit?t Dresden is pleased to announce the first draft of the L4.Sec Preliminary Microkernel Reference Manual. The document can be found at http://os.inf.tu-dresden.de/L4/L4.Sec/ L4.Sec is a specification of a next generation microkernel interface targeted to co-host user-level servers implementing security-critical functionality next to untrusted and potentially malicious software. Bernhard Kauer

1 0

RE: Sawmill's dataspaces and the Hurd's physmem
by yuan Darwin-r62832 19 Oct '05

19 Oct '05

Hi Neal, Thanks for your detailed information. > Physical memory management needn't be an all or nothing deal. Certainly, an application might wish to completely > manage the paging policy and its address space layout, however, I tend to think that this is the exception. And as > we will provide a POSIX personality, we need to have some sort of default VM manager. About general VM manager, what I really mean is just the "default VM manager". However, the question is still there: now that those sort of default VM managers provide mmap to those applications who don't want to manage their phsical memory, should they trust these VM managers? If yes, these applications who use the Sawmill's framework should also trust DSMs, now that DSMs provide mapping to them, and DSMs will manage their own physical memory(implement their own replacement policy, they can even just use the library(LRU) provided by Hurd). So, we can divide the applications into 2 categories: some of them wanna manage their physical memory, others won't. For the applications who do intend to do that, they just apply memory directly from Hurd's physmem server which is trustworthy; For others, they can just use the Sawmill's framework. Note that these DSMs also apply memory from Hurd's physmem, instead of Sawmill physmem DSM. So we can just think these DSMs are just the applications who intend to manager their own physical memory. My conclusion is, if Sawmill's framework has security problem on trust model, so has Hurd. So we have to assume that an application must trust its pager ( or pagers in Sawmill's model). Base on this assumption, Hurd & Sawmill's approach can live together. > I see a number of problems with SawMill's dataspaces. The root of this thread is the presentation of a potential security flaw > in the design of dataspaces. (Whether this is important or not depends on the assumed trust model and security goals.) > Another is that as far as I can tell paging decisions are made towards the root of a dataspace hierarchy and not at the applications themselves. As I said above, for those applications who don't want to manage their own physical memory, they don't need to make paging decision. For others, they just apply memory from Hurd's physmem server, and manage the memory by themselves, which means they can make the paging decision by themselves. Correct me if I have any misunderstanding. Thanks. Darwin

2 1

RE: Sawmill's dataspaces and the Hurd's physmem
by yuan Darwin-r62832 19 Oct '05

19 Oct '05

Hi Neal, By reading the document of Hurd(VMM), I guess I had a misunderstanding about Hurd's approach. Sorry for bothering. Best Regards, Darwin -----Original Message----- From: Neal H. Walfield [mailto:neal@walfield.org] Sent: Tuesday, October 18, 2005 9:40 PM To: yuan Darwin-r62832 Cc: l4-hackers(a)os.inf.tu-dresden.de; l4-hurd(a)gnu.org Subject: Re: Sawmill's dataspaces and the Hurd's physmem At Tue, 18 Oct 2005 19:42:27 +0800, yuan Darwin-r62832 wrote: > I think these 2 approachs are not incompatible. Here are the reasons, > > 1. In Hurd's approach, every application could manage its own > physical memory. However, for most of application developers, they > don't want to take care of the VM replacement policy. To solve this > problem, Hurd has to provide a general VM server to be the pager of > this kind of applications. However, as the philosophy of Hurd, should > this applications trust this server? Physical memory management needn't be an all or nothing deal. Certainly, an application might wish to completely manage the paging policy and its address space layout, however, I tend to think that this is the exception. And as we will provide a POSIX personality, we need to have some sort of default VM manager. The solution that I've opted for is a library based one: a default memory management library will, for instance, implement an LRU based eviction scheme and require no application input. For many applications this will be appropriate and sufficient. Those applications wishing to take complete control will also be able to completely replace the library. I think that some applications can provide useful hints in relatively concise ways. A document viewer, for instance xpdf, might want to cache previously rendered pages. It does not make sense to send these to swap if rereading the data and rerendering is cheaper. In this case, the application can attach a function to drain the cache to a library provided hook which is called when there is memory pressure. I think that this small type of change may offer dramatic results. Moreover, if the change is highly isolated (which in this case seems feasible), it will be easily accepted upstream. An even less invasive hint would be to set some environment variables. Clearly we wouldn't expect most users to set these but an application's packager could based on observed behavior. In the case of e.g. grep or cat we might want to set the read ahead parameter to "very aggressive". If a developper so desires, a more aggressive, but more invasive approach, can also be adopted. Instead of using malloc and free, the application can use a slab allocator. I think this can only be effectively done if the slab allocator participates in the eviction scheme. Again, this is possible in our case with a number of library provided hooks but not for user applications running on a traditional Unix-like core. This can be made backwards compatible by having the configure script check for the required mechanisms and if they are not available then to redefine slab_alloc and slab_free to malloc and free. > 2. In Sawmill's DS approach, every task(AS) has a specific thread > named "region mapper" to be the pager of other threads. It captures > the page fault, then decide to forward it to corresponding server, and > get mapped. So from the higher level point of view, these servers are > the pagers of the task. If Hurd application should trust that general > VM pager, the applications using Sawmill's DS framework should trust > these servers as well. I hope it is now clear that there is no general VM server. > 3. Relative to Sawmill's approach, Hurd provides a clear & great > physical memory server, which makes the whole physical memory of > platform could be fairly used by all of the servers & applications. > > Therefore, we can use Hurd's physmem server as the central > controller. Sawmill's DSMs apply physical memory from it. The > applications who wanna use Sawmill's approach could still walk on > their own way. For some applications who wanna manage their own > physical memory, they can apply memory from physmem server directly. I see a number of problems with SawMill's dataspaces. The root of this thread is the presentation of a potential security flaw in the design of dataspaces. (Whether this is important or not depends on the assumed trust model and security goals.) Another is that as far as I can tell paging decisions are made towards the root of a dataspace hierarchy and not at the applications themselves. Hopefully it is clear why I've choosen to reject this scheme. Thanks, Neal

1 0

RE: Sawmill's dataspaces and the Hurd's physmem
by yuan Darwin-r62832 18 Oct '05

18 Oct '05

Hi Neal, I think these 2 approachs are not incompatible. Here are the reasons, 1. In Hurd's approach, every application could manage its own physical memory. However, for most of application developers, they don't want to take care of the VM replacement policy. To solve this problem, Hurd has to provide a general VM server to be the pager of this kind of applications. However, as the philosophy of Hurd, should this applications trust this server? 2. In Sawmill's DS approach, every task(AS) has a specific thread named "region mapper" to be the pager of other threads. It captures the page fault, then decide to forward it to corresponding server, and get mapped. So from the higher level point of view, these servers are the pagers of the task. If Hurd application should trust that general VM pager, the applications using Sawmill's DS framework should trust these servers as well. 3. Relative to Sawmill's approach, Hurd provides a clear & great physical memory server, which makes the whole physical memory of platform could be fairly used by all of the servers & applications. Therefore, we can use Hurd's physmem server as the central controller. Sawmill's DSMs apply physical memory from it. The applications who wanna use Sawmill's approach could still walk on their own way. For some applications who wanna manage their own physical memory, they can apply memory from physmem server directly. [ physmem ] / \ |_ _| [ DSM ] [Hurd app] (manage physmem by itself] / \ |_ _| [Sawmill app] [Sawmill app] Best Regards, Darwin

2 1

Re: Re: Building device drivers with oskit10_support_l4env
by Christian Helmuth 16 Oct '05

16 Oct '05

Hello, On Thu, Oct 13, 2005 at 08:03:38PM +0800, Jianjun Shen wrote: > I think my solution can not help you - I has not > investigated omega0, but just suspected oskit dose not > correctly request service from omega0. In fact, I am > far from a certain answer, and still can not make my > program always play properly. The scis drivers still > do not work, so I just removed scsi support. Too bad. > Some questions: > 1) I know there is a ore stub in l4lx26, then, is > there a one for flips in lx26? Yes, there is a device driver stub for ore in L4Linux-2.6. For flips, there's no such module as Linux does not support more than 1 TCP/IP instance below its socket layer - remember flips is a fully functional network stack implementation providing a BSD socket API. (You're right if think one could implement a virtual device in L4Linux-2.6 and FLIPS that communicate.) If you're looking for an ore device driver stub for flips, I must put you off until a volunteer appears who wants to implement it / port it from L4Linux-2.6 to Linux2.4-based flips. Maybe you're prepared to do the job? ;) > 2) How you have considered a NIC can be shared by > multiple l4lx instance? One IP per instance, or NAT? Please, do not mistake the network interface layers for the "network layer" (that is IP in TCP/IP). If your L4Linux instances are to share one physical device on device layer, ore is what you want. It switches the NIC into promiscuous mode effectively listening to all traffic on the wire. (Yes, there are performance concerns.) Then ore serves network packets on the basis of MAC addresses to clients. If you want network address translation (NAT), you need router software as NAT works on the "network layer". With some effort you may use FLIPS with virtual device(s) or a special L4Linux instance for that purpose. But in this case, you may also need a virtual (wire) switch. > 3) I found a "l4vfs" in your CVS. What is it? Hence the name, l4vfs implements a kind of virtual file system switch, but I'm far from the right person to give voluminous information. Maybe somebody else could step in here? > 4) I am also interested in IPSec, and I noticed there > is a paper: "IPSec-Infrastruktur für Mikro-SINA" (in > German) - is it about an IPSec implementation? Yes, it is, actually about the IKE part of IPSec. You may also have a look at: http://os.inf.tu-dresden.de/papers_ps/dach2005.pdf > Actually, I am trying to develop a secure system based > on l4, in which all "subject"s share some basic > servers, but can only communicate with separate > untrusted servers (e.g. linux) based on their security > classes. Sounds interesting. Is it a term paper or thesis or something else? > Currently, my project is just at initial stage. So I > may often bother all of you in some days. Thanks > first. > > Best regards! > Jianjun Shen Regards -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

3 2

Re: Using l4ide, l4linux and con together (solved)
by Jianjun Shen 15 Oct '05

15 Oct '05

Hi, Sorry for my last mail. I already got the answer - using both --l4io and --omega0. I also found with the latest CVS version, "con" was unable to load "run". Is it just my individual mistake? Best regards! Jianjun Shen --- Jianjun Shen <weishen_cu(a)yahoo.com.cn>: > Hi, > > Thanks for all of your previous help. But I meet > another problem. ;( > > I tried to use l4linux with l4ide which needs > omega0. > Then, I found "con" would fail to load l4linux if > omega0 was running. How can this problem be solved? > > Best regards! > Jianjun Shen > ___________________________________________________________ 雅虎免费G邮箱－中国第一绝无垃圾邮件骚扰超大邮箱 http://cn.mail.yahoo.com

2 1

Using l4ide, l4linux and con together
by Jianjun Shen 14 Oct '05

14 Oct '05

Hi, Thanks for all of your previous help. But I meet another problem. ;( I tried to use l4linux with l4ide which needs omega0. Then, I found "con" would fail to load l4linux if omega0 was running. How can this problem be solved? Best regards! Jianjun Shen ___________________________________________________________ 雅虎邮箱超强增值服务－2G超大空间、pop3收信、无限量邮件提醒 http://cn.mail.yahoo.com

1 0

Dope Crash during large fb output
by Marcel Selhorst 14 Oct '05

14 Oct '05

Hi Hackers, yesterday I was running Dope with L4Linux. Inside the L4Linux-framebuffer I was compiling some applications, which produce lots of output in a very short time. Well, exactly at that point DoPe crashed. Connecting via my serial port to the kdb I got "Dope exited with -1" or something like that. I will try to reproduce that error or is this known already? Best regards, Marcel Selhorst

2 2