- l4-hackers - OS Site

Re: hda : lost interrupt
by Burak OGUZ 29 Mar '07

29 Mar '07

How can I reach to the logs of serial output and grub? Does it writes them anywhere on the disk? -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Wednesday, March 28, 2007 8:49:09 PM Subject: Re: hda : lost interrupt On Wed Mar 28, 2007 at 08:01:09 -0700, Burak OGUZ wrote: > I have successfully booted the L4 and saw the dope. However, while > L4Linux is booting up it gives "hda : lost interrupt" for my hard disk > and "hdc : lost interrupt" for my cd-rom. I have applied whatever says > in the l4-kickstart manual except l4exec because I have read that it > is deprecated. > > Also same problem has occured when I have booted up with live CD. 'lost interrupt' indicates that there's some problem with the interrupt handling on your system. Can you maybe show us the log output that comes on the serial console and your menu.lst? You may also use e.g. qemu and compare the serial output of both systems to see if there's some significant difference which might indicate a problem. For testing purposes you may also comment out the vbeset command in the menu.lst as well as the line that loads dope. With this change you'll see the debug output directly on the screen. Look for messages that might indicate an error. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front

2 1

Re: hda : lost interrupt
by Burak OGUZ 28 Mar '07

28 Mar '07

Hi all, I have successfully booted the L4 and saw the dope. However, while L4Linux is booting up it gives "hda : lost interrupt" for my hard disk and "hdc : lost interrupt" for my cd-rom. I have applied whatever says in the l4-kickstart manual except l4exec because I have read that it is deprecated. Also same problem has occured when I have booted up with live CD. Thanks in advance. -- burak() (ps: bf) METU CENG '06 ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/

2 1

hda : lost interrupt
by Burak OGUZ 28 Mar '07

28 Mar '07

Hi all, I have successfully booted the L4 and saw the dope. However, while L4Linux is booting up it gives "hda : lost interrupt" for my hard disk and "hdc : lost interrupt" for my cd-rom. I have applied whatever says in the l4-kickstart manual except l4exec because I have read that it is deprecated. Thanks in advance. -- burak() (ps: bf) METU CENG '06 ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php

1 0

getting started with L4Linux and DDE
by Igor Shmukler 27 Mar '07

27 Mar '07

Hello, First, I would like to thank everyone for their assistance me with getting up and running. I built a cross sandbox under Ubuntu 6.10 - not a major achievement :) If anyone wants the VMWare image, please let me know. It's 4GB in size, so please prepare enough space for upload. Now, I have been looking through sources. So far these seem quite clear. I even started hacking together something of my own. I do however have questions about using the system. The make installs everything (besides bootstrap and perhaps another tool or two) into the /home/drops/bin/... There is no GRUB menu.lst in that specific directory, but there are a few samples along with various modules. So far everything is very clear and logical. What puzzles me. The DDE (sound) sample needs a missing file - fiasco. However, I only have fiasco_top in my bin. Am I missing it because I need to build (or install) it manually? There is a file in l4/kernel/fiasco/build/fiasco (symlink to the main). That file is an ELF binary. Seems like a logical candidate. :) Are these files not copied by make install because kernels are interchangeable and I could swap one for another? Is there a quick way to test that everything works? Is the TUD GRUB's only difference support for JDB, or are there are features? Do I have to use TUD GRUB to boot, or only when I need debugging? I am assuming the answer to the next question has to be "YES," however I would like to know for sure. Is TUD GRUB 100% compatible with a regular GRUB? If not, am I likely to need the old GRUB for booting regular Linux? Sorry for spamming the list. I could not find good documentation covering this topic. Thank you in advance, igor

2 1

X Windowing System Under Dope
by SwiftBoo 26 Mar '07

26 Mar '07

Is there a "how-to" on configuring the X Windowing System for running under dope? If not, I'd be happy to write one up afterwards, if someone could help me through the process... I am interested in running the X Windowing System from within L4Linux on my existing DROPS workstation (currently using my existing distribution -- Debian Sarge) on native hardware. With Adam's previous help, I have managed to get everything else (fiasco, dope, l4linux with networking) up and running perfectly fine. Thanks! I see from the Nitpicker demo on the Demo CD, that xorg.conf is configured to run the OvlScreen device driver, and xinitrc runs an ovltrack process, however i didn't see these binaries get built as part of the usual drops build process. I did find an ovlscreen.c in the examples directory... is there a separate build process for generating the binaries to use under l4linux? How can I build ovlscreen and ovltrack for my system? Is Nitpicker required or is it optional? I noticed there is now an l4ovlwm, in addition to the nitovlwm binary referenced by the demo cd -- however, i don't see a nitdope binary that the demo cd references. Has this been integrated directly into l4dope, or perhaps no longer supported? Am I missing other pieces as well? Thanks in advance for any help you might offer! -Mike

3 2

Re: How can i know the meaning of options when I configure the Fiasco kernel
by Adam Lackorzynski 24 Mar '07

24 Mar '07

On Sat Mar 24, 2007 at 07:39:07 +0000, chenggh wrote: > > Most configuration options in the kernel configurator have a help text > > which is displayed when pressing '?'. How does it not work for you? > If I press '?' it displays this sentence "Search symbols for regular > expression: " not a help text. This dialog is displayed when pressing '/'. You might also want to press shift to get '?'. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: How can i know the meaning of options when I configure the Fiasco kernel
by chenggh 24 Mar '07

24 Mar '07

> Most configuration options in the kernel configurator have a help text > which is displayed when pressing '?'. How does it not work for you? If I press '?' it displays this sentence "Search symbols for regular expression: " not a help text. Thank you. cheng

1 0

How can i know the meaning of options when I configure the Fiasco kernel
by chenggh 23 Mar '07

23 Mar '07

Hi: Now I could boot the fiasco, l4linux and l4dope. In other words I could start to use drops system. But I want to know deep about the system especially the meanings of configuration options. In the menuconfig of fiasco kernel the help command says I could input the symbol of "?" to get the description of options. But it seems that it can't work well. Thank you. cheng

1 0

Re: How can i know the meaning of options when I configure the Fiasco kernel
by Adam Lackorzynski 23 Mar '07

23 Mar '07

On Fri Mar 23, 2007 at 13:20:13 +0000, chenggh wrote: > Hi: > Now I could boot the fiasco, l4linux and l4dope. In other words I could start > to use drops system. But I want to know deep about the system especially the > meanings of configuration options. > In the menuconfig of fiasco kernel the help command says I could input the > symbol of "?" to get the description of options. But it seems that it can't > work well. Most configuration options in the kernel configurator have a help text which is displayed when pressing '?'. How does it not work for you? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

L4Linux 2.6.19, L4Dope, and L4io and IRQs
by SwiftBoo 19 Mar '07

19 Mar '07

I am able to boot L4Dope successfully with mouse and keyboard working fine. When I try to subsequently load L4Linux, however, it seems to attach to the mouse and keyboard, after which, the mouse disappears and neither mouse and keyboard work at all. L4Linux does boot all the way to login prompt. I have tried various combinations of l4io with and without --noirq and L4Linux configured (and not) to use L4IO for interrupt handling. I thought i had disabled mouse and keyboard properly in L4Linux, however, there must be a setting I am missing. Pasted below are the boot menu.lst and l4linux .config files. Any help in spotting my erroneous l4linux setting(s) would be appreciated. /boot/grub/menu.lst : title X-Verse: Linux Console Mode root (hd0,0) kernel /l4/v2/bootstrap modaddr 0x06000000 module /l4/v2/fiasco -noserial -nowait -nokdb module /l4/v2/sigma0 module /l4/v2/roottask task modname "bmodfs" attached 4 modules module /l4/v2/events module /l4/v2/names --events module /l4/v2/log --events module /l4/v2/dm_phys --isa=0x00800000 -v --events module /l4/v2/simple_ts -t 300 --events module /l4/v2/rtc --events module /l4/v2/l4io --events module /l4/v2/l4dope --l4io -f module /l4/v2/loader --fprov=BMODFS l4linux26.cfg module /l4/v2/bmodfs module /l4/v2/libloader.s.so module /l4/v2/libld-l4.s.so module /l4/v2/vmlinuz26 module /l4/v2/l4linux26.cfg vbeset 0x117 I have also used the above with the following modification: module /l4/v2/l4io --noirq --events L4Linux Config: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.19-l4 # Sun Mar 18 12:22:10 2007 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_OBJ_TREE="/home/memswiler/dev/drops/bld" 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_L4ENV_MEMSIZE=32 CONFIG_L4_TAMED=y # # L4 build options # CONFIG_L4_MK_CPU_X86="586" # # IRQ Handling # # CONFIG_L4_IRQ_SINGLE is not set CONFIG_L4_IRQ_OMEGA0=y # CONFIG_L4_IRQ_MULTI is not set # # Stub drivers # CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # 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 # # Debugging options # CONFIG_L4_DEBUG=y # CONFIG_L4_DEBUG_REGISTER_NAMES is not set # CONFIG_L4_DEBUG_SEGFAULTS is not set # CONFIG_L4_DEBUG_STATS is not set # CONFIG_L4_DEBUG_IRQ_WHEELS is not set # CONFIG_L4_DEBUG_TAMED_COUNT_INTERRUPT_DISABLE is not set # # Monitoring options (ferret) # # CONFIG_L4_FERRET_USER is not set # CONFIG_L4_FERRET_KERNEL is not set # CONFIG_L4_FERRET_SYSCALL_COUNTER is not set # # # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set # CONFIG_POSIX_MQUEUE is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y # CONFIG_UTS_NS is not set CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_IKCONFIG=m CONFIG_IKCONFIG_PROC=y # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y # CONFIG_TASK_XACCT is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # # CONFIG_SMP is not set 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=y # CONFIG_M586TSC is not set # 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_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_GENERIC=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 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_CMPXCHG64=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_INTEL_USERCOPY=y # CONFIG_HPET_TIMER 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_MCE is not set CONFIG_VM86=y # 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_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_POPULATES_NODE_MAP=y 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_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_REGPARM is not set # CONFIG_SECCOMP is not set # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set CONFIG_COMPAT_VDSO=y # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_PM_LEGACY=y # CONFIG_PM_DEBUG is not set # CONFIG_PM_SYSFS_DEPRECATED is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # # # APM (Advanced Power Management) BIOS Support # # CONFIG_APM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # # CONFIG_PCI is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # CONFIG_PCCARD=m # CONFIG_PCMCIA_DEBUG is not set CONFIG_PCMCIA=m CONFIG_PCMCIA_LOAD_CIS=y CONFIG_PCMCIA_IOCTL=y # # PC-card bridges # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_MISC=m # # Networking # CONFIG_NET=y # # Networking options # CONFIG_NETDEBUG=y CONFIG_PACKET=m # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y CONFIG_XFRM=y # CONFIG_XFRM_USER is not set # CONFIG_XFRM_SUB_POLICY is not set CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y # CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_MULTIPLE_TABLES is not set # CONFIG_IP_ROUTE_MULTIPATH is not set # CONFIG_IP_ROUTE_VERBOSE is not set 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=y # CONFIG_NET_IPGRE is not set CONFIG_IP_MROUTE=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y # 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_XFRM_TUNNEL is not set CONFIG_INET_TUNNEL=y CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=y CONFIG_INET_XFRM_MODE_BEET=y CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m # CONFIG_TCP_CONG_HYBLA is not set # CONFIG_TCP_CONG_VEGAS is not set # CONFIG_TCP_CONG_SCALABLE is not set # CONFIG_TCP_CONG_LP is not set # CONFIG_TCP_CONG_VENO is not set # CONFIG_DEFAULT_BIC is not set CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_HTCP is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_WESTWOOD is not set # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" # # IP: Virtual Server Configuration # # CONFIG_IP_VS is not set CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_INET6_AH is not set # CONFIG_INET6_ESP is not set # CONFIG_INET6_IPCOMP is not set CONFIG_IPV6_MIP6=y # CONFIG_INET6_XFRM_TUNNEL is not set # CONFIG_INET6_TUNNEL is not set CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m # CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set CONFIG_IPV6_SIT=m # CONFIG_IPV6_TUNNEL is not set # CONFIG_IPV6_MULTIPLE_TABLES is not set # CONFIG_NETLABEL is not set # CONFIG_NETWORK_SECMARK is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=y # CONFIG_NETFILTER_NETLINK_QUEUE is not set # CONFIG_NETFILTER_NETLINK_LOG is not set # CONFIG_NF_CONNTRACK is not set CONFIG_NETFILTER_XTABLES=m # CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set # CONFIG_NETFILTER_XT_TARGET_MARK is not set # CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set # CONFIG_NETFILTER_XT_MATCH_COMMENT is not set # CONFIG_NETFILTER_XT_MATCH_DCCP is not set # CONFIG_NETFILTER_XT_MATCH_DSCP is not set # CONFIG_NETFILTER_XT_MATCH_ESP is not set # CONFIG_NETFILTER_XT_MATCH_LENGTH is not set # CONFIG_NETFILTER_XT_MATCH_LIMIT is not set # CONFIG_NETFILTER_XT_MATCH_MAC is not set # CONFIG_NETFILTER_XT_MATCH_MARK is not set # CONFIG_NETFILTER_XT_MATCH_POLICY is not set # CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set # CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set # CONFIG_NETFILTER_XT_MATCH_QUOTA is not set # CONFIG_NETFILTER_XT_MATCH_REALM is not set # CONFIG_NETFILTER_XT_MATCH_SCTP is not set # CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set # CONFIG_NETFILTER_XT_MATCH_STRING is not set # CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set # # IP: Netfilter Configuration # # CONFIG_IP_NF_CONNTRACK is not set # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=m # CONFIG_IP_NF_MATCH_IPRANGE is not set # CONFIG_IP_NF_MATCH_TOS is not set # CONFIG_IP_NF_MATCH_RECENT is not set # CONFIG_IP_NF_MATCH_ECN is not set # CONFIG_IP_NF_MATCH_AH is not set # CONFIG_IP_NF_MATCH_TTL is not set # CONFIG_IP_NF_MATCH_OWNER is not set # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_HASHLIMIT is not set # CONFIG_IP_NF_FILTER is not set # CONFIG_IP_NF_TARGET_LOG is not set # CONFIG_IP_NF_TARGET_ULOG is not set # CONFIG_IP_NF_TARGET_TCPMSS is not set # CONFIG_IP_NF_MANGLE is not set # CONFIG_IP_NF_RAW is not set # CONFIG_IP_NF_ARPTABLES is not set # # IPv6: Netfilter Configuration (EXPERIMENTAL) # # CONFIG_IP6_NF_QUEUE is not set # CONFIG_IP6_NF_IPTABLES is not set # # DCCP Configuration (EXPERIMENTAL) # # CONFIG_IP_DCCP is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # # TIPC Configuration (EXPERIMENTAL) # # CONFIG_TIPC 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_LLC=m # CONFIG_LLC2 is not set CONFIG_IPX=m CONFIG_IPX_INTERN=y # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set CONFIG_IRDA=m # # IrDA protocols # # CONFIG_IRLAN is not set # CONFIG_IRNET is not set # CONFIG_IRCOMM is not set # CONFIG_IRDA_ULTRA is not set # # IrDA options # # CONFIG_IRDA_CACHE_LAST_LSAP is not set # CONFIG_IRDA_FAST_RR is not set # CONFIG_IRDA_DEBUG is not set # # Infrared-port device drivers # # # SIR device drivers # # CONFIG_IRTTY_SIR is not set # # Dongle support # # # Old SIR device drivers # # CONFIG_IRPORT_SIR is not set # # Old Serial dongle support # # # FIR device drivers # # CONFIG_NSC_FIR is not set # CONFIG_WINBOND_FIR is not set # CONFIG_SMC_IRCC_FIR is not set # CONFIG_ALI_FIR is not set # CONFIG_VIA_FIR is not set CONFIG_BT=m # CONFIG_BT_L2CAP is not set # CONFIG_BT_SCO is not set # # Bluetooth device drivers # # CONFIG_BT_HCIUART is not set # CONFIG_BT_HCIDTL1 is not set # CONFIG_BT_HCIBT3C is not set # CONFIG_BT_HCIBLUECARD is not set # CONFIG_BT_HCIBTUART is not set # CONFIG_BT_HCIVHCI is not set CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set CONFIG_IEEE80211_CRYPT_WEP=m # CONFIG_IEEE80211_CRYPT_CCMP is not set # CONFIG_IEEE80211_CRYPT_TKIP is not set # CONFIG_IEEE80211_SOFTMAC is not set CONFIG_WIRELESS_EXT=y # # Device Drivers # # # Generic Driver Options # # CONFIG_STANDALONE is not set CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y # CONFIG_SYS_HYPERVISOR is not set # # Connector - unified userspace <-> kernelspace linker # # CONFIG_CONNECTOR is not set # # Memory Technology Devices (MTD) # CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set # CONFIG_MTD_CONCAT is not set # CONFIG_MTD_PARTITIONS is not set # # User Modules And Translation Layers # # CONFIG_MTD_CHAR is not set # CONFIG_MTD_BLOCK is not set # CONFIG_MTD_BLOCK_RO is not set # CONFIG_FTL is not set # CONFIG_NFTL is not set # CONFIG_INFTL is not set # CONFIG_RFD_FTL is not set # CONFIG_SSFDC is not set # # RAM/ROM/Flash chip drivers # # CONFIG_MTD_CFI is not set # CONFIG_MTD_JEDECPROBE is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set # CONFIG_MTD_RAM is not set # CONFIG_MTD_ROM is not set # CONFIG_MTD_ABSENT is not set # CONFIG_MTD_OBSOLETE_CHIPS is not set # # Mapping drivers for chip access # # CONFIG_MTD_COMPLEX_MAPPINGS is not set # CONFIG_MTD_TS5500 is not set # CONFIG_MTD_PLATRAM is not set # # Self-contained MTD device drivers # # CONFIG_MTD_SLRAM is not set # CONFIG_MTD_PHRAM is not set # CONFIG_MTD_MTDRAM is not set # CONFIG_MTD_BLOCK2MTD is not set # # Disk-On-Chip Device Drivers # # CONFIG_MTD_DOC2000 is not set # CONFIG_MTD_DOC2001 is not set # CONFIG_MTD_DOC2001PLUS is not set # # NAND Flash Device Drivers # # CONFIG_MTD_NAND is not set # # OneNAND Flash Device Drivers # # CONFIG_MTD_ONENAND is not set # # Parallel port support # CONFIG_PARPORT=m # CONFIG_PARPORT_PC is not set # CONFIG_PARPORT_GSC is not set # CONFIG_PARPORT_AX88796 is not set # CONFIG_PARPORT_1284 is not set # # Plug and Play support # # # Block devices # CONFIG_BLK_DEV_FD=m # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_RAM=m CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024 CONFIG_BLK_DEV_INITRD=y CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 CONFIG_CDROM_PKTCDVD_WCACHE=y CONFIG_ATA_OVER_ETH=m # # Misc devices # CONFIG_TIFM_CORE=m # # 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=y # CONFIG_BLK_DEV_IDECS is not set CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDETAPE=m CONFIG_BLK_DEV_IDEFLOPPY=m # CONFIG_BLK_DEV_IDESCSI is not set CONFIG_IDE_TASK_IOCTL=y # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set # CONFIG_IDE_ARM is not set # CONFIG_BLK_DEV_IDEDMA is not set # CONFIG_IDEDMA_AUTO is not set # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=m CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=m CONFIG_CHR_DEV_SCH=m # # 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 Transports # CONFIG_SCSI_SPI_ATTRS=y CONFIG_SCSI_FC_ATTRS=m CONFIG_SCSI_ISCSI_ATTRS=m # CONFIG_SCSI_SAS_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # # SCSI low-level drivers # # CONFIG_ISCSI_TCP is not set CONFIG_SCSI_DEBUG=m # # PCMCIA SCSI adapter support # # CONFIG_PCMCIA_AHA152X is not set # CONFIG_PCMCIA_FDOMAIN is not set # CONFIG_PCMCIA_NINJA_SCSI is not set # CONFIG_PCMCIA_QLOGIC is not set # CONFIG_PCMCIA_SYM53C500 is not set # # Serial ATA (prod) and Parallel ATA (experimental) drivers # CONFIG_ATA=m # CONFIG_PATA_PCMCIA is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=m # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID10 is not set # CONFIG_MD_RAID456 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_MD_FAULTY is not set CONFIG_BLK_DEV_DM=m # CONFIG_DM_DEBUG is not set # CONFIG_DM_CRYPT is not set # 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 # # IEEE 1394 (FireWire) support # # # I2O device support # # # Network device support # CONFIG_NETDEVICES=y CONFIG_DUMMY=m # CONFIG_BONDING is not set CONFIG_EQUALIZER=m CONFIG_TUN=m # # PHY device support # # CONFIG_PHYLIB is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # # Ethernet (10000 Mbit) # # # Token Ring devices # # # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # CONFIG_NET_WIRELESS_RTNETLINK is not set # # Obsolete Wireless cards support (pre-802.11) # # CONFIG_STRIP is not set # CONFIG_PCMCIA_WAVELAN is not set # CONFIG_PCMCIA_NETWAVE is not set # # Wireless 802.11 Frequency Hopping cards support # # CONFIG_PCMCIA_RAYCS is not set # # Wireless 802.11b ISA/PCI cards support # # CONFIG_HERMES is not set # CONFIG_ATMEL is not set # # Wireless 802.11b Pcmcia/Cardbus cards support # # CONFIG_AIRO_CS is not set # CONFIG_PCMCIA_WL3501 is not set # CONFIG_HOSTAP is not set CONFIG_NET_WIRELESS=y # # PCMCIA network device support # CONFIG_NET_PCMCIA=y # CONFIG_PCMCIA_3C589 is not set # CONFIG_PCMCIA_3C574 is not set # CONFIG_PCMCIA_FMVJ18X is not set # CONFIG_PCMCIA_PCNET is not set # CONFIG_PCMCIA_NMCLAN is not set # CONFIG_PCMCIA_SMC91C92 is not set # CONFIG_PCMCIA_XIRC2PS is not set # CONFIG_PCMCIA_AXNET is not set # # Wan interfaces # CONFIG_WAN=y CONFIG_HDLC=m CONFIG_HDLC_RAW=m CONFIG_HDLC_RAW_ETH=m CONFIG_HDLC_CISCO=m CONFIG_HDLC_FR=m CONFIG_HDLC_PPP=m # # X.25/LAPB support is disabled # CONFIG_DLCI=m CONFIG_DLCI_COUNT=24 CONFIG_DLCI_MAX=8 CONFIG_SBNI=m CONFIG_SBNI_MULTILINE=y # CONFIG_PLIP is not set CONFIG_PPP=m CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLHC=m CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y CONFIG_SHAPER=m CONFIG_NETCONSOLE=m CONFIG_NETPOLL=y # CONFIG_NETPOLL_RX is not set # CONFIG_NETPOLL_TRAP is not set CONFIG_NET_POLL_CONTROLLER=y # # ISDN subsystem # CONFIG_ISDN=m # # Old ISDN4Linux # # CONFIG_ISDN_I4L is not set # # CAPI subsystem # CONFIG_ISDN_CAPI=m # CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON is not set CONFIG_ISDN_CAPI_MIDDLEWARE=y CONFIG_ISDN_CAPI_CAPI20=m CONFIG_ISDN_CAPI_CAPIFS_BOOL=y CONFIG_ISDN_CAPI_CAPIFS=m # # CAPI hardware drivers # # # Active AVM cards # CONFIG_CAPI_AVM=y CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m # CONFIG_ISDN_DRV_AVMB1_AVM_CS is not set # # Active Eicon DIVA Server cards # CONFIG_CAPI_EICON=y # # Telephony Support # CONFIG_PHONE=m CONFIG_PHONE_IXJ=m CONFIG_PHONE_IXJ_PCMCIA=m # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y # CONFIG_INPUT_MOUSEDEV_PSAUX is not set CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set # CONFIG_INPUT_EVDEV is not set # 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_KEYBOARD_STOWAWAY is not set # CONFIG_INPUT_MOUSE 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_PARKBD is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # CONFIG_SERIAL_8250=m # CONFIG_SERIAL_8250_CS is not set CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=m CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set # CONFIG_PRINTER is not set # CONFIG_PPDEV is not set # CONFIG_TIPAR is not set # # IPMI # CONFIG_IPMI_HANDLER=m # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m # # Watchdog Cards # CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=m CONFIG_ACQUIRE_WDT=m CONFIG_ADVANTECH_WDT=m CONFIG_SC520_WDT=m CONFIG_EUROTECH_WDT=m CONFIG_IB700_WDT=m # CONFIG_IBMASR is not set CONFIG_WAFER_WDT=m CONFIG_SC1200_WDT=m CONFIG_60XX_WDT=m # CONFIG_SBC8360_WDT is not set CONFIG_CPU5_WDT=m # CONFIG_SMSC37B787_WDT is not set CONFIG_W83627HF_WDT=m # CONFIG_W83697HF_WDT is not set CONFIG_W83877F_WDT=m # CONFIG_W83977F_WDT is not set CONFIG_MACHZ_WDT=m # CONFIG_SBC_EPX_C3_WATCHDOG is not set CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_VIA=y CONFIG_NVRAM=y # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # # PCMCIA character devices # # CONFIG_SYNCLINK_CS is not set # CONFIG_CARDMAN_4000 is not set # CONFIG_CARDMAN_4040 is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # CONFIG_TCG_TPM=m CONFIG_TCG_ATMEL=m # CONFIG_TELCLOCK is not set # # I2C support # # CONFIG_I2C is not set # # SPI support # # CONFIG_SPI is not set # CONFIG_SPI_MASTER is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # # CONFIG_HWMON is not set # CONFIG_HWMON_VID is not set # # Multimedia devices # CONFIG_VIDEO_DEV=m # CONFIG_VIDEO_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_VIDEO_V4L2=y # # Video Capture Adapters # # # Video Capture Adapters # # CONFIG_VIDEO_ADV_DEBUG is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_VIVI=m # # Radio Adapters # # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set CONFIG_VIDEO_BUF=m # # Graphics support # # CONFIG_FIRMWARE_EDID is not set CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_ARC is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set # CONFIG_VIDEO_SELECT is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # # Logo configuration # # CONFIG_LOGO is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # CONFIG_SOUND=m # # Advanced Linux Sound Architecture # CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_DYNAMIC_MINORS=y CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # CONFIG_SND_MPU401_UART=m # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_MTS64 is not set # CONFIG_SND_SERIAL_U16550 is not set CONFIG_SND_MPU401=m # # PCMCIA devices # # CONFIG_SND_VXPOCKET is not set # CONFIG_SND_PDAUDIOCF is not set # # Open Sound System # # CONFIG_SOUND_PRIME is not set # # USB support # # CONFIG_USB_ARCH_HAS_HCD is not set # CONFIG_USB_ARCH_HAS_OHCI is not set # CONFIG_USB_ARCH_HAS_EHCI is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # USB Gadget Support # CONFIG_USB_GADGET=m # CONFIG_USB_GADGET_DEBUG_FILES is not set # CONFIG_USB_GADGET_NET2280 is not set # CONFIG_USB_GADGET_PXA2XX is not set # CONFIG_USB_GADGET_GOKU is not set # CONFIG_USB_GADGET_LH7A40X is not set # CONFIG_USB_GADGET_OMAP is not set # CONFIG_USB_GADGET_AT91 is not set # CONFIG_USB_GADGET_DUMMY_HCD is not set # CONFIG_USB_GADGET_DUALSPEED is not set # # MMC/SD Card support # CONFIG_MMC=m CONFIG_MMC_DEBUG=y CONFIG_MMC_BLOCK=m CONFIG_MMC_WBSD=m CONFIG_MMC_TIFM_SD=m # # LED devices # # CONFIG_NEW_LEDS is not set # # LED drivers # # # LED Triggers # # # InfiniBand support # # # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) # # CONFIG_EDAC is not set # # Real Time Clock # # CONFIG_RTC_CLASS is not set # # DMA Engine support # # CONFIG_DMA_ENGINE is not set # # DMA Clients # # # DMA 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=y CONFIG_EXT3_FS_SECURITY=y # CONFIG_EXT4DEV_FS 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=m # CONFIG_JFS_POSIX_ACL is not set # CONFIG_JFS_SECURITY is not set # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set CONFIG_FS_POSIX_ACL=y CONFIG_XFS_FS=m CONFIG_XFS_QUOTA=y # CONFIG_XFS_SECURITY is not set CONFIG_XFS_POSIX_ACL=y CONFIG_XFS_RT=y # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set CONFIG_MINIX_FS=m CONFIG_ROMFS_FS=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_QUOTA=y CONFIG_QFMT_V1=m CONFIG_QFMT_V2=m CONFIG_QUOTACTL=y CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=m # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_ZISOFS_FS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set CONFIG_NTFS_RW=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_CONFIGFS_FS is not set # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_ECRYPT_FS is not set CONFIG_HFS_FS=y CONFIG_HFSPLUS_FS=y # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_JFFS_FS is not set # CONFIG_JFFS2_FS is not set CONFIG_CRAMFS=y CONFIG_VXFS_FS=m CONFIG_HPFS_FS=m CONFIG_QNX4FS_FS=m CONFIG_SYSV_FS=m CONFIG_UFS_FS=m # CONFIG_UFS_FS_WRITE is not set # CONFIG_UFS_DEBUG is not set # # Network File Systems # # CONFIG_NFS_FS is not set # CONFIG_NFSD 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 # CONFIG_9P_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=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set CONFIG_LDM_PARTITION=y # CONFIG_LDM_DEBUG is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_KARMA_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=m CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=m CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=y # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_MUST_CHECK is not set # CONFIG_MAGIC_SYSRQ is not set # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_FS is not set # CONFIG_UNWIND_INFO is not set # CONFIG_HEADERS_CHECK is not set CONFIG_EARLY_PRINTK=y CONFIG_DOUBLEFAULT=y # # Security options # CONFIG_KEYS=y # CONFIG_KEYS_DEBUG_PROC_KEYS is not set CONFIG_SECURITY=y # CONFIG_SECURITY_NETWORK is not set CONFIG_SECURITY_CAPABILITIES=m # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=m CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=y CONFIG_CRYPTO_SHA512=y CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_CBC=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m # CONFIG_CRYPTO_TWOFISH_586 is not set CONFIG_CRYPTO_SERPENT=m # CONFIG_CRYPTO_AES is not set CONFIG_CRYPTO_AES_586=y CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_TEST=m # # Hardware crypto devices # CONFIG_CRYPTO_DEV_PADLOCK=m CONFIG_CRYPTO_DEV_PADLOCK_AES=m CONFIG_CRYPTO_DEV_PADLOCK_SHA=m # # Library routines # CONFIG_CRC_CCITT=m # CONFIG_CRC16 is not set CONFIG_CRC32=y CONFIG_LIBCRC32C=m CONFIG_AUDIT_GENERIC=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_PLIST=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y Thanks, MikeE

2 1

Re: L4linux Booting Problem
by Adam Lackorzynski 17 Mar '07

17 Mar '07

Hi, I fished this email out of the spam folder of l4-hackers and if you look below there's little doubt why it was put there. To all: Guys, please STOP sending HTML mails and use a proper email client. Thanks a lot. On Wed Mar 14, 2007 at 22:14:45 +0900, Yunju Na wrote: > I am trying to install L4/fiasco and L4linux on my computer. > > > I downloaded source files from CVS and compiled reffering document > "L4/Fiasco/L4Linux Kickstart" (written by Gheng Guanghui, Nicholas Mc > Guire). > > Source compile is OK. > > > But when I boot the machine, L4linux is shotdown in the middle of > booting. > > > I saw the message "Warning: unable to open an initial console." before > shotdown. I cannot tell you why it breaks but I can ask a couple of question to make the situation clearer for me. You are starting two instances of L4Linux. Looks like one is failing because it wants to request some device resource which was already requested by the other L4Linux. Did you use different configuration for both builds? Does only one L4Linux work? You may want to add 'console=ttyLv0' to the kernel command line to see more output of L4Linux on the serial console. What does it show? Please start with a simple configuration and make it more complicated step by step. > Roottask: Loading 19 modules. > #05: loading > "/boot/DDL4/l4v2/events" >      from [0212d000-021731cc] to > [01540000-015491e4][0154a000-0154c954] >      entry at > 0005b370 via trampoline page code >      symbols at > [7c3fe000-7c400000] (8kB), lines at [7c3f7000-7c3fe000] (28kB) > #06: loading > "/boot/DDL4/l4v2/names --events" >      from > [02174000-021b662e] to > [002d0000-002d616a][002d7000-002e3000] >      entry at > 0005c378 via trampoline page code >      symbols at > [7c3f5000-7c3f7000] (8kB), lines at [7c3ef000-7c3f5000] (24kB) > #07: loading > "/boot/DDL4/l4v2/log --prio 0xA1" >      from > [021b7000-021f6177] to > [00400000-00406c4a][00407000-004398b0] >      entry at > 0005d378 via trampoline page code >      symbols at > [7c3ed000-7c3ef000] (8kB), lines at [7c3e7000-7c3ed000] (24kB) > #08: loading > "/boot/DDL4/l4v2/dm_phys --events" >      from > [021f7000-02284e59] to > [01500000-015120ca][01513000-0151d000] >      entry at > 0005e37c via trampoline page code >      symbols at > [7c3e2000-7c3e7000] (20kB), lines at [7c3d5000-7c3e2000] (52kB) > #09: loading > "/boot/DDL4/l4v2/simple_ts -t 400 --events" >      from > [02285000-022d1ea9] to > [01400000-014086ca][01409000-0141b070] >      entry at > 0005f384 via trampoline page code >      symbols at > [7c3d3000-7c3d5000] (8kB), lines at [7c3cc000-7c3d3000] (28kB) > #0a: loading > "/boot/DDL4/l4v2/rtc" >      from [022d2000-02304842] to > [01080000-01084200][01085000-0108a000] >      entry at > 0006136c via trampoline page code >      symbols at > [7c3ca000-7c3cc000] (8kB), lines at [7c3c6000-7c3ca000] (16kB) > #0b: loading > "/boot/DDL4/l4v2/l4io --noirq" >      from > [02305000-02552c4e] to > [00b80000-00ba29e4][00ba3000-00c0e000] >      entry at > 00062378 via trampoline page code >      symbols at > [7c377000-7c3c6000] (316kB), lines at [7c35d000-7c377000] (104k) > #0c: loading > "/boot/DDL4/l4v2/bmodfs" >      from [02553000-025f4b22] to > [01220000-01235524][01236000-01256000] >      passing > module /boot/DDL4/l4v2/libloader.s.so        > [ 025f5000-026971bd ] >      passing module > /boot/DDL4/l4v2/libld-l4.s.so         [ > 02698000-02711019 ] >      passing module > /boot/DDL4/l4v2/run                   > [ 02712000-02759ef4 ] >      passing module > /boot/DDL4/cfg/run.bmodfs.cfg         [ > 0275a000-0275a078 ] >      passing module > /boot/DDL4/linux/vmlinuz26.ddosnet    [ 0275b000-035ad0e7 > ] >      passing module > /boot/DDL4/linux/vmlinuz26.vt         [ > 035ae000-043cb06e ] >      passing module > /boot/DDL4/cfg/l4linux26_net.cfg      [ > 043cc000-043cc0b0 ] >      passing module > /boot/DDL4/cfg/l4linux26_vt.cfg       [ > 043cd000-043cd05e ] >      passing module > /boot/DDL4/cfg/tty.rd                 > [ 043ce000-04dce000 ] >      entry at 00063514 via > trampoline page code >      symbols at [7c358000-7c35d000] > (20kB), lines at [7c347000-7c358000] (68kB) > #0d: loading "/boot/DDL4/l4v2/con > --l4io --events" >      from [04dce000-04f5df2b] to > [00b00000-00b4d0a0][00b4e000-00b79000] >      entry at > 0006437c via trampoline page code >      symbols at > [7c33a000-7c347000] (52kB), lines at [7c306000-7c33a000] (208kB) > #0e: loading > "/boot/DDL4/l4v2/loader --events --fprov=BMODFS run.bmodfs.cfg > l4l" >      from [04f5e000-050364fd] to > [01300000-01324f28][01325000-0134e000] >      entry at > 000653bc via trampoline page code >      symbols at > [7c300000-7c306000] (24kB), lines at [7c2e8000-7c300000] (96kB) > > > names   | Starting thread listening for `exit' events > simplets| > Configured for 400 tasks. > rtc     | Date:14.03.2007 > Time:16:15:02 > bmodfs  | Passed the following modules: > bmodfs  > |   module "/boot/DDL4/l4v2/libloader.s.so" (649kB) > bmodfs  > |   module "/boot/DDL4/l4v2/libld-l4.s.so" (485kB) > bmodfs  > |   module "/boot/DDL4/l4v2/run" (288kB) > bmodfs  |   > module "/boot/DDL4/cfg/run.bmodfs.cfg" (1kB) > bmodfs  |   > module "/boot/DDL4/linux/vmlinuz26.ddosnet" (14665kB) > bmodfs  > |   module "/boot/DDL4/linux/vmlinuz26.vt" (14453kB) > bmodfs  > |   module "/boot/DDL4/cfg/l4linux26_net.cfg" (1kB) > bmodfs  > |   module "/boot/DDL4/cfg/l4linux26_vt.cfg" (1kB) > bmodfs  > |   module "/boot/DDL4/cfg/tty.rd" > (10240kB) > io      | do_args(): Disabling internal > IRQ handling. > io      | CPU supports 8 MTRRs. > Allocated: > io      |   0: > 00000000-80000000 (2048MB) type WB > io      > |   1: 7ff80000-80000000 (   1MB) type > UC > con     | Using fast memcpy. > loader  | run: > Starting application using libld-l4.s.so > loader  | run,#f: Loading > binary > loader  | run,#f: Loading ldso > loader  | Capability > support not supported. > loader  | run,#f: Starting libld-l4.s.so at > 00013890 via 0000cc80 > loader  | sleeping for 1000 > ms > io      | PCI: Using configuration type > 1 > io      | PCI: Probing PCI > hardware > io      | PCI: Probing PCI hardware (bus > 00) > io      | PCI: Ignoring BAR0-3 of IDE controller > 00:1f.1 > io      | Transparent bridge - Intel > Corporation 82801 PCI Bridge > io      | PCI: Enabling > device 00:1f.1 (0005 -> 0007) > io      | PCI: No > IRQ known for interrupt pin B of device 00:1f.3. Please try > u > io      : sing > pci=biosirq. > io      | 00000000-ffffffff : PCI > mem > io      |   80000000-800003ff : Intel > Corporation 82801CA Ultra ATA Storage Con > io      : > troller > io      |   fc100000-fc2fffff : > PCI Bus #01 > io      |     > fc100000-fc100fff : Intel Corporation 82870P2 P64H2 > I/OxAPIC > io      |     > fc101000-fc101fff : Intel Corporation 82870P2 P64H2 I/OxAPIC > (#2) > io      |     > fc200000-fc2fffff : PCI Bus #03 > io      > |       fc200000-fc21ffff : Intel Corporation > 82546EB Gigabit Ethernet > io      : Controller > (Copper) > io      > |       fc220000-fc23ffff : Intel Corporation > 82546EB Gigabit Ethernet > io      : Controller > (Copper) (#2) > io      |   > fc300000-fc6fffff : PCI Bus #04 > io      > |     fc300000-fc300fff : Intel Corporation 82870P2 P64H2 > I/OxAPIC (#3) > io      |     > fc301000-fc301fff : Intel Corporation 82870P2 P64H2 I/OxAPIC > (#4) > io      |     > fc400000-fc5fffff : PCI Bus #05 > io      > |       fc400000-fc400fff : Intel Corporation > 82557/8/9 [Ethernet Pro 1 > io      : > 00] > io      |       > fc500000-fc5fffff : Intel Corporation 82557/8/9 [Ethernet Pro > 1 > io      : 00] > io      > |     fc600000-fc6fffff : PCI Bus > #06 > io      |       > fc600000-fc601fff : Adaptec AIC-7902B U320 > io      > |       fc602000-fc603fff : Adaptec AIC-7902B U320 > (#2) > io      |   fc700000-fc700fff : ATI > Technolog0000-ffff : PCI IO > io      |   > 0cf8-0cff : PCI conf1 > io      |   > 1100-111f : Intel Corporation 82801CA/CAM SMBus > Controller > io      |   2000-201f : Intel > Corporation 82801CA/CAM USB (Hub #1) > io      > |   2020-203f : Intel Corporation 82801CA/CAM USB (Hub > #2) > io      |   2040-205f : Intel > Corporation 82801CA/CAM USB (Hub #3) > io      > |   2060-206f : Intel Corporation 82801CA Ultra ATA Storage > Controller > io      |   3000-3fff : PCI Bus > #01 > io      |     3000-3fff : > PCI Bus #03 > io      > |       3000-303f : Intel Corporation 82546EB > Gigabit Ethernet Controll > io      : er > (Copper) > io      > |       3040-307f : Intel Corporation 82546EB > Gigabit Ethernet Controll > io      : er (Copper) > (#2) > io      |   4000-5fff : PCI Bus > #04 > io      |     4000-4fff : > PCI Bus #05 > io      > |       4000-40ff : PCI device > 177d:0001 > io      > |       4400-44ff : PCI device > 177d:0001 > io      > |       4800-483f : Intel Corporation 82557/8/9 > [Ethernet Pro 100] > io      |     > 5000-5fff : PCI Bus #06 > io      > |       5000-50ff : Adaptec AIC-7902B > U320 > io      |       > 5400-54ff : Adaptec AIC-7902B U320 > io      > |       5800-58ff : Adaptec AIC-7902B U320 > (#2) > io      |       > 5c00-5cff : Adaptec AIC-7902B U320 (#2) > io      > |   6000-60ff : ATI Technologies Inc Rage > XL > con     | Character size is 8x14, font has 256 > characters > con     | VESA reports > 1024x768@16 > 2048bpl (00bb) > [8128kB] > con     | Color mapping: red=11:5 green=5:6 > blue=0:5 res=0:0 > con     | Mapped I/O ctrl mem fc700000 > => 02300000+000000 [4kB] via l4io > con     | Found ATI > 3D RAGE (XL) [0x4752 rev 0x27] (PCI 07/08) > io      | > Remapping I/O memory fd000000-fd7f0000 > cached > io      | Setting MTRR 2 to fd000000-fd800000 > type WC > con     | Mapped I/O video mem fd000000 => > 03000000+000000 [8128kB] via l4io > con     | Backend > scaler: no, color keying: no > con     | Using MMXEXT for > colorspace transform > con     | > L4INPUT:                > !!! W A R N I N G !!! > con     | L4INPUT:  Please, do > not use Fiasco's "-esc" with L4INPUT. > con     | > L4INPUT:                > !!! W A R N I N G !!! > con     | L4INPUT: Registered > 0xb03c50 for callbacks. > con     | serio: i8042 AUX port > at 0x60,0x64 irq 12 > con     | serio: i8042 KBD port at > 0x60,0x64 irq 1 > con     | input: ImExPS/2 Generic > Explorer Mouse on isa0060/serio1 > con     | input: AT > Translated Set 2 keyboard on isa0060/serio0 > con     | > input: PC Speaker > con     | input: L4 input event > injector > con     | L4 input event injector: IRQ handler > up > con     | connect "ImExPS/2 Generic Explorer Mouse", > isa0060/serio1/input0 > con     | connect "AT Translated > Set 2 keyboard", isa0060/serio0/input0 > con     | connect > "PC Speaker", isa0061/input0 > con     | connect "L4 input > event injector", l4/sys > con     | Running as D.02. Video > mode is > 1024x768@16 > . > con     | > vc_loop(): vc[1] running as D.08 > con     | vc_open_out(): > vc[1] > 1024x768@16 > , > gmode:0x35 > run     | contxt_init(): 1024x750, cols:128, > lines:53, sb_lines:1053 > loader  | vmlinuz26.ddosnet: Starting > application using libld-l4.s.so > loader  | vmlinuz26.ddosnet,#10: Loading > binary > loader  | vmlinuz26.ddosnet,#10: Loading ldso > loader  | > Capability support not supported. > loader  | vmlinuz26.ddosnet,#10: > Starting libld-l4.s.so at 00013890 via 0000cc1 > loader  : > c > loader  | sleeping for 30000 ms > l4lx    | ======> > L4Linux 2.6 starting... <======== > l4lx    | Linux version > 2.6.19-l4 ( > root(a)dup.postech.ac.kr > ) > (gcc version 3.4.6) > l4lx    : #1 Thu Mar 8 15:30:29 KST > 2007 > l4lx    | Binary name: > vmlinuz26.ddosnet > l4lx    | Kernel command line (8 args): > mem=32M noreplacement root=1:0 load_ram > l4lx    : disk=1 > ramdisk_size=10240 l4env_rd=tty.rd panicblink=0 > lang=us > l4lx    | Image: 00400000 - 0072d000 [3252 > KiB]. > l4lx    | Areas: Text:     00400000 > - 00643000 [2316kB] (a bit longer) > l4lx    > |        Data:     > 00643000 - 0068808c [276kB] > l4lx    > |        Initdata: 0068c000 - 006c2000 > [216kB] > l4lx    |        > BSS:      006c4000 - 0072b7a0 > [413kB] > l4lx    | l4lx_thread_create: Created thread 10.03 > (server) > l4lx    | main thread will be > 10.03 > l4lx    | l4env_register_pointer_section: addr = > 0068a000 size = 233472 > l4lx    |      > sec-w-init: virt: 0x0068a000 to 0x006c2fff [228 KiB] > l4lx    > |      sec-w-init: Number of physical regions: 1, > 233472 Bytes > l4lx    |      > sec-w-init: 1: Phys: 0x0148c000 to 0x014c5000, Size:   > 233472 > l4lx    | l4env_linux_startup thread > 3. > l4lx    | main thread: received startup > message. > l4lx    | Main thread running, > waiting... > l4lx    | setup_l4env_memory: Forcing superpages > for main memory > l4lx    | Main memory size: > 32MB > l4lx    |     Main memory: virt: > 0x00800000 to 0x027fffff [32768 KiB] > l4lx    > |     Main memory: Number of physical regions: 1, 33554432 > Bytes > l4lx    |     Main memory: 1: Phys: > 0x7a000000 to 0x7c000000, Size: 33554432 > l4lx    | Filling > lower ptabs... > l4lx    | Done (1104 > entries). > l4lx    | l4env_rd_path: > tty.rd > l4lx    | Loading: tty.rd > l4lx    | > INITRD: Size of RAMdisk is 10240KiB > l4lx    | RAMdisk from > 02800000 to 03200000 [10240KiB] > l4lx    | l4lx_thread_create: > Created thread 10.04 (timer.i0) > l4lx    | l4lx_thread_create: > Created thread 10.05 (Idler) > l4lx    | Starting L4FB via > CON > con     | vc_loop(): vc[2] running as > D.09 > l4lx    | l4lx_thread_create: Created thread 10.06 > (L4ConInput) > con     | vc_open_out(): vc[2] > 1024x768@16 > , gmode:0x35 > l4lx    > | l4fbcon: 1024x750 2bypp, size: 1540096 > l4lx    | > l4lx_thread_create: Created thread 10.07 (CON > refresher) > l4lx    | DDOS : [eth0]  card found with > 00:30:48:27:E3:AC, IRQ 0 > l4lx    | l4lx_thread_create: Created > thread 10.08 (IRQ11) > l4lx    | l4lx_thread_create: Created > thread 10.09 (DDOSnetMain) > loader  | vmlinuz26.vt: Starting application > using libld-l4.s.so > loader  | vmlinuz26.vt,#1a: Loading > binary > loader  | vmlinuz26.vt,#1a: Loading ldso > loader  | > Capability support not supported. > loader  | vmlinuz26.vt,#1a: Starting > libld-l4.s.so at 00013890 via 0000cc6c > l4lx    | ======> > L4Linux 2.6 starting... <======== > l4lx    | Linux version > 2.6.19-l4 ( > root(a)dup.postech.ac.kr > ) > (gcc version 3.4.6) > l4lx    : #5 Thu Mar 8 19:38:18 KST > 2007 > l4lx    | Binary name: > vmlinuz26.vt > l4lx    | Kernel command line (2 args): mem=512M > root=/dev/hda1 > l4lx    | Image: 00400000 - 0071a000 [3176 > KiB]. > l4lx    | Areas: Text:     00400000 > - 00635000 [2260kB] (a bit longer) > l4lx    > |        Data:     > 00635000 - 0067908c [272kB] > l4lx    > |        Initdata: 0067c000 - 006ac000 > [192kB] > l4lx    |        > BSS:      006ae000 - 007184d0 > [425kB] > l4lx    | l4lx_thread_create: Created thread 1a.03 > (tamer) > l4lx    | Using tamed mode. > l4lx    > | l4lx_thread_create: Created thread 1a.04 (server) > l4lx    | > main thread will be 1a.04 > l4lx    | > l4env_register_pointer_section: addr = 00635000 size = > 491520 > l4lx    |      sec-w-init: > virt: 0x00635000 to 0x006acfff [480 KiB] > l4lx    > |      sec-w-init: Number of physical regions: 1, > 491520 Bytes > l4lx    |      > sec-w-init: 1: Phys: 0x00e63000 to 0x00edb000, Size:   > 491520 > 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: > 512MB > l4lx    |     Main memory: virt: > 0x00800000 to 0x207fffff [524288 KiB] > l4lx    > |     Main memory: Number of physical regions: 1, 536870912 > Bytes > l4lx    |     Main memory: 1: Phys: > 0x5a000000 to 0x7a000000, Size: 536870912 > l4lx    | Filling > lower ptabs... > l4lx    | Done (1122 > entries). > l4lx    | l4lx_thread_create: Created thread 1a.05 > (timer.i0) > > >     --l4io_request_mem_region > error--------------------------IP: 0040f98b > (1a.04) jdb: > g > l4lx    | l4lx_thread_create: Created thread 1a.06 > (Idler) > l4lx    | Starting L4FB via > CON > con     | vc_loop(): vc[3] running as > D.0A > l4lx    | l4lx_thread_create: Created thread 1a.07 > (L4ConInput) > con     | vc_open_out(): vc[3] > 1024x768@16 > , gmode:0x35 > l4lx    > | l4fbcon: 1024x750 2bypp, size: 1540096 > l4lx    | > l4lx_thread_create: Created thread 1a.08 (CON > refresher) > l4lx    | l4lx_thread_create: Created thread 10.0a > (PosDDOSNetWorker) > l4lx    | DDOS : main thread sleep > forerver. > l4lx    | l4lx_thread_create: Created thread 1a.09 > (IRQ14) > l4lx    | l4lx_thread_create: Created thread 1a.0a > (IRQ15) > l4lx    | Terminating L4Linux. > simplets| Exit > 1A.02 > con     | switch_vc(): switch to vc 02 > > > Welcome to Fiasco(ia32)! > DD-L4(v2)/x86 microkernel (C) 1998-2006 TU > Dresden > Rev: Wed Mar 14 03:48:02 2007 compiled with gcc 3.4.6 for Intel > Pentium > 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 > Absolute KIP Syscalls using: Sysenter > CPU: GenuineIntel > (F:2:5:B) Model: Pentium 4 (Northwood/Prestonia) at 2799 MHz > > >   64 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) > > > Calibrating timer loop... done. > SIGMA0: Hello! >   KIP @ > 1000 >   Found Fiasco: KIP syscalls: yes >   allocated 4KB for > maintenance structures > > > Roottask. >   Command line found: "/boot/OrgL4/l4v2/roottask task > modname "bmodfs" attached" > > >  2095677kB (2046MB) total RAM (reported by > bootloader) >  2028708kB (1982MB) received RAM from Sigma0 >    > 26692kB (  27MB) reserved RAM for RMGR >   Received I/O ports > 0000-ffff >   Attached irqs = [ <!0> 1 <!2> 3 4 5 6 7 8 9 A B > C D E F ] > > > Roottask: Parsing command line config. >   configured task 0x00 > (bmodfs): >     vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff > prio:10 small:ff mods:6 > > > Roottask: Loading 16 modules. > #05: loading > "/boot/OrgL4/l4v2/events" >      from [0212d000-02173281] > to [01540000-015491e4][0154a000-0154c954] >      entry at > 0005b370 via trampoline page code >      symbols at > [7c3fe000-7c400000] (8kB), lines at [7c3f7000-7c3fe000] (28kB) > #06: loading > "/boot/OrgL4/l4v2/names --events" >      from > [02174000-021b66db] to > [002d0000-002d616a][002d7000-002e3000] >      entry at > 0005c378 via trampoline page code >      symbols at > [7c3f5000-7c3f7000] (8kB), lines at [7c3ef000-7c3f5000] (24kB) > #07: loading > "/boot/OrgL4/l4v2/log --prio 0xA1" >      from > [021b7000-021f621c] to > [00400000-00406c4a][00407000-004398b0] >      entry at > 0005d37c via trampoline page code >      symbols at > [7c3ed000-7c3ef000] (8kB), lines at [7c3e7000-7c3ed000] (24kB) > #08: loading > "/boot/OrgL4/l4v2/dm_phys --events" >      from > [021f7000-02284f46] to > [01500000-015120ea][01513000-0151d000] >      entry at > 0005e37c via trampoline page code >      symbols at > [7c3e2000-7c3e7000] (20kB), lines at [7c3d5000-7c3e2000] (52kB) > #09: loading > "/boot/OrgL4/l4v2/simple_ts -t 300 --events" >      from > [02285000-022d1f5a] to > [01400000-014086ca][01409000-0141b070] >      entry at > 0005f384 via trampoline page code >      symbols at > [7c3d3000-7c3d5000] (8kB), lines at [7c3cc000-7c3d3000] (28kB) > #0a: loading > "/boot/OrgL4/l4v2/rtc" >      from [022d2000-023048c7] to > [01080000-01084200][01085000-0108a000] >      entry at > 00061370 via trampoline page code >      symbols at > [7c3ca000-7c3cc000] (8kB), lines at [7c3c6000-7c3ca000] (16kB) > #0b: loading > "/boot/OrgL4/l4v2/l4io --noirq" >      from > [02305000-02552e67] to > [00b80000-00ba2a08][00ba3000-00c0e000] >      entry at > 00062378 via trampoline page code >      symbols at > [7c377000-7c3c6000] (316kB), lines at [7c35d000-7c377000] (104k) > #0c: loading > "/boot/OrgL4/l4v2/bmodfs" >      from [02553000-025f4c5b] > to [01220000-01235544][01236000-01256000] >      passing > module /boot/OrgL4/l4v2/libloader.s.so       [ > 025f5000-026972c6 ] >      passing module > /boot/OrgL4/l4v2/libld-l4.s.so        [ > 02698000-027110ad ] >      passing module > /boot/OrgL4/l4v2/run                  > [ 02712000-02759f9a ] >      passing module > /boot/OrgL4/cfg/run.bmodfs.cfg        [ > 0275a000-0275a025 ] >      passing module > /boot/OrgL4/linux/vmlinuz26           > [ 0275b000-0373333e ] >      passing module > /boot/OrgL4/cfg/l4linux26.cfg         [ > 03734000-03734056 ] >      entry at 00063484 via trampoline > page code >      symbols at [7c358000-7c35d000] (20kB), > lines at [7c347000-7c358000] (68kB) > #0d: loading "/boot/OrgL4/l4v2/con --l4io > --events" >      from [03735000-038c5116] to > [00b00000-00b4d0e0][00b4e000-00b79000] >      entry at > 00064380 via trampoline page code >      symbols at > [7c33a000-7c347000] (52kB), lines at [7c306000-7c33a000] (208kB) > #0e: loading > "/boot/OrgL4/l4v2/loader --events --fprov=BMODFS run.bmodfs.cfg > l4" >      from [038c6000-0399e68a] to > [01300000-01324f28][01325000-0134e000] >      entry at > 000653a8 via trampoline page code >      symbols at > [7c300000-7c306000] (24kB), lines at [7c2e8000-7c300000] (96kB) > > > names   | Starting thread listening for `exit' events > simplets| > Configured for 300 tasks. > rtc     | Date:14.03.2007 > Time:16:17:09 > bmodfs  | Passed the following modules: > bmodfs  > |   module "/boot/OrgL4/l4v2/libloader.s.so" (649kB) > bmodfs  > |   module "/boot/OrgL4/l4v2/libld-l4.s.so" (485kB) > bmodfs  > |   module "/boot/OrgL4/l4v2/run" (288kB) > bmodfs  > |   module "/boot/OrgL4/cfg/run.bmodfs.cfg" (1kB) > bmodfs  > |   module "/boot/OrgL4/linux/vmlinuz26" (16225kB) > bmodfs  > |   module "/boot/OrgL4/cfg/l4linux26.cfg" > (1kB) > con     | Using fast > memcpy. > io      | do_args(): Disabling internal IRQ > handling. > io      | CPU supports 8 MTRRs. > Allocated: > io      |   0: > 00000000-80000000 (2048MB) type WB > io      > |   1: 7ff80000-80000000 (   1MB) type UC > loader  | > run: Starting application using libld-l4.s.so > loader  | run,#f: Loading > binary > loader  | run,#f: Loading ldso > loader  | Capability > support not supported. > loader  | run,#f: Starting libld-l4.s.so at > 00013890 via 0000cc80 > loader  | sleeping for 2000 > ms > io      | PCI: Using configuration type > 1 > io      | PCI: Probing PCI > hardware > io      | PCI: Probing PCI hardware (bus > 00) > io      | PCI: Ignoring BAR0-3 of IDE controller > 00:1f.1 > io      | Transparent bridge - Intel > Corporation 82801 PCI Bridge > io      | PCI: Enabling > device 00:1f.1 (0005 -> 0007) > io      | PCI: No > IRQ known for interrupt pin B of device 00:1f.3. Please try > u > io      : sing > pci=biosirq. > io      | 00000000-ffffffff : PCI > mem > io      |   80000000-800003ff : Intel > Corporation 82801CA Ultra ATA Storage Con > io      : > troller > io      |   fc100000-fc2fffff : > PCI Bus #01 > io      |     > fc100000-fc100fff : Intel Corporation 82870P2 P64H2 > I/OxAPIC > io      |     > fc101000-fc101fff : Intel Corporation 82870P2 P64H2 I/OxAPIC > (#2) > io      |     > fc200000-fc2fffff : PCI Bus #03 > io      > |       fc200000-fc21ffff : Intel Corporation > 82546EB Gigabit Ethernet > io      : Controller > (Copper) > io      > |       fc220000-fc23ffff : Intel Corporation > 82546EB Gigabit Ethernet > io      : Controller > (Copper) (#2) > io      |   > fc300000-fc6fffff : PCI Bus #04 > io      > |     fc300000-fc300fff : Intel Corporation 82870P2 P64H2 > I/OxAPIC (#3) > io      |     > fc301000-fc301fff : Intel Corporation 82870P2 P64H2 I/OxAPIC > (#4) > io      |     > fc400000-fc5fffff : PCI Bus #05 > io      > |       fc400000-fc400fff : Intel Corporation > 82557/8/9 [Ethernet Pro 1 > io      : > 00] > io      |       > fc500000-fc5fffff : Intel Corporation 82557/8/9 [Ethernet Pro > 1 > io      : 00] > io      > |     fc600000-fc6fffff : PCI Bus > #06 > io      |       > fc600000-fc601fff : Adaptec AIC-7902B U320 > io      > |       fc602000-fc603fff : Adaptec AIC-7902B U320 > (#2) > io      |   fc700000-fc700fff : ATI > Technolog0000-ffff : PCI IO > io      |   > 0cf8-0cff : PCI conf1 > io      |   > 1100-111f : Intel Corporation 82801CA/CAM SMBus > Controller > io      |   2000-201f : Intel > Corporation 82801CA/CAM USB (Hub #1) > io      > |   2020-203f : Intel Corporation 82801CA/CAM USB (Hub > #2) > io      |   2040-205f : Intel > Corporation 82801CA/CAM USB (Hub #3) > io      > |   2060-206f : Intel Corporation 82801CA Ultra ATA Storage > Controller > io      |   3000-3fff : PCI Bus > #01 > io      |     3000-3fff : > PCI Bus #03 > io      > |       3000-303f : Intel Corporation 82546EB > Gigabit Ethernet Controll > io      : er > (Copper) > io      > |       3040-307f : Intel Corporation 82546EB > Gigabit Ethernet Controll > io      : er (Copper) > (#2) > io      |   4000-5fff : PCI Bus > #04 > io      |     4000-4fff : > PCI Bus #05 > io      > |       4000-40ff : PCI device > 177d:0001 > io      > |       4400-44ff : PCI device > 177d:0001 > io      > |       4800-483f : Intel Corporation 82557/8/9 > [Ethernet Pro 100] > io      |     > 5000-5fff : PCI Bus #06 > io      > |       5000-50ff : Adaptec AIC-7902B > U320 > io      |       > 5400-54ff : Adaptec AIC-7902B U320 > io      > |       5800-58ff : Adaptec AIC-7902B U320 > (#2) > io      |       > 5c00-5cff : Adaptec AIC-7902B U320 (#2) > io      > |   6000-60ff : ATI Technologies Inc Rage > XL > con     | Character size is 8x14, font has 256 > characters > con     | VESA reports > 1024x768@16 > 2048bpl (00bb) > [8128kB] > con     | Color mapping: red=11:5 green=5:6 > blue=0:5 res=0:0 > con     | Mapped I/O ctrl mem fc700000 > => 02300000+000000 [4kB] via l4io > con     | Found ATI > 3D RAGE (XL) [0x4752 rev 0x27] (PCI 07/08) > io      | > Remapping I/O memory fd000000-fd7f0000 > cached > io      | Setting MTRR 2 to fd000000-fd800000 > type WC > con     | Mapped I/O video mem fd000000 => > 03000000+000000 [8128kB] via l4io > con     | Backend > scaler: no, color keying: no > con     | Using MMXEXT for > colorspace transform > con     | > L4INPUT:                > !!! W A R N I N G !!! > con     | L4INPUT:  Please, do > not use Fiasco's "-esc" with L4INPUT. > con     | > L4INPUT:                > !!! W A R N I N G !!! > con     | L4INPUT: Registered > 0xb03c50 for callbacks. > con     | serio: i8042 AUX port > at 0x60,0x64 irq 12 > con     | serio: i8042 KBD port at > 0x60,0x64 irq 1 > con     | input: ImExPS/2 Generic > Explorer Mouse on isa0060/serio1 > con     | input: AT > Translated Set 2 keyboard on isa0060/serio0 > con     | > input: PC Speaker > con     | input: L4 input event > injector > con     | L4 input event injector: IRQ handler > up > con     | connect "ImExPS/2 Generic Explorer Mouse", > isa0060/serio1/input0 > con     | connect "AT Translated > Set 2 keyboard", isa0060/serio0/input0 > con     | connect > "PC Speaker", isa0061/input0 > con     | connect "L4 input > event injector", l4/sys > con     | Running as D.02. Video > mode is > 1024x768@16 > . > con     | > vc_loop(): vc[1] running as D.08 > con     | vc_open_out(): > vc[1] > 1024x768@16 > , > gmode:0x35 > run     | contxt_init(): 1024x750, cols:128, > lines:53, sb_lines:1053 > loader  | vmlinuz26: Starting application using > libld-l4.s.so > loader  | vmlinuz26,#10: Loading binary > loader  | > vmlinuz26,#10: Loading ldso > loader  | Capability support not > supported. > loader  | vmlinuz26,#10: Starting libld-l4.s.so at 00013890 > via 0000cc70 > l4lx    | ======> L4Linux 2.6 starting... > <======== > l4lx    | Linux version 2.6.19-l4 ( > root(a)dup.postech.ac.kr > ) (gcc version > 3.4.6) > l4lx    : #1 Wed Mar 14 15:44:36 KST > 2007 > l4lx    | Binary name: > vmlinuz26 > l4lx    | Kernel command line (2 args): mem=128M > root=/dev/hda1 > l4lx    | Image: 00400000 - 0078e000 [3640 > KiB]. > l4lx    | Areas: Text:     00400000 > - 00695000 [2644kB] (a bit longer) > l4lx    > |        Data:     > 00695000 - 006e308c [312kB] > l4lx    > |        Initdata: 006e6000 - 00720000 > [232kB] > l4lx    |        > BSS:      00722000 - 0078c460 > [425kB] > l4lx    | l4lx_thread_create: Created thread 10.03 > (tamer) > l4lx    | Using tamed mode. > l4lx    > | l4lx_thread_create: Created thread 10.04 (server) > l4lx    | > main thread will be 10.04 > l4lx    | > l4env_register_pointer_section: addr = 00695000 size = > 573440 > l4lx    |      sec-w-init: > virt: 0x00695000 to 0x00720fff [560 KiB] > l4lx    | > Noncontiguous region for sec-w-init > l4lx    > |      sec-w-init: Number of physical regions: 2, > 573440 Bytes > l4lx    |      > sec-w-init: 1: Phys: 0x002e3000 to 0x00307000, Size:   > 147456 > l4lx    |      sec-w-init: 2: > Phys: 0x01498000 to 0x01500000, Size:   > 425984 > 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: > 128MB > l4lx    |     Main memory: virt: > 0x00800000 to 0x087fffff [131072 KiB] > l4lx    > |     Main memory: Number of physical regions: 1, 134217728 > Bytes > l4lx    |     Main memory: 1: Phys: > 0x74000000 to 0x7c000000, Size: 134217728 > l4lx    | Filling > lower ptabs... > l4lx    | Done (1006 > entries). > l4lx    | l4lx_thread_create: Created thread 10.05 > (timer.i0) > l4lx    | l4lx_thread_create: Created thread 10.06 > (Idler) > l4lx    | Starting L4FB via > CON > con     | vc_loop(): vc[2] running as > D.09 > l4lx    | l4lx_thread_create: Created thread 10.07 > (L4ConInput) > con     | vc_open_out(): vc[2] > 1024x768@16 > , gmode:0x35 > l4lx    > | l4fbcon: 1024x750 2bypp, size: 1540096 > l4lx    | > l4lx_thread_create: Created thread 10.08 (CON > refresher) > l4lx    | l4lx_thread_create: Created thread 10.09 > (IRQ14) > l4lx    | l4lx_thread_create: Created thread 10.0a > (IRQ15) > l4lx    | Terminating L4Linux. > simplets| Exit > 10.02 > con     | switch_vc(): switch to vc 01 > > >   > > > ----------------------------------l4linux configuration > > > # > # Automatically generated make config: don't edit > # Linux kernel > version: 2.6.19-l4 > # Wed Mar 14 15:38:44 2007 > # > > > # > # L4Linux > configuration > # > CONFIG_L4=y > CONFIG_L4_LINUX=y > CONFIG_L4_OBJ_TREE="/home/OrgL4/build_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_L4ENV_MEMSIZE=32 > CONFIG_L4_TAMED=y > > > # > # L4 build options > # > CONFIG_L4_MK_CPU_X86="586" > > > # > # IRQ Handling > # > CONFIG_L4_IRQ_SINGLE=y > # CONFIG_L4_IRQ_OMEGA0 > is not set > # CONFIG_L4_IRQ_MULTI is not set > > > # > # Stub drivers > # > CONFIG_L4_EXTERNAL_RTC=y > # CONFIG_L4_BLK_DRV > is not set > # CONFIG_L4_PDSPBLK_DRV is not > set > CONFIG_L4_FB_DRIVER=y > CONFIG_L4_FB_DRIVER_XF86IF=y > # > CONFIG_L4_OSHKOSH_DRV is not set > # CONFIG_L4_ORE_DRV is not > set > CONFIG_L4_SERIAL=y > CONFIG_L4_SERIAL_CONSOLE=y > # 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 > > > # > # Debugging options > # > # CONFIG_L4_DEBUG is not set > > > # > # Monitoring options (ferret) > # > # CONFIG_L4_FERRET_USER is not > set > # CONFIG_L4_FERRET_KERNEL is not set > # > CONFIG_L4_FERRET_SYSCALL_COUNTER is not set > > > # > # > > # > CONFIG_X86_32=y > CONFIG_GENERIC_TIME=y > CONFIG_LOCKDEP_SUPPORT=y > CONFIG_STACKTRACE_SUPPORT=y > CONFIG_SEMAPHORE_SLEEPERS=y > CONFIG_X86=y > CONFIG_MMU=y > CONFIG_GENERIC_ISA_DMA=y > CONFIG_GENERIC_IOMAP=y > CONFIG_GENERIC_HWEIGHT=y > CONFIG_ARCH_MAY_HAVE_PC_FDC=y > CONFIG_DMI=y > CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" > > > # > # Code maturity level > options > # > CONFIG_EXPERIMENTAL=y > CONFIG_BROKEN_ON_SMP=y > CONFIG_INIT_ENV_ARG_LIMIT=32 > > > # > # General > setup > # > CONFIG_LOCALVERSION="" > CONFIG_LOCALVERSION_AUTO=y > CONFIG_SWAP=y > CONFIG_SYSVIPC=y > # > CONFIG_IPC_NS is not set > CONFIG_POSIX_MQUEUE=y > # CONFIG_BSD_PROCESS_ACCT > is not set > # CONFIG_TASKSTATS is not set > # CONFIG_UTS_NS is not set > # > CONFIG_AUDIT is not set > # CONFIG_IKCONFIG is not set > # CONFIG_RELAY is not > set > CONFIG_INITRAMFS_SOURCE="" > # CONFIG_CC_OPTIMIZE_FOR_SIZE is not > set > CONFIG_SYSCTL=y > CONFIG_EMBEDDED=y > CONFIG_UID16=y > CONFIG_SYSCTL_SYSCALL=y > CONFIG_KALLSYMS=y > # > CONFIG_KALLSYMS_ALL is not set > # CONFIG_KALLSYMS_EXTRA_PASS is not set > # > CONFIG_HOTPLUG is not > set > CONFIG_PRINTK=y > CONFIG_BUG=y > CONFIG_ELF_CORE=y > CONFIG_BASE_FULL=y > CONFIG_FUTEX=y > CONFIG_EPOLL=y > CONFIG_SHMEM=y > CONFIG_SLAB=y > CONFIG_VM_EVENT_COUNTERS=y > CONFIG_RT_MUTEXES=y > # > CONFIG_TINY_SHMEM is not set > CONFIG_BASE_SMALL=0 > # CONFIG_SLOB is not > set > > > # > # Loadable module support > # > CONFIG_MODULES=y > # > CONFIG_MODULE_UNLOAD is not set > CONFIG_MODVERSIONS=y > # > CONFIG_MODULE_SRCVERSION_ALL is not set > CONFIG_KMOD=y > > > # > # Block layer > # > CONFIG_BLOCK=y > # CONFIG_LBD is not set > # > CONFIG_BLK_DEV_IO_TRACE is not set > # CONFIG_LSF is not set > > > # > # IO > Schedulers > # > CONFIG_IOSCHED_NOOP=y > CONFIG_IOSCHED_AS=y > CONFIG_IOSCHED_DEADLINE=y > CONFIG_IOSCHED_CFQ=y > CONFIG_DEFAULT_AS=y > # > CONFIG_DEFAULT_DEADLINE is not set > # CONFIG_DEFAULT_CFQ is not set > # > CONFIG_DEFAULT_NOOP is not set > CONFIG_DEFAULT_IOSCHED="anticipatory" > > > # > # Processor type and features > # > # CONFIG_SMP is not > set > 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_MGEODE_LX 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_CMPXCHG64=y > CONFIG_X86_ALIGNMENT_16=y > CONFIG_X86_TSC=y > # > CONFIG_HPET_TIMER 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_MCE is not set > # CONFIG_VM86 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_DELL_RBU > is not set > # CONFIG_DCDBAS is not set > CONFIG_NOHIGHMEM=y > # > CONFIG_HIGHMEM4G is not set > # CONFIG_HIGHMEM64G is not > set > CONFIG_VMSPLIT_3G=y > # CONFIG_VMSPLIT_3G_OPT is not set > # > CONFIG_VMSPLIT_2G is not set > # CONFIG_VMSPLIT_1G is not > set > CONFIG_PAGE_OFFSET=0xC0000000 > CONFIG_ARCH_FLATMEM_ENABLE=y > CONFIG_ARCH_SPARSEMEM_ENABLE=y > CONFIG_ARCH_SELECT_MEMORY_MODEL=y > CONFIG_ARCH_POPULATES_NODE_MAP=y > 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_SPARSEMEM_STATIC=y > CONFIG_SPLIT_PTLOCK_CPUS=4 > # > CONFIG_RESOURCES_64BIT is not set > # 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 > CONFIG_COMPAT_VDSO=y > > > # > # Power management options (ACPI, APM) > # > # CONFIG_PM is not > set > > > # > # ACPI (Advanced Configuration and Power Interface) Support > # > # > CONFIG_ACPI 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_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 > # > > > # > # PCI Hotplug Support > # > > > # > # Executable file > formats > # > CONFIG_BINFMT_ELF=y > CONFIG_BINFMT_AOUT=y > CONFIG_BINFMT_MISC=y > > > # > # Networking > # > CONFIG_NET=y > > > # > # Networking options > # > # CONFIG_NETDEBUG is not > set > CONFIG_PACKET=y > # CONFIG_PACKET_MMAP is not > set > CONFIG_UNIX=y > CONFIG_XFRM=y > # CONFIG_XFRM_USER is not set > # > CONFIG_XFRM_SUB_POLICY is not set > # 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_XFRM_TUNNEL is not set > # CONFIG_INET_TUNNEL is not set > # > CONFIG_INET_XFRM_MODE_TRANSPORT is not set > # CONFIG_INET_XFRM_MODE_TUNNEL is > not > set > CONFIG_INET_XFRM_MODE_BEET=y > CONFIG_INET_DIAG=y > CONFIG_INET_TCP_DIAG=y > # > CONFIG_TCP_CONG_ADVANCED is not > set > CONFIG_TCP_CONG_CUBIC=y > CONFIG_DEFAULT_TCP_CONG="cubic" > # > CONFIG_IPV6 is not set > # CONFIG_INET6_XFRM_TUNNEL is not set > # > CONFIG_INET6_TUNNEL is not set > # CONFIG_NETWORK_SECMARK is not set > # > CONFIG_NETFILTER is not set > > > # > # DCCP Configuration (EXPERIMENTAL) > # > # CONFIG_IP_DCCP is not > set > > > # > # SCTP Configuration (EXPERIMENTAL) > # > # CONFIG_IP_SCTP is not > set > > > # > # TIPC Configuration (EXPERIMENTAL) > # > # CONFIG_TIPC 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_ECONET is not set > # > CONFIG_WAN_ROUTER is not set > > > # > # QoS and/or fair queueing > # > # CONFIG_NET_SCHED 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 > # CONFIG_IEEE80211 is not set > > > # > # Device Drivers > # > > > # > # Generic Driver > Options > # > CONFIG_STANDALONE=y > CONFIG_PREVENT_FIRMWARE_BUILD=y > # > CONFIG_DEBUG_DRIVER is not set > # CONFIG_SYS_HYPERVISOR is not set > > > # > # Connector - unified userspace <-> kernelspace linker > # > # > CONFIG_CONNECTOR is not set > Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

How many tasks can be started?
by Daniel Vandersee 15 Mar '07

15 Mar '07

Hi there, can you tell me how many Tasks can be started from L4? As the task id has 11 bit, the theoretical maximum seems to be 2048, but if I configure simple_ts to use 246 tasks, I can't create a new task without using simple_ts (I use rmgr_get_task and rmgr_task_new). In this case the first free task number is 256. The task creation via rmgr_task_new seems to work (a valid task id is returned), but it seems that I can't serve the first page fault. If I serve it with an fpage, I immediately get the same page fault again and again. With simple_ts configured to 245 tasks everything works fine. Regards, Daniel

2 2

Build problems (with automake version)
by Igor Shmukler 08 Mar '07

08 Mar '07

Hello, I am having problems with CVS version of L4 not building due automake version error. Please advise. Error pasted below: ./bootstrap: ERROR: `automake' is too old. automake (GNU automake) 1.10 Written by Tom Tromey <tromey(a)redhat.com> and Alexandre Duret-Lutz <adl(a)gnu.org>. Copyright 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (version 1.9 or newer is required) ./bootstrap: ERROR: `aclocal' is too old. aclocal (GNU automake) 1.10 Written by Tom Tromey <tromey(a)redhat.com> and Alexandre Duret-Lutz <adl(a)gnu.org>. Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (version 1.9 or newer is required) make[2]: *** [GNUmakefile] Error 1 make[2]: Leaving directory `/home/ubuntu/l4-devel/l4/tool/dice' make[1]: *** [dice] Error 2 make[1]: Leaving directory `/home/ubuntu/l4-devel/l4/tool' make: *** [tool] Error 2 ubuntu@ubuntu:~/l4-devel/l4$

3 10

minor makefile error in examples
by Igor Shmukler 08 Mar '07

08 Mar '07

This one is minor, but i think it's nor imaginary - makefile does not make a symlink or something. I'll just copy the file. make[5]: Entering directory `/home/ubuntu/l4-devel/build/pkg/loader/examples/fprov-l4/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/ubuntu/l4-devel/l4/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -c -DRAM_BASE=0x0 -DUSE_UCLIBC=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/ubuntu/l4-devel/build/pkg/loader/idl/OBJ-x86-l4v2 -I/home/ubuntu/l4-devel/build/include/x86/l4v2 -I/home/drops/include/x86/l4v2 -I/home/ubuntu/l4-devel/build/include/l4v2 -I/home/drops/include/l4v2 -I/home/ubuntu/l4-devel/build/include/x86 -I/home/drops/include/x86 -I/home/ubuntu/l4-devel/l4/tool/dice/include -I/home/ubuntu/l4-devel/build/include -I/home/drops/include -I/usr/lib/gcc-lib/i486-linux-gnu/3.3.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common /home/ubuntu/l4-devel/l4/pkg/loader/examples/fprov-l4/main.c -o main.o /home/ubuntu/l4-devel/l4/pkg/loader/examples/fprov-l4/main.c:22:18: zlib.h: No such file or directory

2 1

and now linking problems
by Igor Shmukler 08 Mar '07

08 Mar '07

Hello, First, I would like to thank Ronald, Michael, Adam and everyone else for helping me to get started. I have another problem. This time it's linking issue. I was compiling with gcc 3.3. Please advise: --- -e ... Making gdb_copy.o -e ... Making gdb_pc_com_intr.o -e ==> Archiving into libkern.a -e ==> Linking kernel.image thread-log.o: In function `sys_ipc_log_wrapper': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:65: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' main-ia32-amd64.o: In function `main_arch()': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/main-ia32-amd64.cpp:112: undefined reference to `__stack_chk_fail' cpu-common.o: In function `Cpu::show_cache_tlb_info(char const*)': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:(.initcall.text+0x381): undefined reference to `__stack_chk_fail' cpu-common.o:/home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:892: more undefined references to `__stack_chk_fail' follow make[4]: *** [kernel.image] Error 1 make[4]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build' make[2]: *** [build] Error 2 make[2]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel' make: *** [kernel] Error 2 ubuntu@ubuntu:~/l4-devel/l4$ ---

3 4

Can I use L4/Fiasco in Dual Core CPU ?
by chenggh 08 Mar '07

08 Mar '07

Hi: Now I have a machine with dual core cpu of Athlon. I want to know if I could boot L4/Fiasco in dual core cpu and if there is some optimization of L4/Fiasco for dual core cpu. Thanks. cheng

2 1

[BUG] Deadlock in Fiasco kernel
by Daniel Vandersee 06 Mar '07

06 Mar '07

Hi there, I noticed that the Fiasco kernel hangs under some circumstances so the whole system stops working. Unfortunately I wasn't even able to enter the kernel debugger via a serial cable in this case. The error is reproducible on different plattforms (e.g. Thinkpad T43, 1GB RAM, Pentium M 1.8 GHz or Thinkpad T41) even though it only appears from time to time (probability ~50% or even better). Within VMWare or Qemu this deadlock does *not* appear. Furthermore this error does not occur if the kernel was started using the "-esc" option. I wasn't able to reproduce this bug on a HP nx7400 (Dual Core T2300, 1GB RAM). We use an own dynamic loader to load some L4 tasks whereas other L4 tasks, as the mGUI, are loaded by GRUB. The bug can be reproduced on real hardware using the iso-image which I will upload to the SLOX server (deadlock.iso). You have to choose GRUB entry two or three. If the error occurs the system hangs in text mode otherwise a graphical mode is entered. Sometimes you have to reboot up to 20 times but it usually occurs immediately. Kind regards Daniel

3 2

DROPS and vbeset 0x117
by Igor Shmukler 05 Mar '07

05 Mar '07

I tried running DROPS demo CD on VMWare Server 1.0. I am getting an error on vbeset 0x117. I guess there is no VESA support in server or something like that. Should I just try using the Free Player to run the demo? Thank you in advance.

3 3

Problem booting l4linux
by Eduard Benes 28 Feb '07

28 Feb '07

Hi all, I'm newbie in this area, and I would like to ask for help with some problems I run into (hope this is the right place). I've finally build l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". (please let me know if there is better document to start with) dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. I had some problem finding out the right configuration of the l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). Right now I'm trying to run it on real hw (How to make it run under qemu?) but when I try to boot DOpE using patched grub, it hangs when (at least I assume) trying to enter graphic mode. The screen shows this: [VESA 2.0 info @ 0x75b5000, 0x2ff bytes] boot <blank> I've tried the L4Linux demo CD, but with the same result. Tried to boot into DOpE or console. I suspect that video card might not be supported. But during many attempts, once the DOpE environment flashed for a second (before doing the restart routine accidentally) and that really surprise for me. The graphical user interface is not necessary, but I don't know yet how to run L4Linux in console. I'm able to get into kernel debugger, when I boot the L4Linux by remote serial console variant of grub menu.lst entries (based on the kickstart document mentioned above). In the kernel debugger mode was logged one error: [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): Error: Missing 'deceit_bit_disables_switch' kernel feature! Startup: semaphore lib initialization failed (-1)! It is probably not related to the problem with video card, but might show some mistakes in my l4linux-2.6 kernel configuration. Here is my PCI device list: $ lspci 00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge (rev 02) 00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge 00:13.0 USB Controller: ATI Technologies Inc OHCI USB Controller #1 (rev 01) 00:13.1 USB Controller: ATI Technologies Inc OHCI USB Controller #2 (rev 01) 00:14.0 SMBus: ATI Technologies Inc ATI SMBus (rev 16) 00:14.1 IDE interface: ATI Technologies Inc ATI Dual Channel Bus Master PCI IDE Controller 00:14.3 ISA bridge: ATI Technologies Inc Unknown device 434c 00:14.4 PCI bridge: ATI Technologies Inc Unknown device 4342 00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller 00:14.6 Modem: ATI Technologies Inc IXP AC'97 Modem (rev 01) 01:05.0 VGA compatible controller: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP] 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) 02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01) 02:07.0 USB Controller: NEC Corporation USB (rev 43) 02:07.1 USB Controller: NEC Corporation USB (rev 43) 02:07.2 USB Controller: NEC Corporation USB 2.0 (rev 04) My final goal is to compare performance of L4Linux and native Linux on real hw. I will appreciate any suggestions or study literature on this topic. Other questions I would like to ask: What is the right way to boot from serial console? How can be achieved networking under L4Linux? Regards, Eduard Benes

2 1

RE: Learning and Hacking L4 - My Bookshelf
by Stitt, Michael (AGRE) 28 Feb '07

28 Feb '07

Hi Jeff, Being in a similar boat, I don't have a good answer for you. But here's a copy (in semi-alphabetical order) of my L4 bookshelf and links to the other bookshelves I know about. Maybe you've found these already. -Hope this helps -Mike ++++L4 - My Bookshelves L4 eXperimental Kernel Reference Manual - (Karlsruhe) - Version X.2, Revision 5 - June 4 2004 http://l4ka.org/projects/pistachio/l4-x2-r5.pdf L4 User Manual - NICTA L4-embedded API - Ihor Kuz - Document Version 1.11 of October 5, 2005 http://www.ertos.nicta.com.au/software/kenge/pistachio/latest/userman.pdf L4Ka::Pistachio PowerPC Implementation Revision: 1.9 - Joshua LeVasseur - Karlsruhe http://l4ka.org/projects/pistachio/powerpc/ppc.pdf NICTA L4-embedded Kernel Reference Manual Version NICTA N1, Revision 5 http://www.ertos.nicta.com.au/software/kenge/pistachio/latest/refman.pdf On Micro-Kernel Contruction - Jochen Liedke - Karlsruhe - 15th ACM Symposium on Operating System Principles (SOSP) December 3-6, Copper Mountain Resort, Colorado http://www.l4ka.org/publications/1995/ukernel-construction.pdf Real-Time Programming and L4 Microkernels - Sergio Ruocco - NICTA - UNSW - 2007 http://www.ertos.nicta.com.au/publications/papers/Ruocco_06.abstract.pml Towards Real Microkernels - Jochen Liedke - Karlsruhe - September 1996/Vol. 39, No. 9 Communications of the ACM http://i30www.ira.uka.de/research/documents/l4ka/towards-ukernels.pdf ++++L4 - Other Bookshelves Dresden L4 Developer's Bibliography http://os.inf.tu-dresden.de/L4/bib.html Karlsruhe L4Ka Publications - OR - Karlsruhe System Architecture Group L4ka Publications http://www.l4ka.org/publications/ - OR - http://i30www.ira.uka.de/research/publications/l4ka/index.php?lid=en NICTA ERTOS Publications http://www.ertos.nicta.com.au/publications/ Teaching material from University of Karlsruhe http://i30www.ira.uka.de/teaching/courses/lecture.php?courseid=130 Teaching material from University of New South Wales http://www.cse.unsw.edu.au/~cs9242/06/lectures/ -----Original Message----- From: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] On Behalf Of Jeff Douglas Sent: Tuesday, February 27, 2007 11:29 AM To: l4-hackers(a)os.inf.tu-dresden.de Subject: Learning and Hacking L4 Hi Coly, I've read through the X.2 spec and some of the other papers that looked like they might be useful. Unfortunately, they are not really helpful to me. Or, perhaps it is better to say that they don't seem to paint a full picture. What I think would really be helpful is the L4 System Programmer's Manual. I've waited for it to materialize for years now, but it still hasn't appeared. Do you have any particular papers to suggest? Does you know if/when the System Programmer's Manual will be released? Regards, JD >Jeff: >hi, do you read some papers for L4 ? Maybe you can start from reading >these papers. > >Coly > >在 2007-02-27二的 22:36 +0900，Jeff Douglas写道： > Greetings, > > I have had some interest in os development and theory for quite some > time now, and a particular interest in L4. I'm a newbie, but I've read > through a lot, and have done some os programming for fun in the past. > > My question is: what is your advice on learning and hacking L4? > > I've read through quite a bit of the documentation, but reading > through specs does not seem like a good way to really understand; it > seems like too much to digest at once. And of course, the purpose of a > specification is to specify, not explain. I've browsed through source > code, but that is even worse. > > I'm sorry if my question is overly broad, but I'd appreciate any > advice that anyone can spare. > > Regards, > JD > > _______________________________________________ > l4-hackers mailing list > l4-hackers at os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ______________________________________________________________________ CAUTION: This message was sent via the Public Internet and its authenticity cannot be guaranteed. ______________________________________________________ ************************************************ The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ************************************************

3 2

Re: Problem booting l4linux
by chenggh 28 Feb '07

28 Feb '07

On Wednesday 28 February 2007 11:12, Eduard Benes wrote: > Hi all, > > I'm newbie in this area, and I would like to ask for help with some > problems I run into (hope this is the right place). I've finally build > l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". > (please let me know if there is better document to start with) > dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. We have tested this document many times and some Linux newbie used this document to build the L4Linux very successfully. And please pay attention that this document is made in the case of kernel 2.6.17. Maybe in the kernel 2.6.19 there are some problems, too. > I had some problem finding out the right configuration of the > l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). > Right now I'm trying to run it on real hw (How to make it run under qemu?) > but when I try to boot DOpE using patched grub, it hangs when (at least I > assume) trying to enter graphic mode. The screen shows this: If you use L4Linux or Fiasco the first thing is to study how to use serial console to debug the Fiasco especially in the graphical mode you don't see anything important in the screen. Some booting error messages could only be output by the serial console. > I've tried the L4Linux demo CD, but with the same result. Tried to boot > into DOpE or console. I suspect that video card might not be supported. But > during many attempts, once the DOpE environment flashed for a second > (before doing the restart routine accidentally) and that really surprise > for me. The graphical user interface is not necessary, but I don't know yet > how to run L4Linux in console. I'm able to get into kernel debugger, when I > boot the L4Linux by remote serial console variant of grub menu.lst entries > (based on the kickstart document mentioned above). In the kernel debugger > mode was logged one error: > [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): > Error: Missing 'deceit_bit_disables_switch' kernel feature! > Startup: semaphore lib initialization failed (-1)! > It is probably not related to the problem with video card, but might show > some mistakes in my l4linux-2.6 kernel configuration. > If you still have some problems about compiling or booting, please download this tar ball (http://dslab.lzu.edu.cn/~chenggh/doc/L4.tar). I have tested this tar ball many times successfully and if you use this directory and do as the kickstart says. I promise you could be successful. In this letter there are 2 attachments: one is 2.4.17 configuration file for booting from serial console and another is 2.4.17 configuration file for booting from Dope. > My final goal is to compare performance of L4Linux and native Linux on real > hw. I will appreciate any suggestions or study literature on this topic. I have done some similar work as you want to do and if you want know something about my paper and data please access my home page (dslab.lzu.edu.cn/~chenggh). > Other questions I would like to ask: > What is the right way to boot from serial console? Please review my kickstart and some configuration file. > How can be achieved networking under L4Linux? In my benchmark about performance comparasion between L4Linux and Linux I use L4Linux network (It is same as you do in Linux). But if you want to use Fiasco network there is a module ORe (the Oshkosh Resurrection) you could try. But I think this module only show us the Fiasco supports network, too and you don't do anything meaningful. Thank you. I hope you could modify my kickstart and give the new version of this kickstart. Thank you. cheng

1 0

Learning and Hacking L4
by Jeff Douglas 27 Feb '07

27 Feb '07

Hi Coly, I've read through the X.2 spec and some of the other papers that looked like they might be useful. Unfortunately, they are not really helpful to me. Or, perhaps it is better to say that they don't seem to paint a full picture. What I think would really be helpful is the L4 System Programmer's Manual. I've waited for it to materialize for years now, but it still hasn't appeared. Do you have any particular papers to suggest? Does you know if/when the System Programmer's Manual will be released? Regards, JD >Jeff: >hi, do you read some papers for L4 ? Maybe you can start from reading >these papers. > >Coly > >在 2007-02-27二的 22:36 +0900，Jeff Douglas写道： > Greetings, > > I have had some interest in os development and theory for quite some > time now, and a particular interest in L4. I'm a newbie, but I've read > through a lot, and have done some os programming for fun in the past. > > My question is: what is your advice on learning and hacking L4? > > I've read through quite a bit of the documentation, but reading > through specs does not seem like a good way to really understand; it > seems like too much to digest at once. And of course, the purpose of a > specification is to specify, not explain. I've browsed through source > code, but that is even worse. > > I'm sorry if my question is overly broad, but I'd appreciate any > advice that anyone can spare. > > Regards, > JD > > _______________________________________________ > l4-hackers mailing list > l4-hackers at os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

3 2

Learning and Hacking L4
by Jeff Douglas 27 Feb '07

27 Feb '07

Greetings, I have had some interest in os development and theory for quite some time now, and a particular interest in L4. I'm a newbie, but I've read through a lot, and have done some os programming for fun in the past. My question is: what is your advice on learning and hacking L4? I've read through quite a bit of the documentation, but reading through specs does not seem like a good way to really understand; it seems like too much to digest at once. And of course, the purpose of a specification is to specify, not explain. I've browsed through source code, but that is even worse. I'm sorry if my question is overly broad, but I'd appreciate any advice that anyone can spare. Regards, JD

2 1

IPC problem
by Michael Scheibel 16 Feb '07

16 Feb '07

Hello L4 hackers, we've encountered a problem with an IPC transmission based on DICE stubs generated from the following interface definition: UInt32 process( [in, size_is(bufferALen), max_is(MAX_BUFFER_SIZE)] UInt8* bufferA, [in] UInt32 bufferALen, [in, size_is(bufferBLen), max_is(MAX_BUFFER_SIZE)] UInt8* bufferB , [in] UInt32 bufferBLen, [out, size_is(*bufferCLen), max_is(MAX_BUFFER_SIZE)] UInt8** bufferC, [out] UInt32* bufferCLen); UInt8 is defined as unsigned char, UInt32 is defined as unsigned long, MAX_BUFFER_SIZE is 1500. We are using dice version 3.1.0 with the command line options -fforce-corba-alloc -nostdinc -P-DL4API_l4v2 and the latest OTC snapshot. In this configuration bufferB is not transmitted correctly but is received as corrupt data on the server side (which is an L4Linux application). Is there anything wrong with our interface definition? Any hints appreciated! Michael -- Sirrix AG security technologies - http://www.sirrix.com 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 message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 4

small address-space can not be used in em64t mode ?
by coly 14 Feb '07

14 Feb '07

Hi, The transparently flexing user address space method which is called as "small address-space" uses segment to implement the protection for small address sapce. But in em64t or amd64 mode, there is not segment (except FS,GS) exists. So it seems the small address-space method can not be used under 64bit mode. Isn't it ? Thanks in advance. Coly

2 1

Booting L4Linux on Fiasco-UX fails with kernel panic
by Michael Kasper 14 Feb '07

14 Feb '07

Hello L4-Hackers, I try to become familiar with L4Linux on top of Fiasco-UX. Therefor, I've rebuilt the sources as described online. But booting L4Linux with the example drops-rd.rd ramdisk fails with kernel panic. Shortly after the ramdisk is loaded, the boot process halts with the following message: Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye Has anyone a solution for this? Is the ramdisk not accessible by the L4Linux kernel, or do I need explicitly specify an init parameter? Thanks and kind regards, Michael ################################################# Fiasco-UX on Linux 2.6.18-gentoo-r6 (i686) Native Syscall Map: 0x600 Mapped 256 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00099364 [/base/drops/l4/build/bin/x86_586/l4v2/sigma0] Loading Module 0x00120000-0x002b29e4 [/base/drops/l4/build/bin/x86_586/l4v2/roottask] Copying Module 0x0ea5d000-0x0ea847ff [/base/drops/l4/kernel/fiasco/build/Symbols] Copying Module 0x0ea24000-0x0ea5cedc [/base/drops/l4/kernel/fiasco/build/Lines] Copying Module 0x0e9e4000-0x0ea2347e [/base/drops/l4/build/bin/x86_586/l4v2/names] Copying Module 0x0e9a7000-0x0e9e3dc8 [/base/drops/l4/build/bin/x86_586/l4v2/log] Copying Module 0x0e921000-0x0e9a63c7 [/base/drops/l4/build/bin/x86_586/l4v2/dm_phys] Copying Module 0x0e8d6000-0x0e92068d [/base/drops/l4/build/bin/x86_586/l4v2/simple_ts] Copying Module 0x0e822000-0x0e8d5804 [/base/drops/l4/build/bin/x86_586/l4v2/fuxfprov] Copying Module 0x0e7f0000-0x0e821f37 [/base/drops/l4/build/bin/x86_586/l4v2/rtc-ux] Copying Module 0x0e71e000-0x0e7ef395 [/base/drops/l4/build/bin/x86_586/l4v2/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: GenuineIntel (6:F:6:0) Model: Core 2 (Merom) at 2394 MHz 128 Entry I TLB (4K pages) 272 Entry D TLB (4K pages) 48 Entry D TLB (4M pages) 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 4096 KB L2 U Cache (16-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ ea99000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Found Fiasco-UX. Command line found: "/base/drops/l4/build/bin/x86_586/l4v2/roottask -symbols -lines" 261120kB ( 255MB) total RAM (reported by bootloader) 235040kB ( 230MB) received RAM from Sigma0 5488kB ( 6MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 A B C D E F ] Roottask: Loading 7 modules. #05: loading "/base/drops/l4/build/bin/x86_586/l4v2/names " from [0e9e4000-0ea2347e] to [002d0000-002d5f6a][002d6000-002e2000] entry at 0000d088 via trampoline page code #06: loading "/base/drops/l4/build/bin/x86_586/l4v2/log" from [0e9a7000-0e9e3dc8] to [00400000-004064ca][00407000-004398b0] entry at 0000e084 via trampoline page code #07: loading "/base/drops/l4/build/bin/x86_586/l4v2/dm_phys " from [0e921000-0e9a63c7] to [01500000-0150e50a][0150f000-01519000] entry at 0000f088 via trampoline page code #08: loading "/base/drops/l4/build/bin/x86_586/l4v2/simple_ts " from [0e8d6000-0e92068d] to [01400000-014080ea][01409000-0141b070] entry at 0001008c via trampoline page code #09: loading "/base/drops/l4/build/bin/x86_586/l4v2/fuxfprov" from [0e822000-0e8d5804] to [00500000-0051ec6c][0051f000-00553000] entry at 00011088 via trampoline page code #0a: loading "/base/drops/l4/build/bin/x86_586/l4v2/rtc-ux" from [0e7f0000-0e821f37] to [01080000-01084040][01085000-0108a000] entry at 00012088 via trampoline page code #0b: loading "/base/drops/l4/build/bin/x86_586/l4v2/loader /base/drops/l4/cfg/l4linux26.ux" from [0e71e000-0e7ef395] to [01300000-01320642][01321000-0134c000] entry at 000130a8 via trampoline page code simplets| Configured for 64 tasks. loader | Can't map tbuf status page fuxfprov| File provider started, registered as 9.02 fuxfprov| open "/base/drops/l4/cfg/l4linux26.ux" by B.02 loader | sleeping for 2000 ms fuxfprov| open "/base/drops/l4linux-2.6/vmlinuz26.ux" by B.02 loader | vmlinuz26.ux: Starting application using libld-l4.s.so loader | vmlinuz26.ux,#c: Loading binary fuxfprov| open "/base/drops/l4/build/bin/x86_586/l4v2/libld-l4.s.so" by B.02 loader | vmlinuz26.ux,#c: Loading ldso loader | Capability support not supported. loader | vmlinuz26.ux,#c: Starting libld-l4.s.so at 00013890 via 0000cf00 fuxfprov| open "./libloader.s.so" by C.00 fuxfprov| Can't open "./libloader.s.so": -2 fuxfprov| open "/base/drops/l4/build/bin/x86_586/l4v2/./libloader.s.so" by C.00 fuxfprov| open "/base/drops/l4linux-2.6/vmlinuz26.ux" by C.00 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.19-l4 (root@localhost) (gcc version 3.4.6 (Gentoo 3 l4lx : .4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #30 Wed Feb 14 15:53:39 Local tim l4lx : e zone must be set--see zic man l4lx | Binary name: /base/drops/l4linux-2.6/vmlinuz26.ux l4lx | Kernel command line (7 args): mem=128M root=1:0 load_ramdisk=1 ramdis l4lx : k_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de l4lx | Image: 00400000 - 0054e000 [1336 KiB]. l4lx | Areas: Text: 00400000 - 004cf000 [828kB] (a bit longer) l4lx | Data: 004cf000 - 004eb63c [113kB] l4lx | Initdata: 004ee000 - 00503000 [84kB] l4lx | BSS: 00504000 - 0054cd50 [291kB] l4lx | l4lx_thread_create: Created thread 0c.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0c.04 (server) l4lx | main thread will be 0c.04 l4lx | l4env_register_pointer_section: addr = 004cf000 size = 520192 l4lx | sec-w-init: virt: 0x004cf000 to 0x0054dfff [508 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 520192 Bytes l4lx | sec-w-init: 1: Phys: 0x0127d000 to 0x012f6000, Size: 495616 l4lx | sec-w-init: 2: Phys: 0x01356000 to 0x0135c000, Size: 24576 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 128MB l4lx | Main memory: virt: 0x00800000 to 0x087fffff [131072 KiB] l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x09800000, Size: 134217728 l4lx | Filling lower ptabs... l4lx | Done (1582 entries). l4lx | l4lx_thread_create: Created thread 0c.05 (timer.i0) Linux version 2.6.19-l4 (root@localhost) (gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #30 Wed Feb 14 15:53:39 Local time zone must be set--see zic man dm_phys: 0000000000800000 - 0000000008800000 [131072 KiB] (usable) 128MB memory available. Zone PFN ranges: DMA 0 -> 512 Normal 512 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 Allocating PCI resources starting at 10000000 (gap: 08800000:f7800000) Detected 2394.000 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: mem=128M root=1:0 load_ramdisk=1 ramdisk_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) l4lx_irq_timer_startup(0) timer_irq_thread: Starting timer IRQ thread. l4ser_init_ports l4ser: vkey_irq not set - input disabled! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 129620k/139264k available (729k kernel code, 1300k reserved, 211k data, 84k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0x10000000 - 0x18000000 ( 128 MB) lowmem : 0x00000000 - 0x08800000 ( 136 MB) .init : 0x004ee000 - 0x00503000 ( 84 kB) .data : 0x004b670c - 0x004eb63c ( 211 kB) .text : 0x00400000 - 0x004b670c ( 729 kB) Calibrating delay using timer specific routine.. 4680.80 BogoMIPS (lpj=23404042) Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K Compat vDSO mapped to 0040e000. CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz stepping 06 Setting up standard PCI resources fuse init (API version 7.7) L4 serial driver l4ser_init_ports l4ser: vkey_irq not set - input disabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye l4lx | panic: going to sleep forever, bye Time: tsc clocksource has been installed. ############################################### # # L4Linux26.ux # modpath "/base/drops/l4linux-2.6" libpath "/base/drops/l4/build/bin/x86_586/l4v2" sleep 2 task "/base/drops/l4linux-2.6/vmlinuz26.ux" "mem=128M root=1:0 load_ramdisk=1 ramdisk_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de" allow_cli all_sects_writable priority 0xA0 ############################################### # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_OBJ_TREE="/base/drops/l4/build" 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=y CONFIG_L4_L4ENV_MEMSIZE=128 CONFIG_L4_TAMED=y # # L4 build options # CONFIG_L4_MK_CPU_X86="586" # # IRQ Handling # # CONFIG_L4_IRQ_SINGLE is not set CONFIG_L4_IRQ_OMEGA0=y # CONFIG_L4_IRQ_MULTI is not set # # Stub drivers # CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set CONFIG_L4_SERIAL=y CONFIG_L4_SERIAL_CONSOLE=y # 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 # # Debugging options # CONFIG_L4_DEBUG=y CONFIG_L4_DEBUG_REGISTER_NAMES=y CONFIG_L4_DEBUG_SEGFAULTS=y CONFIG_L4_DEBUG_STATS=y # CONFIG_L4_DEBUG_IRQ_WHEELS is not set CONFIG_L4_DEBUG_TAMED_COUNT_INTERRUPT_DISABLE=y # # Monitoring options (ferret) # # CONFIG_L4_FERRET_USER is not set # CONFIG_L4_FERRET_KERNEL is not set # CONFIG_L4_FERRET_SYSCALL_COUNTER is not set # # # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_UTS_NS is not set # CONFIG_IKCONFIG is not set # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_HOTPLUG is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # # CONFIG_BLOCK is not set # # Processor type and features # # CONFIG_SMP is not set 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=y # CONFIG_M586TSC is not set # 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_MGEODE_LX 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_CMPXCHG64=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER 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_MCE is not set CONFIG_VM86=y # 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_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_POPULATES_NODE_MAP=y 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_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set # 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 CONFIG_COMPAT_VDSO=y # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # # CONFIG_PCI is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_MISC=m # # Networking # # CONFIG_NET is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_SYS_HYPERVISOR is not set # # Connector - unified userspace <-> kernelspace linker # # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # # Misc devices # # CONFIG_TIFM_CORE is not set # # SCSI device support # # CONFIG_SCSI_NETLINK is not set # # Serial ATA (prod) and Parallel ATA (experimental) drivers # # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # I2O device support # # # ISDN subsystem # # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # # CONFIG_INPUT is not set # # Hardware I/O ports # # CONFIG_SERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # # CONFIG_VT is not set # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set # # 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 # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # # CONFIG_I2C is not set # # SPI support # # CONFIG_SPI is not set # CONFIG_SPI_MASTER is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # # CONFIG_HWMON is not set # CONFIG_HWMON_VID is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # # Graphics support # # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # # CONFIG_USB_ARCH_HAS_HCD is not set # CONFIG_USB_ARCH_HAS_OHCI is not set # CONFIG_USB_ARCH_HAS_EHCI is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # LED devices # # CONFIG_NEW_LEDS is not set # # LED drivers # # # LED Triggers # # # InfiniBand support # # # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) # # CONFIG_EDAC is not set # # Real Time Clock # # CONFIG_RTC_CLASS is not set # # DMA Engine support # # CONFIG_DMA_ENGINE is not set # # DMA Clients # # # DMA Devices # # # File systems # CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y CONFIG_FUSE_FS=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_CONFIGFS_FS is not set # # Miscellaneous filesystems # # # 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 # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=14 # CONFIG_DEBUG_BUGVERBOSE is not set # CONFIG_DEBUG_FS is not set # CONFIG_UNWIND_INFO is not set # CONFIG_HEADERS_CHECK is not set CONFIG_EARLY_PRINTK=y # CONFIG_DOUBLEFAULT is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_MANAGER=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=m CONFIG_CRYPTO_SHA256=m # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES 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_CRC16 is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_PLIST=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y

2 1

large memory model kernel
by David Shifflett 12 Feb '07

12 Feb '07

Hi, I am looking for a development and run-time environment for an experimental kernel. I want to run large memory model (multiple code and data segments). Can L4 / Fiasco support a segmented architecture? Can it support large memory model code? What file formats (ELF, COFF, LE/LX) does it support? What compiler/linker might work? (I am looking at Open WATCOM) Thanks in advance, dave

2 1

Problem compiling dice
by thbach＠students.uni-mainz.de 12 Feb '07

12 Feb '07

Hi, trying to compile the recent cvs-source I got the following error (both, with bison and byacc), while compiling dice: mv -f .deps/IncludeStatement.Tpo .deps/IncludeStatement.Po g++ -DHAVE_CONFIG_H -I. -I.. -D__USER__="\"knoppix@`hostname`\"" -D__L4DIR__="\"`pwd`/../../..\"" -D__DICEINCDIR__="\"/home/drops/include\"" -Wall -I../src -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -MT Exception.o -MD -MP -MF .deps/Exception.Tpo -c -o Exception.o Exception.cpp mv -f .deps/Exception.Tpo .deps/Exception.Po g++ -DHAVE_CONFIG_H -I. -I.. -D__USER__="\"knoppix@`hostname`\"" -D__L4DIR__="\"`pwd`/../../..\"" -D__DICEINCDIR__="\"/home/drops/include\"" -Wall -I../src -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -MT Dependency.o -MD -MP -MF .deps/Dependency.Tpo -c -o Dependency.o Dependency.cpp mv -f .deps/Dependency.Tpo .deps/Dependency.Po g++ -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -export-dynamic -o dice main.o Compiler.o CParser.o File.o Object.o Visitor.o version.o CCParser.o CCXXParser.o CDCEParser.o CCORBAParser.o CPreProcess.o IncludeStatement.o Exception.o Dependency.o -L../src/be/l4/v2 -lv2 -L../src/be/l4/v2/amd64 -lv2amd64 -L../src/be/l4/v2/ia32 -lv2ia32 -L../src/be/l4/x0 -lx0 -L../src/be/l4/v4 -lv4 -L../src/be/l4/v4/ia32 -lv4ia32 -L../src/be/l4 -ll4 -L../src/be/sock -lsock -L../src/be/cdr -lcdr -L../src/be -lbe -L../src/parser/dce -ldce -L../src/parser/corba -lcorba -L../src/parser/inc -linc -L../src/parser/gcc-c -lgcc_c -L../src/parser/gcc-cxx -lgcc_cxx -L../src/fe -lfe -lstdc++ -ldl collect2: ld returned 1 exit status make[6]: *** [dice] Fehler 1 make[6]: Leaving directory `/home/knoppix/l4/l4/tool/dice/src' make[5]: *** [all-recursive] Fehler 1 make[5]: Leaving directory `/home/knoppix/l4/l4/tool/dice/src' make[4]: *** [all-recursive] Fehler 1 make[4]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[3]: *** [all] Fehler 2 make[3]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[1]: *** [dice] Fehler 2 make[1]: Leaving directory `/home/knoppix/l4/l4/tool' make: *** [tool] Fehler 2 There was allready someone else having this problem in the mailing-list... Any suggestions? Greets, Vincent

2 4

Compile Error in L4 Environment
by WanKeun Jo 12 Feb '07

12 Feb '07

Hi, I've been using L4 packages and fiasco kernel for ARM platform. At this time, I changed my test bed, and made a new environment for L4. Using the same cross toolchain as before, I succeed to compile l4 packages and l4linux. However, when I tried to make a bootstrap image at "l4/build_user/pkg/bootstrap/server/src", the following error occured. The error doens't occur in the previous machine at all. ========================================================================================== ....omitted... Merging image /fiasco to mod00 cp: omitting directory `/fiasco' Use of uninitialized value in concatenation (.) or string at /home/jowkju/project/Microkernel/Latest/l4/pkg/bootstrap/server/src/build.pl line 198. mod00.extra.s: Assembler messages: mod00.extra.s:7: Warning: partial line at end of file ignored Merging image /home/jowkju/project/Microkernel/Latest/l4/build_user/bin/arm_pxa/l4x0/sigma0 to mod01 ....omitted... ==> Linking bootstrap.image LD_PRELOAD=/home/jowkju/project/Microkernel/Latest/l4/tool/gendep/libgendep.so GENDEP_TARGET=bootstrap.image GENDEP_BINARY=ld arm-linux-gcc -o bootstrap.image startup.o exec.o region.o module.o base_critical.o patch.o loader_mbi.o libc_support.o crt0.o init_kip_arm.o mbi_modules.bin mod00.bin mod01.bin mod02.bin mod03.bin mod04.bin mod05.bin mod06.bin mod07.bin mod08.bin mod09.bin mod10.bin mod11.bin mod12.bin mod13.bin mod14.bin mod15.bin -Ttext=0xa1400000 -L/home/jowkju/project/Microkernel/Latest/l4/build_user/lib/arm_pxa/l4x0 -L/home/jowkju/project/Microkernel/Latest/l4/lib/arm_pxa/l4x0 -L/home/jowkju/project/Microkernel/Latest/l4/build_user/lib/arm_pxa -L/home/jowkju/project/Microkernel/Latest/l4/lib/arm_pxa -L/home/jowkju/project/Microkernel/Latest/l4/build_user/lib -L/home/jowkju/project/Microkernel/Latest/l4/lib -Tbootstrap.ld -larm_drv-pxa -larm_uart -lcxx_base -lcxx_io -lcxx_io_kdebug -nostdlib -Wl,--nostdlib -ll4util -luc_c /opt/crosstool/gcc-3.4.4-glibc-2.2.5/arm-linux/lib/gcc/arm-linux/3.4.4/libgcc.a -Ttext=0xa1400000 -Wl,--warn-common mod00.bin(.module_info+0x0): undefined reference to `_binary_mod00_start' collect2: ld returned 1 exit status make[2]: *** [bootstrap.image] Error 1 ========================================================================================== To fix up the error, I also tried to use the same versions of the tools, which are thought to be related to the problem - gcc,g++, binutils, make, perl, flex, bison, byacc, automake - as before. But , the error not fixed.. Could you help me to use "l4" with the new machine?? Thank you...

2 1

IO Address Mapping
by WanKeun Jo 31 Jan '07

31 Jan '07

Hi, In the previous "sigma0" version, for IO Address mapping, we can add "static Region_instance< start physical address, size, > name;" and then "memmap.add_region &name)"; makes the region available. But now, sigma0 implementation is changed a lot. How can I make a IO Address Region and then add it to sigma0??

2 1

Compilation of Fiasco-1.2 quits...
by thbach＠students.uni-mainz.de 30 Jan '07

30 Jan '07

Hi, I just tried to compile fiasco-1.2 (from the tar-ball). After doing > cd fiasco-1.2/l4/kernel/fiasco > make BUILDDIR=build > cd build > make It quits the compilation with the following output: ... Making startup.o /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:71: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8 [222]’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:72: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8 [256]’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:80: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:81: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:92: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:93: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:94: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:95: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:96: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:97: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:98: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:99: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:100 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:103 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:104 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:105 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:106 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:107 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:108 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:109 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:110 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:111 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:120 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:121 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:122 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:123 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:124 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:125 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:126 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:127 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:128 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:129 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:132 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8 [189]’ auto/x86desc.h:34: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:35: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:44: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:45: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:46: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:47: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:54: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:55: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:63: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:64: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/timeout.h:42: error: extra qualification ‘Timeout::’ on member ‘get_first_timeout’ auto/kmem.h: In static member function ‘static volatile Address* Kmem::kernel_esp()’: auto/kmem.h:176: warning: dereferencing type-punned pointer will break strict-aliasing rules auto/kmem_alloc.h: At global scope: auto/kmem_alloc.h:19: error: extra qualification ‘Kmem_alloc::’ on member ‘Kmem_alloc’ auto/thread.h:84: error: extra qualification ‘Thread::’ on member ‘d_taskno’ auto/thread.h:90: error: extra qualification ‘Thread::’ on member ‘d_threadno’ auto/thread.h:129: error: extra qualification ‘Thread::’ on member ‘associate_irq’ auto/thread.h:130: error: extra qualification ‘Thread::’ on member ‘disassociate_irq’ auto/thread.h:140: error: extra qualification ‘Thread::’ on member ‘lookup’ auto/mapdb.h:64: warning: ‘packed’ attribute ignored for field of type ‘Mapping_entry’ make[2]: *** [startup.o] Fehler 1 make[2]: Leaving directory `/home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/build' make[1]: *** [all] Fehler 2 make[1]: Leaving directory `/home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/build' make: *** [all] Fehler 2 Does someone know how to fix this? I'm building on Debian etch (gcc version 4.1.2) with an Intel Pentium III.

2 1

L4Env DDE questions
by Igor Shmukler 29 Jan '07

29 Jan '07

Hello, I am working on a research project where we are trying to play with information flow between device drivers, and IO stack in general. We want to be able to break disk and network IO in pieces and glue it together as our needs require. From what I understood while going over KMB slides, it seems like L4Env might be an ideal platform for our experiments. However, I am not sure whether I understand how things work correctly. I was wondering if someone could answer some of my questions, to give me a little head start. When Linux drivers are reused, does everyone of these drivers run in its' own address space? Would "reused DDE" drivers still be isolated from one another? Thank you in advance, igor

2 1

[PATCH] L4Linux Ore fix
by Alexander Warg 29 Jan '07

29 Jan '07

No comment -- Alex

1 0

Problem with syscall 243.
by Jorge Cardona 21 Jan '07

21 Jan '07

Hi. I download form the svn of NICTA all the iguana-project--devel--1.2--version-0, and when it was finished, i type: scons machine=pc99 simulate, i also try with toolsuffix=-3.3 and toolsuffix=-4.0 after a moment of compilation it start to run on qemu an image with l4 kernel, iguana and wombat at the top but get's into an infinite loop of: syscall 243 init:1:e4001 unknown syscall I was searching and found that the problem it get solved building a crosscompiler, but it was on a Red Hat system, I'm using a Debian. Some info about my machine: ii libc5 5.4.46-15 The Linux C library version 5 (run-time libr ii libc6 2.3.6-9 GNU C Library: Shared libraries ii libc6-dev 2.3.6-9 GNU C Library: Development Libraries and Hea ii libc6-i686 2.3.6-9 GNU C Library: Shared libraries [i686 optimi ii libg++2.8.1.3-glibc2.2 2.95.4-27 The GNU C++ extension library - runtime vers ii libstdc++2.10-glibc2.2 2.95.4-27 The GNU stdc++ library $ gcc -print-file-name=libc.so.6 /lib/../lib/libc.so.6 $ gcc -print-file-name=ld-linux.so.2 /lib/../lib/ld-linux.so.2 I'm using Debian on testing. The complete log is: Booting 'L4 NICTA::Iguana' kernel=/boot/grub/kickstart [Multiboot-elf, <0x800000:0x6a98:0x0>, <0x808000:0x0:0x18a8>, shtab=0x80a258 , entry=0x800000] module=/boot/grub/l4kernel [Multiboot-module @ 0x821000, 0x19f295 bytes] module=/boot/grub/ig_server [Multiboot-module @ 0x9c1000, 0x58fde bytes] module=/boot/grub/ig_init [Multiboot-module @ 0xa1a000, 0x55344 bytes] module=/boot/grub/ig_serial [Multiboot-module @ 0xa70000, 0x4dae7 bytes] module=/boot/grub/ig_naming [Multiboot-module @ 0xabe000, 0x41798 bytes] module=/boot/grub/ig_trace [Multiboot-module @ 0xb00000, 0x4104a bytes] module=/boot/grub/ig_timer [Multiboot-module @ 0xb42000, 0x4701e bytes] module=/boot/grub/vmlinux [Multiboot-module @ 0xb8a000, 0x2cbc6c bytes] module=/boot/grub/ramdisk [Multiboot-module @ 0xe56000, 0x7d0000 bytes] module=/boot/grub/startup.script [Multiboot-module @ 0x1626000, 0x1f0 bytes] KickStart 0.13.0 Detected multiboot compliant loader Found an elf32 file called "kernel" located at address 0x00821000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x0000c0 0xf0100200 0x00100200 0x0a4ec 0x0a4ec RWE 0x0010 LOAD 0x00a800 0xf010c000 0x0010c000 0x111e0 0x111e0 RWE 0x0800 LOAD 0x01c000 0x0013e000 0x0013e000 0x0b03c 0x0b03c RWE 0x1000 segment 3 is not loadable, skipping Found an elf32 file called "roottask" located at address 0x009c1000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00150000 0x00150000 0x10032 0x131d0 RWE 0x1000 segment 1 is not loadable, skipping Loaded normal modules.. now the rest Found an elf32 file called "/boot/grub/ig_init" located at address 0x00a1a000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00170000 0x00170000 0x0e032 0x0e090 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_serial" located at address 0x00a70000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00180000 0x00180000 0x0c032 0x0c0a4 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_naming" located at address 0x00abe000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00190000 0x00190000 0x0a032 0x0a088 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_trace" located at address 0x00b00000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x001a0000 0x001a0000 0x0a032 0x0a088 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_timer" located at address 0x00b42000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x001b0000 0x001b0000 0x0b032 0x0b0ac RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/vmlinux" located at address 0x00b8a000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x001c0000 0x001c0000 0x1ec06c 0x20d0b8 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ramdisk" located at address 0x00e56000 Invalid elf file (-1) Magic is: 00 00 00 00 Found an elf32 file called "/boot/grub/startup.script" located at address 0x0162 6000 Invalid elf file (-1) Magic is: 23 20 49 67 Launching kernel ... NICTA::Pistachio - built on Jan 20 2007 15:57:48 by jorgee@mio using gcc version 3.3.6 (Debian 1:3.3.6-13). Initializing boot memory (f011e000 - f013e000) kmem_init (f011e000, f013e000) [128K] remap area f0100000->00100000 len=3e000, w=1, k=1, size=0 remap area 0013e000->0013e000 len=c000, w=1, k=1, size=0 remap area 00000000->00000000 len=400000, w=1, k=1, size=0 activate_gdt remap area f7000000->07000000 len=1000000, w=1, k=1, size=0 activate_gdt Registering processor 0 in KIP (0MHz, 0MHz) startup_system done domain pairs: (0, 1) Initialising scheduler... Switching to idle thread initial_switch_to:552: Initial switch to: sp = f0113ff8 system has 16 interrupts Initializing root servers root-servers: utcb_area: bf000110 (128KB), kip_area: bff000c0 (4KB) creating root server (000c0001) idle thread started ***************************************** * Iguana system, Copyright 1996-2004 * * ERTOS - National ICT Australia * ***************************************** Unknown type: 258 Iguana init starting Initialise naming: Initialise trace: Initialise timer: Initialise serial: Trace server starting no kernel tracebuffer found Backing memory section: 0x001be000 Backed memory section Driver enable Done driver enable Initial servers started Loading linux wombat is at <0x001c0000:0x003ce000> starting at 0x001c0000 Instance: 0x0500e868 -- server: dc001 objref: 1c0000 Loading eCos Couldn't find: ecos Linux version 2.6.10-i386l4_pc99 (jorgee@mio) (gcc version 4.0.4 20060507 (prere lease) (Debian 4.0.3-3)) #4 Sat Jan 20 16:00:03 COT 2007 Kernel memory ranges: 0: 0x03000000-0x04000000 (4096 pages) total 4096 pages Built 4 zonelists Kernel command line: vmlinux igms_name=ramdisk root=/dev/igms0 PID hash table entries: 128 (order: 7, 2048 bytes) Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 16088k/16400k available (1336k kernel code, 200k reserved, 332k data, 30 0k init) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) NET: Registered protocol family 16 PCI: direct init pci_direct_init: calling request_region(0xCF8, 8, "PCI conf1") pci_direct_init: request_region returned 0x0301fe60 calling pci_check_type1() PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: pcibios_fixup_bus : Limiting direct PCI/PCI transfers. PCI: PIIX3: Enabling Passive Release on 0000:00:01.0 Activating ISA DMA hang workarounds. RAM (4096 kB) at 0xxe0000000, Cirrus Logic chipset on PCI bus cirrusfb: Driver for Cirrus Logic based graphic boards, v2.0-pre2 igvfb alloc = 00020000 fb1: Virtual frame buffer device, using 75K of video memory io scheduler noop registered io scheduler anticipatory registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html eth0: RealTek RTL-8029 found at 0xc100, IRQ 10, 52:54:00:12:34:56. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hda: QEMU HARDDISK, ATA DISK drive hda: IRQ probe failed (0xffffffff) hdb: IRQ probe failed (0xffffffff) hdb: IRQ probe failed (0xffffffff) hdc: QEMU CD-ROM, ATAPI CD/DVD-ROM drive hdc: IRQ probe failed (0xffffffff) hdd: IRQ probe failed (0xffffffff) hdd: IRQ probe failed (0xffffffff) elevator: using anticipatory as default io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 88704 sectors (45 MB) w/256KiB Cache, CHS=88/255/63 hda: hda1 hdc: ATAPI 4X CD-ROM drive, 512kB Cache Uniform CD-ROM driver Revision: 3.20 igms0: unknown partition table NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Mounted root (ext2 filesystem) readonly. syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall What can i do to fix this? -- Jorge Eduardo Cardona jorgeecardona(a)gmail.com ------------------------------------------------ Linux registered user #391186 Registered machine #291871 ------------------------------------------------

1 0

GRUB and modaddr
by Manuel A. Fernandez Montecelo 17 Jan '07

17 Jan '07

Hello, If I understood it correctly (stumbling upon a memory overlapping error and searching the web), that 'modaddr' command (or similar name, don't have it around now) exists only in a fork of GRUB maintained to boot Fiasco (and maybe other Dresden/L4 projects). Is there a way to run Fiasco with standard GRUB, or any ongoing work to be able to do it? Regards. -- Manuel A. Fernandez Montecelo <manuel.montezelo(a)gmail.com>

5 6

Fiasco lazy-scheduling question
by eschierb＠sci.kun.nl 17 Jan '07

17 Jan '07

Hi, I'm Erik Schierboom and I study at the Radboud University Nijmegen. Right now, I'm writing my master thesis, under supervision of Hendrik Tews, on the formal verification of a part of Fiasco's IPC implementation. I studied the thesis by René Reusner but I don't fully grasp the lazy-scheduling details. I have the following questions. For one, the description says that the sender is not removed from the ready-list when the switch is made to the receiver (even though it is now in waiting status). However, as the sender is the active thread it is not part of the ready-list by definition (at least that is how I interpreted the system), so how could it be removed anyway? Secondly, the switching from sender to receiver is simply an execution context switch. If the receiver finishes before the sender's time is up, does the receiver switch the execution context back to that of the sender? With regards, Erik

2 1

Re: some problems of when compiling IDL with dice tools
by Ronald Aigner 17 Jan '07

17 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 CC'd to l4-hackers, so the most probable solution is in the archives :) chenggh wrote on 17.01.2007 12:04 this: > On Wednesday 17 January 2007 17:04, you wrote: >> chenggh wrote on 17.01.2007 04:52 this: >>> Hi: >>> In the idl file i defined an interface including a function declaration >>> like this: >>> int foo([in] arg1, [in] void *( * start_routine)(void *), [in] arg2); >>> >>> My aim is to define a method which includes a function pointer I define >>> the function name and function parameters by myself. But when I compile >>> there is error. >> Naturally. >> >>> I checked out the dice manual there is nothing about how to deal with >>> function pointer in idl file. Is this style supported by dice IDL ? If >>> it supports how could I do? >> No, don't do it! >> >> Dice is an IDL compiler. IDL stands for Interface Definition Language. >> And IDL is *NOT* the C programming language. Even though IDL looks >> similar to C it is not C. So using function pointers as arguments in an >> interface definition won't work. > > If I want to define a method including a function as a parameter in IDL file > how can I do? You will have to find another way of expressing a call-back function, e.g., using addresses which you convert into a function pointer wherever you want to invoke the function. You could write something like: int foo([in] arg1, [in] unsigned long * addr_func, [in] arg2); (unsigned long* is used here as the type describing a memory location) and then in the component function: /* I did not test this. Maybe it compiles and works, maybe it doesn't. */ foo_component(arg1, unsigned long * addr_func, arg2) { void *(*start_routine)(void*) = addr_func; ... start_routine(...); ... } However, you usually use IDL to describe an interface for a service that runs in a *different* address space. Sending a pointer to a function to that server is useless, because it has no access to that function located in the client's address space. Then again, if the function is located in a shared memory region you could do the above, but would have to "translate" the address from the client's address space location to the server's address space location. Or client and server are located in the same address space. Then you could use the method described above. Greetings, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFrg9m2sAx3Dtx9+YRApzmAJ92VK5ke3N1wfsLD7Aktp8cVhiR/QCggnS5 DU9EjVEN9u4A+bF9G6b7fSs= =9Noj -----END PGP SIGNATURE-----

1 0

Re: some problems of when compiling IDL with dice tools
by Bjoern Doebel 17 Jan '07

17 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 chenggh wrote: > On Wednesday 17 January 2007 15:44, you wrote: >> chenggh wrote: >>> Hi: >>> In the idl file i defined an interface including a function declaration >>> like this: >>> int foo([in] arg1, [in] void *( * start_routine)(void *), [in] arg2); >>> >>> My aim is to define a method which includes a function pointer I define >>> the function name and function parameters by myself. But when I compile >>> there is error. >>> >>> I checked out the dice manual there is nothing about how to deal with >>> function pointer in idl file. Is this style supported by dice IDL ? If >>> it supports how could I do? >> What exactly are you trying to do? > I try to encapsulate the pthread function with some l4 thread functions. In > Linux the pthread definition is like this: > int pthread_create (pthread_t *__restrict __threadp, > __const pthread_attr_t *__restrict __attr, > void *(*__start_routine) (void *), > void *__restrict __arg) __THROW; > So in IDL file I define the similar style but compilation has some errors. > Maybe I must consider other solutions. Why do you need an IDL interface for starting a thread? Can't this just be implemented as a C function? You can have a look at l4/pkg/thread to see how the L4 thread library is implemented. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrgu/P5ijxgQLUNkRAjUNAJ4h4VwnevgtTlxTXnYaz2s7/SwHoACfRjmj ExnO96FlWr/PL7I0fDYNRa8= =9dYs -----END PGP SIGNATURE-----

1 0

some problems of when compiling IDL with dice tools
by chenggh 17 Jan '07

17 Jan '07

Hi: In the idl file i defined an interface including a function declaration like this: int foo([in] arg1, [in] void *( * start_routine)(void *), [in] arg2); My aim is to define a method which includes a function pointer I define the function name and function parameters by myself. But when I compile there is error. I checked out the dice manual there is nothing about how to deal with function pointer in idl file. Is this style supported by dice IDL ? If it supports how could I do? Thanks. cheng

3 2

arm instruction version
by WanKeun Jo 17 Jan '07

17 Jan '07

Hi, In the l4linux-2.6, if set L4ARCH=arm, the processor type is fixed to CPU_SA1100. And the arm instruction version is armv4. I want to use arch-dependent code for pxa, so I changed CPU_SA1100 to CPU_XSCALE config and arm instruction set version to armv5te at --------------------------------------------------- $ l4linux-2.6/arch/l4/Makefile CFLAGS += -D__LINUX_ARM_ARCH__=5 -march=armv5te --------------------------------------------------- and found a code, --------------------------------------------------- $ l4linux-2.6/arch/l4/kernel/arch-arm/setup.c unsigned int processor_id = 0x0001f000; /* ARMv4 */ --------------------------------------------------- The processor_id is fixed to ARMv4 value. My question is 001. How processor_id affect the linux?? Should I also change this value to a armv5te value?? 002. If I have to change it, what is the proper value for armv5te?? I can't find the value anywhere. Thank you!!!

2 1

AW: Documentation for L4Linux/L4Env
by Christian, Martin, OPEE45 16 Jan '07

16 Jan '07

Hi Adam! > maybe the KMB lecture slides are somehow helpful. They are a good starting point to understand the principles. However the mapping to the code is still unclear. Wouldn't it be possible to get a student (HiWi) writing some documentation? > You should have some good understanding of Linux internals though Yes. And that's exactly my problem ... :-( > understand what the important code does. First understand what the important code is. > Besides that you can of course ask questions and I can try to answer them. >From your lecture I understand that a new architecture would require mainly changes to the "Lower Half" of L4Linux. But I suppose there are also changes required to the Syscall Interface. However, since I want to port it to another L4 Interface, I'll also have to rewrite a lot more. So I'm tending more to use either the L4Linux-2.4 (where there is no documentation) or Wombat, which at least builds on the L4.X2 API. Anyways, I fear I won't manage to do it within 6 weeks ... :-( Thanks for the help, Martin.

2 1

Re: Please help me to solve this problem of my application
by chenggh 15 Jan '07

15 Jan '07

Hi: Now the compilation is ok. But when I run this application there are some errors. This is my log: Fiasco-UX on Linux 2.6.15-23-386 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096964 [sigma0-ux] Loading Module 0x00120000-0x002bc9c4 [roottask] Copying Module 0x039a1000-0x039e0de8 [names] Copying Module 0x03965000-0x039a06d1 [log] Copying Module 0x038de000-0x03964162 [dm_phys] Copying Module 0x03854000-0x038ddee7 [clock] Copying Module 0x037cc000-0x03853750 [clk] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Mon Aug 28 08:34:51 2006 compiled with gcc 3.4.6 for AMD Athlon CPU: AuthenticAMD (6:8:1:0) Model: Duron (Applebred) at 1602 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 64 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: yes. Allocated 20kB for maintenance structures. Roottask. Found Fiasco-UX. Command line found: "roottask" 64512kB ( 63MB) total RAM (reported by bootloader) 55080kB ( 54MB) received RAM from Sigma0 3788kB ( 4MB) reserved RAM 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 ] Roottask: Loading 5 modules. #05: loading "names" from [039a1000-039e0de8] to [002d0000-002d614a][002d7000-002e3000] entry at 0000d060 via trampoline page code symbols at [039ee000-039f0000] (8kB), lines at [039e8000-039ee000] (24kB) #06: loading "log" from [03965000-039a06d1] to [00400000-00406c6a][00407000-00439850] entry at 0000e05c via trampoline page code symbols at [039e6000-039e8000] (8kB), lines at [039e0000-039e6000] (24kB) #07: loading "dm_phys" from [038de000-03964162] to [01500000-01511d6a][01512000-0151c000] entry at 0000f060 via trampoline page code symbols at [039db000-039e0000] (20kB), lines at [039ce000-039db000] (52kB) #08: loading "clock" from [03854000-038ddee7] to [01800000-01812bb4][01813000-01833000] entry at 00010060 via trampoline page code symbols at [039ca000-039ce000] (16kB), lines at [039ba000-039ca000] (64kB) #09: loading "clk" from [037cc000-03853750] to [01100000-011124d4][01113000-01133000] entry at 0001105c via trampoline page code symbols at [039b6000-039ba000] (16kB), lines at [039a7000-039b6000] (60kB) clock_s | L4RM: [PF] write at 0x00000000, ip 018001ac, src 8.02 clock_s | [8.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): clock_s | unhandled page fault The attachment is the source code, too. Thank you. cheng

2 1

Please help me to solve this problem of my application
by chenggh 13 Jan '07

13 Jan '07

Hi: I write a simple service for L4/Fiasco which encapsulate two methods. clock_gettime() and clock_nanosleep(). Of course now it doesn't not have full functions of these two methods. But when I compile the client application for this server. It has some errors like this: PWD=/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2 make -C /home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2 -f Makefile make[1]: Entering directory `/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2' ==> Linking clk LD_PRELOAD=/home/fiasco/L4.17/l4/tool/gendep/libgendep.so GENDEP_TARGET=clk GENDEP_BINARY=ld gcc -o clk /home/fiasco/L4.17/build/lib/x86_586/crt0.o main.o -Ttext=0x01100000 -L/home/fiasco/L4.17/build/lib/x86_586/l4v2 -L/home/fiasco/L4.17//lib/x86_586/l4v2 -L/home/fiasco/L4.17/build/lib/x86_586 -L/home/fiasco/L4.17//lib/x86_586 -L/home/fiasco/L4.17/build/lib -L/home/fiasco/L4.17//lib -T/home/fiasco/L4.17/build/lib/x86_586/main_stat.ld -lclock -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a -luc_c -ll4sys -Ttext=0x01100000 -Wl,--warn-common -Wl,-gc-sections main.o: In function `main':/home/fiasco/L4.17/l4/pkg/clock/examples/client/main.c:11: undefined reference to `clock_gettime' collect2: ld returned 1 exit status make[1]: *** [clk] Error 1 make[1]: Leaving directory `/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2' make: *** [/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2] Error 2 it says there is no declaration of clock_gettime(). But according to the same method as showing in BID tutorial my hello example runs well. There is attachment of all my source code file. Please help me and I have this problem for many days. Thank you. Cheng

2 1

I/O port protection
by Daniel Vandersee 12 Jan '07

12 Jan '07

Hi there, is it possible to allow I/O page mapping at the RMGR for a newly created task (using l4_task_new) as it were possible using the "allow_cli" flag in the roottask configuration? Usually the pager of the newly created task would handle its I/O pagefaults. Unfortunately this won't work here as this particular task (L4 loader) tries to directly map I/O pages using an IPC call to the ressource manager. So the question is: How can I tell the ressource manager to allow I/O mapping for this particular task? Thanks, Daniel

2 3

Documentation for L4Linux/L4Env
by Christian, Martin, OPEE45 11 Jan '07

11 Jan '07

Hi, is there some documentation on the L4Linux source code? A kind of what-does-what? I've seen L4Linux has been ported to ARM? Is there a porting guide? HowTo? Wiki? Something more than C or assembler? How much has L4Linux still in common with UML? Which parts were used and where are they now? Best, Martin.

2 1

Indirect IPC or direct IPC
by chenggh 10 Jan '07

10 Jan '07

Hi: Today I read the DICE Manual 3.1.0 and it talks about something about indirect IPC and direct IPC. According to my understanding it seems like this: indirect IPC: sender - > message buffer -> receiver direct IPC: sender ->sender buffer -> receive buffer ->receiver. But I think this understanding is wrong and I don't search something helpful by google, too. If somebody knows please tell me. In this manaul it says ln L4 version 4 all constructed data types will be transmitted by indirect IPC not direct IPC. I also want to know why. Thank you. Best wishes. cheng

3 2

Why I can't get the seconds and nanoseconds like this?
by chenggh 08 Jan '07

08 Jan '07

Hi: I wrote the simple application like this. #include <stdio.h> #include <l4/util/rdtsc.h> #include <l4/sys/l4int.h> #include <l4/thread/thread.h> char LOG_tag[4]="clk"; int main(void) { l4_uint32_t *second; l4_uint32_t *nanosecond; l4_cpu_time_t tsc; tsc = l4_rdtsc(); l4_tsc_to_s_and_ns(tsc, second, nanosecond); printf("%d, %d \n", *second, *nanosecond); } The result is : clk | 0, 0 clk | clk | Exiting with 6 Does these code have some problems? Thank you. cheng

3 2

Re: L4 Demo CD problems
by Dave Haddon 08 Jan '07

08 Jan '07

I am using a PC104 stack with a PIII/1Ghz, 256Mb, CD and 6Gig HD... no floppy..currently running timesys (6.1) (Linux Kernel 2.6.16.16 for i686) I eventually got the source for L4 to Compile by leaving out bits that were causing compiling errors.. RTC for example.. once I got to that point.. my hard drive died and I had to start from scratch.. arrgghh!!!! After much stuffing around to find a workable drive for the PC104, I figured I'd just download the Demo cd and have a whack at that, and it wouldn't work.. I'm starting to get a bit annoyed.. I originally retrieved the L4linux source from CVS, (l4 and linux-2.6) and tried to compile it together from the instructions on the DROPS web and had a lot of missing pieces in timesys, (mainly upto-date PERL and automake).. I haven't tried with QEMU or VMware as I have the PC104 on the same monitor and keyboard.. it is too easy to switch between the PC104 and my desktop (P4 2.8G, SuSe 9.3, KDE 3.4.0b..with no root permissions...) Any info you can give me would be greatly appreciated.. Dave Haddon On Fri, 2007-01-05 at 08:20 +0100, Bjoern Doebel wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > > I have downloaded and burnt the Demo CD exactly as described on the > > website, but it won't come up with the grub menu as described. All I get > > is the Grub command prompt. Have I done something wrong? I have been > > trying to get L4linux to work for ages now and nothing is working.. > > (Mainly a harddrive crash and a lack of root permissions on my main PC > > causing problems...) Can someone please help.. > > some more information about your system, what exactly you've been doing to > run L4Linux and what failures you encountered could be helpful. > And can you maybe try to run the DemoCD-Image in QEMU or VMWare? > > Bjoern > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFFnfxIP5ijxgQLUNkRAuKHAKCQBAHJbkFm6/GaBo7WCyMsnSY1LQCfcKbR > 3LKgzTHKSIU3HlfiEoHadIM= > =6eip > -----END PGP SIGNATURE----- -- CSIRO - Queensland Centre for Advanced Technologies Technology Court Pullenvale Qld 4069 AUSTRALIA PO Box 883 Kenmore Qld 4069 AUSTRALIA Telephone +61 7 3327 4444 Facsimile +61 7 3327 4455

2 1

L4 Demo CD problems
by Dave Haddon 05 Jan '07

05 Jan '07

I have downloaded and burnt the Demo CD exactly as described on the website, but it won't come up with the grub menu as described. All I get is the Grub command prompt. Have I done something wrong? I have been trying to get L4linux to work for ages now and nothing is working.. (Mainly a harddrive crash and a lack of root permissions on my main PC causing problems...) Can someone please help.. Thanks -- CSIRO - Queensland Centre for Advanced Technologies Technology Court Pullenvale Qld 4069 AUSTRALIA PO Box 883 Kenmore Qld 4069 AUSTRALIA Telephone +61 7 3327 4444 Facsimile +61 7 3327 4455

2 1

Problems compiling NICTA::Pistachio-embedded 1.3.0.
by Jaeheon Yi 01 Jan '07

01 Jan '07

Hello, I'm attempting to compile NICTA::Pistachio-embedded, version 1.3.0. I've downloaded the source using tla, via `tla get ertos(a)nicta.com.au--public/pistachio--release my_pistachio`. When I follow the standard L4 compile procedure and perform make, I get this message: [jaeheon@l4rbed ia32-kernel-build]$ make menuconfig dirname: too few arguments Try `dirname --help' for more information. bash: /gccgcc: No such file or directory make[1]: Entering directory `/src/NICTA-1.3.0/ia32-kernel-build' make[2]: Entering directory `/src/NICTA-1.3.0/ia32-kernel-build/config' Compiling rules, please wait......(0.72 sec) Done. Loading 'config.out' failed, continuing... Rewriting Makeconf.local ... make[2]: Leaving directory `/src/NICTA-1.3.0/ia32-kernel-build/config' make[1]: Leaving directory `/src/NICTA-1.3.0/ia32-kernel-build' [jaeheon@l4rbed ia32-kernel-build]$ make dirname: too few arguments Try `dirname --help' for more information. bash: /gccgcc: No such file or directory make[1]: Entering directory `/src/NICTA-1.3.0/ia32-kernel-build' make[1]: *** No rule to make target `src/generic/mapping_alloc.cc', needed by `.depend'. Stop. make[1]: Leaving directory `/src/NICTA-1.3.0/ia32-kernel-build' make: *** [all] Error 2 [jaeheon@l4rbed ia32-kernel-build]$ I've tried doing this for the ARM architecture ala Ben Leslie's L4 dev slides, and that also ends up not finding a certain file. I get the feeling that I am missing some files, or perhaps I have to tweak some config files? I would appreciate any pointers on this issue. Thank you, Jaeheon Yi

2 1

Re: What is difference among these 3 terms: domain, task and thread
by Adam Lackorzynski 29 Dec '06

29 Dec '06

Hi, On Wed Dec 27, 2006 at 16:16:57 +0800, chenggh wrote: > I want to know what is the difference among these 3 terms : domain, task and > thread in L4/Fiasco documents. If sb could understand please show me clearly. Where did you read 'domain' in a Fiasco document? A task is an address space which contains one or more threads. Pagetables are attached to tasks, threads execute code. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

What is difference among these 3 terms: domain, task and thread
by chenggh 27 Dec '06

27 Dec '06

Hi: I want to know what is the difference among these 3 terms : domain, task and thread in L4/Fiasco documents. If sb could understand please show me clearly. thank you. Best wishes. cheng

1 0

Re: failed to booting l4linux from serial console
by chenggh 23 Dec '06

23 Dec '06

> CPU: Intel Pentium III (Coppermine) stepping 03 > 0000 [#1] > Modules linked in: > CPU: 0 > EIP: fd10:[<00501eb0>] Not tainted VLI > EFLAGS: 00213202 (2.6.18-l4 #22) > EIP is at _mmx_memcpy+0x30/0x150 > eax: bff00200 ebx: 00000014 ecx: 00000064 edx: 010cfa84 > esi: 0064d924 edi: 00000200 ebp: 010cdd94 esp: 010cdd84 > ds: fd24 es: 0890 ss: 0000 > Process swapper (pid: 1, ti=010cc000 task=010caa70 task.ti=010cc000) > Stack: 00000014 010ca550 fffffff4 00000200 010cde04 004132e4 010cfa84 > 0064d924 00000500 00000000 00000000 ffffffff ffffffff 010cc038 010ca610 > 010cde5c 00000000 10800711 00000000 010ca550 000000d0 00000000 010c93a8 > 010c93a8 Call Trace: > [<0040c449>] show_stack_log_lvl+0xa9/0xd0 > [<0040c61a>] show_registers+0x15a/0x1c0 > [<0040c795>] die+0x115/0x2d0 > [<00000000>] _start+0xffc00000/0x50 > [<004132e4>] copy_process+0x954/0xfb0 > [<00413b2b>] do_fork+0x6b/0x1c0 > [<004092ba>] kernel_thread+0x7a/0x90 > [<00427707>] keventd_create_kthread+0x27/0x70 > [<0042791a>] kthread_create+0xda/0xe0 > [<0069e226>] cpu_callback+0x76/0xd0 > [<0069e2a2>] spawn_ksoftirqd+0x22/0x50 > [<004001cc>] init+0x1c/0x280 > [<00408960>] kernel_thread_start+0x30/0x40 > [<004084e6>] ret_kernel_thread_start+0x6/0x10 > Code: 53 83 ec 04 8b 75 0c 89 e0 25 00 e0 ff ff f7 40 14 00 ff ff 0f 0f 85 > 11 01 00 00 8b 45 10 c1 e8 06 89 45 f0 89 c3 e8 30 43 f0 ff <0f> 0d 06 0f > 0d 46 40 0f 0d 86 80 00 00 00 0f 0d 86 c0 00 00 00 > EIP: [<00501eb0>] _mmx_memcpy+0x30/0x150 SS:ESP 0023:010cdd7c > <0>Kernel panic - not syncing: Attempted to kill init! > panic: going to sleep forever, bye Right now I forget to tell you my CPU type is Duron. Do you change the cpu type in my configuration? And I suggest in the first time you should use the com1 to display the l4 output information and after you check that the l4 booting is correct you use the com1 to display the l4linux output inforamtion instead of l4. It seems that you have only one serial console. :) it is bad. cheng cheng

1 0

Re: failed to booting l4linux from serial console
by chenggh 23 Dec '06

23 Dec '06

On Saturday 23 December 2006 16:26, halo duan wrote: > Hi all > as my graphic card of my pc can not support l4dope, I boot l4linux from > serial console, my grub configuration looks like following Oh, My l4linux is 2.6.17. I test it works well. In the l4 configuration of l4linux i think there is no special option to be choose except the l4 build directory. and in the linux configuration of l4linux, the options about serial console is like this: # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 according to some errors I suggest you close the option loading module automatically. In this letter there is attachment which is my configuation in l4linux-2.6.17. Maybe it could help you. Good luck. Merry Christmas. cheng

2 1

Re: failed to booting l4linux from serial console
by Adam Lackorzynski 23 Dec '06

23 Dec '06

On Sat Dec 23, 2006 at 17:53:46 +0800, chenggh wrote: > On Saturday 23 December 2006 16:26, halo duan wrote: > > Hi all > > as my graphic card of my pc can not support l4dope, I boot l4linux from > > serial console, my grub configuration looks like following > Oh, My l4linux is 2.6.17. I test it works well. > In the l4 configuration of l4linux i think there is no special option to be > choose except the l4 build directory. > and in the linux configuration of l4linux, the options about serial console > is like this: Please note that you are interfering with the uart here which is not recommended. You can do that of course but then you also need to disable its usage in the kernel to be safe. I recommend using the L4_SERIAL driver. > # Serial drivers > # > CONFIG_SERIAL_8250=y > CONFIG_SERIAL_8250_CONSOLE=y > CONFIG_SERIAL_8250_PCI=y > CONFIG_SERIAL_8250_NR_UARTS=4 > CONFIG_SERIAL_8250_RUNTIME_UARTS=4 > # CONFIG_SERIAL_8250_EXTENDED is not set > > # > # Non-8250 serial port support > # > CONFIG_SERIAL_CORE=y > CONFIG_SERIAL_CORE_CONSOLE=y > # CONFIG_SERIAL_JSM is not set > CONFIG_UNIX98_PTYS=y > CONFIG_LEGACY_PTYS=y > CONFIG_LEGACY_PTY_COUNT=256 > > according to some errors I suggest you close the option loading module > automatically. Which errors are you referring to? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

failed to booting l4linux from serial console
by halo duan 23 Dec '06

23 Dec '06

Hi all as my graphic card of my pc can not support l4dope, I boot l4linux from serial console, my grub configuration looks like following title l4linux root (hd0,0) kernel /l4/bootstrap modaddr 0x02000000 # module /l4/fiasco -serial_esc comspeed 115200 -comport 0 module /l4/fiasco module /l4/sigma0 module /l4/roottask task modname "bmodfs" attached 4 modules module /l4/events module /l4/names --events module /l4/log module /l4/dm_phys --isa=0x00800000 -v --events module /l4/simple_ts -t 300 --events module /l4/rtc --events module /l4/l4io --noirq --events module /l4/bmodfs --events module /l4/libld-l4.s.so module /l4/libloader.s.so module /l4/loadercfg module /l4/vmlinuz26 module /l4/loader --fprov=BMODFS loadercfg # vbeset 0x117 506070 and my loadercfg contains following rules modpath "(hd0,0)/l4" task "vmlinuz26 earlyprintk=yes mem=64M console=ttyS0,115200 root=/dev/hda2" all_sects_writable allow_cli the l4linux build config , I check on the CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set CONFIG_L4_SERIAL=y CONFIG_L4_SERIAL_CONSOLE=y # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set ...... # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_UNIX98_PTYS is not set # CONFIG_LEGACY_PTYS is not set but as i boot up the system , it shows that l4linux can not open the initial console. NET: Registered protocol family 17 input: AT Translated Set 2 keyboard as /class/input/input0 kjournald starting. Commit interval 5 seconds EXT3 FS on hda2, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Warning: unable to open an initial console. modprobe: FATAL: Could not load /lib/modules/2.6.18-l4/modules.dep: No such file or directory udevd[59]: init_uevent_netlink_sock: bind failed: No such file or directory udevd[59]: main: uevent socket not available modprobe: FATAL: Could not load /lib/modules/2.6.18-l4/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-l4/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-l4/modules.dep: No such file or directory Restarting system. anybody give a hand. best regards

2 1

unmap() guaranteed to succeed?
by Marcus Brinkmann 22 Dec '06

22 Dec '06

Hi, I try to understand if (and if yes, why) unmap() in L4 architecture implementations is guaranteed to succeed. I hesitate to say I understood the description in Marcus Völp, Design and Implementation of the Recursive Virtual Address Space Model for Small Scale Multiprocessor Systems, but at least I skimmed through it and have developed sort of a mental picture of the post-order node processing. Bernhard Kauer in L4.sec Implementation also refers to this work. I understand there are substantial variations of L4 implementations, and I don't have a complete picture of which one uses which algorithm. In any case, I am worried about the following scenario, and wonder if you can share with me your insight on the question if this is a valid concern or not: Let's say there is a mapping of the same page from A to B and from A to C. Now, unmap() proceeds in post-order, and deletes the mapping from A to C. Then it is preempted, and a restart point at B is noted. Next B maps the page to B', which updates the restart point to be at B'. Now, unmap() proceeds by deleting the mapping from B to B'. Again, the unmap operation is preempted, with the restart point being B. The cycle continues. There are variations of this, where B' creates a mapping to B'', which creates a mapping to B''' etc, n times in total, and unmap() undos the last k such mappings before it is preempted. As long as n >= k, the B's can create new mappings as fast or faster as unmap can delete them, so there doesn't seem to be a way for unmap() to succeed eventually. I have the feeling that this is an obvious threat scenario and thus is probably addressed already, but I can't find where. I might be missing something obvious. Thanks, Marcus

5 6

AW: L4Linux on L4Ka::Pistachio
by Christian, Martin, OPEE45 22 Dec '06

22 Dec '06

Thanks Volkmar, that sound promising! However, I'll first try if the L4Linux Kernel 2.4 is running on Pistachio for PowerPC. If not, I will look deeper into the kernel 2.6, so I can estimate how much work it is. I've got to minimize my time to (scientific) market. ;-) ... It just came to my mind, that I might confuse things. Is the L4Linux with Kernel 2.4 architecture neutral? That is, there is only L4 dependent C Code and no "real" architecture dependent code like IA32/PowerPC Assembler. I suppose I should just start to get the force and read the source. ;-) Nice holidays, Martin. -----Ursprüngliche Nachricht----- Von: Volkmar Uhlig [mailto:volkmar@volkmaruhlig.com] Gesendet: Mittwoch, 20. Dezember 2006 16:17 An: Christian, Martin, OPEE45; 'Adam Lackorzynski' Cc: l4-hackers(a)os.inf.tu-dresden.de Betreff: RE: L4Linux on L4Ka::Pistachio According to some people I talked to over here, Linux for PPC has pretty much everything abstracted already. So the job at hand is to fill the architecture specific function table with the L4 specific implementation. Linux on Power is more abstracted than x86 in order to accommodate the various hardware platforms and chip versions (...and to run on IBM's hypervisor). - Volkmar

2 1

Fwd: 答复: ×a・￠ : segment fault for fiasco-ux
by halo duan 21 Dec '06

21 Dec '06

at last , my athena say hello to me. thanks very much. [root@athena l4]# ./fiasco Fiasco-UX on Linux 2.6.15-1.2054_FC5 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00099380 [sigma0] Loading Module 0x00120000-0x002b09e4 [roottask] Copying Module 0x039bb000-0x039e0d4e [hello] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 14:23:32 2006 compiled with gcc 4.1.0 for Intel Pentium III CPU: GenuineIntel (6:8:3:2) Model: Pentium III (Coppermine) at 797 MHz 32 Entry I TLB (4K pages) 2 Entry I TLB (4M pages) 64 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 16 KB L1 I Cache (4-way associative, 32 bytes per line) 16 KB L1 D Cache (4-way associative, 32 bytes per line) 256 KB L2 U Cache (8-way associative, 32 bytes per line) Freeing init code/data: 28672 bytes (7 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 39f5000 Found Fiasco: KIP syscalls: yes allocated 4kB for maintainance structures Roottask. Found Fiasco-UX. Command line found: "roottask" 64512kB ( 63MB) total RAM (reported by bootloader) 57500kB ( 57MB) received RAM from Sigma0 1760kB ( 2MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 A B C D E F ] Roottask: Loading 1 module. #05: loading "hello" from [039bb000-039e0d4e] to [01000000-01002eea][01003000-010055c8] entry at 0000d060 via trampoline page code Hello World hello: My thread-id is 5.0 hello: My thread-id is 5.0 hello: My thread-id ps shown following info 6324 tty1 S+ 0:00 ./fiasco-ux -l hello 6325 tty1 S+ 0:00 [I](irq0) 6326 tty1 T+ 0:00 [fiasco-ux] 6327 tty1 T+ 0:00 [fiasco-ux] 6328 tty1 T+ 0:00 [fiasco-ux] 6329 pts/0 R+ 0:00 ps ax On 12/21/06, Carsten Weinhold <weinhold(a)os.inf.tu-dresden.de> wrote: > Am Donnerstag Dezember 21 2006 12:56 schrieb halo duan: > > Hi! > > > [...] > > following is my screen copy of fisco-ux. it's freezed there. I can not use > > CTRL-C to bring up the jdb. > > [...] > > Calibrating timer loop... done. > > > > ^^^^^^ > > freezed to above > > Are you using a System with a recent version of GLibC (you said you were using > Fedorea Core 5 in another email, I think it ships with GLibC 2.4)? If you do, > do you have the most recent Fiasco version from CVS? A TLS-related problem > with new versions of GLibC has been fixed in Fiasco last week, so you should > update your CVS copy. > > Regards, > Carsten > > > [...] >

1 0

Re: 答复: ×a・￠ : segment fault for fiasco-ux
by halo duan 21 Dec '06

21 Dec '06

>Hi, >On Wed Dec 20, 2006 at 14:00:26 +0800, halo.duan wrote: >> and I check the host linux configuration. the page offset is >> CONFIG_PAGE_OFFSET=0xC0000000 which is correct as your >> suggestion.I guss that fiasco-ux must be failed to interpret ELF >> of sigma0/roottask/irq0 and execute it . I put the same "hello" >> bin in grub/ fiasco environment. it works fun. JDB does not help >> me becuase that fiasco-ux enter a stage that CRTL-C does not >> work, I can not bring the system to jdb stage with CRTL-C. ps >> can find three processes which are 'fiasco-ux,[I][irq0] and >> [fiasco-ux]. I can use strace for fiasco-ux and [i][irq0]. but >> failed to trace [fiasco-ux]. >Thats correct, as the fiasco-ux is already ptracing the [fiasco-ux] >binary. I think you haven't shown us the full log of the segfault and >the text before yet, so please post it. We should be able to see more >when we see the log. >Adam following is my screen copy of fisco-ux. it's freezed there. I can not use CTRL-C to bring up the jdb. [root@athena l4]# ./fiasco-ux -l hello Fiasco-UX on Linux 2.6.15-1.2054_FC5 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00099380 [sigma0] Loading Module 0x00120000-0x002b09e4 [roottask] Copying Module 0x039bb000-0x039e0d4e [hello] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Fri Dec 8 18:40:04 2006 compiled with gcc 4.1.0 for Intel Pentium III CPU: GenuineIntel (6:8:3:2) Model: Pentium III (Coppermine) at 797 MHz 32 Entry I TLB (4K pages) 2 Entry I TLB (4M pages) 64 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 16 KB L1 I Cache (4-way associative, 32 bytes per line) 16 KB L1 D Cache (4-way associative, 32 bytes per line) 256 KB L2 U Cache (8-way associative, 32 bytes per line) Freeing init code/data: 28672 bytes (7 pages) Calibrating timer loop... done. ^^^^^^ freezed to above ps shows there are three related process 1955 pts/0 R+ 2:18 ./fiasco-ux -l hello 1956 pts/0 S+ 0:00 [I](irq0) 1957 pts/0 T+ 0:00 [fiasco-ux] strace shows segment fault, i think it's normal for execute "CLI" in userland .

3 2

hiworld example
by Shakthi Kannan 20 Dec '06

20 Dec '06

Hi, After checking out hello, l4/pkg/generic_ts, l4/pkg/cxx, l4/kernel/fiasco, l4/tool/preprocess from CVS and doing: make -C l4 O=build oldconfig cd l4 make O=build stops at: l4/pkg/generic_ts/lib/clientlib/server.c:16:26: error: l4/log/l4log.h: No such file or directory l4/pkg/generic_ts/lib/clientlib/server.c:17:26: error: l4/env/errno.h: No such file or directory l4/pkg/generic_ts/lib/clientlib/server.c:18:31: error: l4/names/libnames.h: No such file or directory What do I need to checkout for log, env and names? System is x86 running Ubuntu Dapper with make-3.81-2. Is there a complete tarball that contains the entire sources - L4env, fiasco, L4Linux, and others, that I can simply download and build, rather than having to check-out individual modules from CVS? Thanks, SK -- Shakthi Kannan http://www.shakthimaan.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

5 8

AW: L4Linux on L4Ka::Pistachio
by Christian, Martin, OPEE45 20 Dec '06

20 Dec '06

Hi Adam! >> a) Is the L4Env required for running L4Linux? > Yes but that's no strict requirement. How much time would it probably take, to adjust L4Linux without L4Env to the L4 Interface of Pistachio? Did anybody try this? >> This is part of my "Diplomarbeit" at the University of Leipzig. > That isn't too far away from here. Well, actually I'm in Friedrichshafen with EADS to write my thesis. But I'm studying at the University of Leipzig. >> b) How much time would it take to port L4Env to L4Ka::Pistachio? > It would probably take me a month or two That's definitely more time, than I've got left. I also assume you know L4Env much better than I do, so it would take me even longer. >> d) What about the Fiasco port to PowerPC from Mathias Lange? > This didn't come to an end. That's a pity! :-( >> e) If Fiasco would be running on PowerPC, would it be possible >> to run L4Linux without changes? > If one wants to have binary compatibility then some PPC code needs > to be there. And then that would not be the way I'm currently doing > things. As far as I understood Michael Hohmuths Diplomarbeit, all Hardware access from Linux is replaced by sycalls to L4. Is that still the case? And so far only the IA32 part of Linux is changed that way, isn't it? So I would basically need to rewrite the PowerPC architecture part of Linux, basically. Isn't it the way things are supposed to be done? > Yes, L4Linux-2.4 also runs in Pistachio, at least it did when we worked > on it. It's all in the l4ka CVS. I'll try it. :-) > I suppose support on this is basically non-existent. L4Ka::Pistachio for PowerPC is also not really supported, so I'm used to not getting support! :-( Thanks, Martin.

3 2

L4linux compile errors..
by Wankeun Jo 20 Dec '06

20 Dec '06

Hi, I use L4Linux-2.6.18 version on pxa255 board. l4linux boots well and then now tried to expand my work for device drivers. I compiled dice and dm_generic, dm_phys packages as well. I want to use the file in "l4linux/arch/arm/mach-pxa/*", so I add the files to be compiled in "l4linux-2.6/arch/l4/Makefile" And I link all the files of "include/asm-arm/arch-pxa/*.h" in "asm-l4/arch-arm/arch" for use. And then I tried to compile l4linux, but failed with the following messages --------------- CHK include/linux/version.h CHK include/linux/utsrelease.h CC arch/l4/kernel/asm-offsets.s In file included from include/linux/sched.h:49, from arch/l4/kernel/asm-offsets.c:93: include/linux/jiffies.h:211:31: missing binary operator before token "#" In file included from include/linux/sched.h:49, from arch/l4/kernel/asm-offsets.c:93: include/linux/jiffies.h: In function `timespec_to_jiffies': include/linux/jiffies.h:316: error: syntax error at '#' token include/linux/jiffies.h:316: error: parse error before "Current" include/linux/jiffies.h:316: error: syntax error at '#' token include/linux/jiffies.h:316: error: parse error before "Current" include/linux/jiffies.h:316: error: syntax error at '#' token include/linux/jiffies.h:316: error: parse error before "Current" include/linux/jiffies.h:316: error: syntax error at '#' token include/linux/jiffies.h:316: error: parse error before "Current" include/linux/jiffies.h:316: error: syntax error at '#' token include/linux/jiffies.h:316: error: parse error before "Current" . . . . include/linux/jiffies.h:389: error: syntax error at '#' token include/linux/jiffies.h:389: error: parse error before "Current" include/linux/jiffies.h:417:6: missing binary operator before token "#" --------------- The error messages are so long. What's the problem?? Is it a compiler problem?? Thank you.

2 1

转发: segment fault for fiasco-ux
by halo.duan 20 Dec '06

20 Dec '06

Hi the linux kernel is 2.6.15-1.2054-FC5, gcc is 4.1.0 20060304. code is the latest update. following is screen copy of gdb Fiasco-UX on Linux 2.6.15-1.2054_FC5 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 6 Loading Module 0x00090000-0x00099380 [sigma0] Loading Module 0x00120000-0x002b09e4 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Fri Dec 8 18:40:04 2006 compiled with gcc 4.1.0 for Intel Pentium III Detaching after fork from child process 2486. Program received signal SIGSEGV, Segmentation fault. Dirq::alloc (this=0xd242d, t=0xd7b80, ack_in_kernel=-1) at /home/halo/l4/kernel/fiasco/src/drivers/ux/processor-ux.cpp:62 62 asm volatile ("cli" : : : "memory"); (gdb) according to the fiasco-ux documents, the SIGSEGV must be handled by fiasico registered handler. but I don't know why fiasco generate such enomous number of SYSSEGV. so what's happened best regards On 12/11/06, halo.duan <halo.duan(a)huawei.com> wrote: > > > -----邮件原件----- > 发件人: l4-hackers-bounces(a)os.inf.tu-dresden.de > [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] 代表 Udo A. Steinberg > 发送时间: 2006年12月11日 15:22 > 收件人: l4-hackers(a)os.inf.tu-dresden.de > 主题: Re: segment fault for fiasco-ux > > On Mon, 11 Dec 2006 09:08:13 +0800 halo.duan (HD) wrote: > > HD> I am newbie for L4 and just downloaded the fiasco last week. > HD> as i compiled as ux and run fiasco hello stuff. loading of sigma0 > HD> and roottask and irq0 is ok. but nothing displayed. as i use > HD> strace attach > the fiasco > HD> process, it shown full screen segment fault. only think i can do is > "kill > HD> -9 PID". > HD> any sugestion? > > What tools did you use to build Fiasco-UX (gcc, binutils, glibc)? Also > your globalconfig.out would be helpful as well putting up a tarball of > your built binaries on the web somewhere. > > - Udo > > >

2 3

Compilation of L4Linux, problems with make
by Dave Haddon 20 Dec '06

20 Dec '06

Hi all, I am having problems trying to build the L4Linux kernel, has anyone seen the problem shown? -bash-2.05b# pwd /fiasco_part/src/l4linux-2.6 -bash-2.05b# make CHK include/linux/version.h CHK include/linux/utsrelease.h CHK include/linux/compile.h dnsdomainname: Host name lookup failure GEN .version CHK include/linux/compile.h dnsdomainname: Host name lookup failure UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 ld: cannot find -lrtc make: *** [.tmp_vmlinux1] Error 1 -bash-2.05b# I have tried to search for an error, but to be honest , I'm lost... Please help? Thanks, Dave

2 3

AW: L4Linux on L4Ka::Pistachio
by Christian, Martin, OPEE45 18 Dec '06

18 Dec '06

Thanks a lot Adam! I'll think about which road to take during Christmas. Nice holidays, Martin. -----Ursprüngliche Nachricht----- Von: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] Im Auftrag von Adam Lackorzynski Gesendet: Samstag, 16. Dezember 2006 00:10 An: l4-hackers(a)os.inf.tu-dresden.de Betreff: Re: L4Linux on L4Ka::Pistachio Hi, On Fri Dec 15, 2006 at 10:11:14 +0100, Christian, Martin, OPEE45 wrote: > >> a) Is the L4Env required for running L4Linux? > > Yes but that's no strict requirement. > How much time would it probably take, to adjust L4Linux without L4Env to > the L4 Interface of Pistachio? Did anybody try this? Something like this is in 2.4. I do not think this is particularly hard. The concepts are the same. One needs to get some memory from somewhere, start tasks somewhere, etc. I don't see big obstacles. > >> e) If Fiasco would be running on PowerPC, would it be possible > >> to run L4Linux without changes? > > If one wants to have binary compatibility then some PPC code needs > > to be there. And then that would not be the way I'm currently doing > > things. > As far as I understood Michael Hohmuths Diplomarbeit, all Hardware > access from Linux is replaced by sycalls to L4. Is that still the case? I'd rather they that it's adapted to run in user-level, using L4. Some of the instructions cannot be executes on user-level, they're replaced, or removed, or whatever. > And so far only the IA32 part of Linux is changed that way, isn't it? So L4Linux is also running on ARM. > I would basically need to rewrite the PowerPC architecture part of > Linux, basically. Isn't it the way things are supposed to be done? Basically yes but all the architecture independant code is already there, and two example architectures. Adam

1 0

Fail to compile Linux kernel on L4Linux
by Jugwan Eom 16 Dec '06

16 Dec '06

Hi, I tried compiling Linux (not L4Linux) kernel on L4Linux. But unhandled page fault was generated during compiling. I use the ubuntu breezy as a root partition. This is the log. ------------------------ L4 Bootstrapper Scaning (nd)/l4/fiasco_org/fiasco -nowait -nokdb -serial_esc -comport 1 Scaning (nd)/l4/bin_org/sigma0 Scaning (nd)/l4/bin_org/roottask Relocated mbi to [0x5f000-0x5f6d0] Loading (nd)/l4/fiasco_org/fiasco Loading (nd)/l4/bin_org/sigma0 Loading (nd)/l4/bin_org/roottask find kernel info page... found kernel info page at 0x1000 API Version: (87) experimental Sigma0 config ip:00094be0 sp:00105100 Roottask config ip:00120000 sp:00108528 [00001000-00002000) (nd)/l4/fiasco_org/fiasco [00002000-00051dc0) (nd)/l4/fiasco_org/fiasco [00051dc0-00059bd0) (nd)/l4/fiasco_org/fiasco [0005a000-0005d4de) (nd)/l4/fiasco_org/fiasco [0005d4e0-0005f000) (nd)/l4/fiasco_org/fiasco [00090000-000993a4) (nd)/l4/bin_org/sigma0 [0009f000-00100000) BIOS area [00100000-00108764) bootstrap [00120000-00133670) (nd)/l4/bin_org/roottask [00134000-0013e87e) (nd)/l4/bin_org/roottask [0013f880-002bda14) (nd)/l4/bin_org/roottask [00300000-00301980) (nd)/l4/fiasco_org/fiasco [00302000-0038f408) (nd)/l4/fiasco_org/fiasco [02000000-028bbb08) Modules Memory [2fffc000-ffffffff) Deep Space Starting kernel (nd)/l4/fiasco_org/fiasco at 003007e8 Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Sun Dec 3 20:42:26 2006 compiled with gcc 3.4.6 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 Found Local APIC version 0x14 id 0x00 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 3d (Periodic Mode) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:1:2:8) Model: Pentium 4 (Willamette/Foster) at 1513 MHz 64 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! KIP @ 1000 Found Fiasco: KIP syscalls: yes allocated 4kB for maintainance structures Roottask. Command line found: "(nd)/l4/bin_org/roottask" 786031kB ( 767MB) total RAM (reported by bootloader) 718912kB ( 703MB) received RAM from Sigma0 9388kB ( 10MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 A B C D E F ] Roottask: Loading 10 modules. #05: loading "(nd)/l4/bin_org/events" from [02130000-02175a9a] to [01540000-015491e4][0154a000-0154c934] entry at 0005a370 via trampoline page code symbols at [2c3fe000-2c400000] (8kB), lines at [2c3f7000-2c3fe000] (28kB) #06: loading "(nd)/l4/bin_org/names --events" from [02176000-021b7e64] to [002d0000-002d614a][002d7000-002e3000] entry at 0005b378 via trampoline page code symbols at [2c3f5000-2c3f7000] (8kB), lines at [2c3ef000-2c3f5000] (24kB) #07: loading "(nd)/l4/bin_org/log --prio 0xA1" from [021b8000-021f6961] to [00400000-00406c4a][00407000-00439890] entry at 0005c378 via trampoline page code symbols at [2c3ed000-2c3ef000] (8kB), lines at [2c3e7000-2c3ed000] (24kB) #08: loading "(nd)/l4/bin_org/dm_phys --events" from [021f7000-02283b76] to [01500000-01511faa][01512000-0151c000] entry at 0005d37c via trampoline page code symbols at [2c3e2000-2c3e7000] (20kB), lines at [2c3d5000-2c3e2000] (52kB) #09: loading "(nd)/l4/bin_org/simple_ts -t 800 --events" from [02284000-022d076b] to [01400000-014086aa][01409000-0141b070] entry at 0005e384 via trampoline page code symbols at [2c3d3000-2c3d5000] (8kB), lines at [2c3cc000-2c3d3000] (28kB) #0a: loading "(nd)/l4/bin_org/rtc" from [022d1000-02302cd8] to [01080000-010841e0][01085000-0108a000] entry at 0006036c via trampoline page code symbols at [2c3ca000-2c3cc000] (8kB), lines at [2c3c5000-2c3ca000] (20kB) #0b: loading "(nd)/l4/bin_org/l4io --noirq" from [02303000-02551e7b] to [00b80000-00ba291c][00ba3000-00c0e000] entry at 00061378 via trampoline page code symbols at [2c376000-2c3c5000] (316kB), lines at [2c35c000-2c376000] (104kB) #0c: loading "(nd)/l4/bin_org/tftp -i" from [02552000-0264e6ab] to [01000000-01027dd4][01028000-01061000] entry at 00062370 via trampoline page code symbols at [2c355000-2c35c000] (28kB), lines at [2c337000-2c355000] (120kB) #0d: loading "(nd)/l4/bin_org/con --l4io --events" from [0264f000-027e017c] to [00b00000-00b4d040][00b4e000-00b79000] entry at 0006337c via trampoline page code symbols at [2c32a000-2c337000] (52kB), lines at [2c2f5000-2c32a000] (212kB) #0e: loading "(nd)/l4/bin_org/loader --events (nd)/l4/bin_org/run (nd)/l4/cfg/l4lx26_hd_org.cfg" from [027e1000-028bbb08] to [01300000-01324630][01325000-0134f000] entry at 000643ac via trampoline page code symbols at [2c2ee000-2c2f5000] (28kB), lines at [2c2d5000-2c2ee000] (100kB) names | Starting thread listening for `exit' events simplets| Configured for 800 tasks. rtc | Date:06.12.2006 Time:14:06:47 con | Using fast memcpy. io | do_args(): Disabling internal IRQ handling. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-20000000 ( 512MB) type WB io | 1: 20000000-30000000 ( 256MB) type WB io | 2: f8000000-fc000000 ( 64MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Enabled i801 SMBus device io | Transparent bridge - Intel Corporation 82801 PCI Bridge io | PCI: No IRQ known for interrupt pin B of device 00:1f.3. Please try u io : sing pci=biosirq. io | 00000000-ffffffff : PCI mem io | ed000000-ed0fffff : Intel Corporation 82557/8/9 [Ethernet Pro 100] io | ed800000-ed800fff : Intel Corporation 82557/8/9 [Ethernet Pro 100] io | ee000000-efdfffff : PCI Bus #01 io | ee000000-eeffffff : nVidia Corporation NV18 [GeForce4 MX 440 AGP io : 8x] io | eff00000-f7ffffff : PCI Bus #01 io | f0000000-f7ffffff : nVidia Corporation NV18 [GeForce4 MX 440 AGP io : 8x] io | f8000000-fbffffff : Intel Corporation 82845 845 (Brookdale) Chipset io : Host Bridge io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | a400-a43f : Intel Corporation 82801BA/BAM AC'97 Audio io | a800-a8ff : Intel Corporation 82801BA/BAM AC'97 Audio io | b000-b01f : Intel Corporation 82801BA/BAM USB (Hub #2) io | b400-b41f : Intel Corporation 82801BA/BAM USB (Hub #1) io | b800-b80f : Intel Corporation 82801BA IDE U100 io | d800-d83f : Intel Corporation 82557/8/9 [Ethernet Pro 100] io | e800-e80f : Intel Corporation 82801BA/BAM SMBus con | Character size is 8x14, font has 256 characters con | VESA reports 800x600@16 1600bpl (039f) [65536kB] con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 con | No supported accelerated graphics card detected io | Remapping I/O memory f0000000-f4000000 cached io | Setting MTRR 3 to f0000000-f4000000 type WC con | Mapped I/O video mem f0000000 => 08000000+000000 [65536kB] via l4io con | Using MMXEXT for colorspace transform tftp | NICs supported: E1000, EEPRO100, NE2000/PCI, PCNET32/PCI, RTL8139, tftp | Tulip, VIA 86C100 con | L4INPUT: !!! W A R N I N G !!! con | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. con | L4INPUT: !!! W A R N I N G !!! con | L4INPUT: Registered 0xb03c50 for callbacks. tftp | Found eepro100 tftp | Ethernet addr: 00:03:47:AF:0A:EF con | serio: i8042 AUX port at 0x60,0x64 irq 12 con | serio: i8042 KBD port at 0x60,0x64 irq 1 tftp | Address: 141.223.121.156 Netmask: 255.255.255.0 tftp | Server: 141.223.121.59 Gateway: 141.223.121.99 con | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 con | input: AT Raw Set 2 keyboard on isa0060/serio0 con | input: PC Speaker con | input: L4 input event injector con | L4 input event injector: IRQ handler up con | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 con | connect "AT Raw Set 2 keyboard", isa0060/serio0/input0 con | connect "PC Speaker", isa0061/input0 con | connect "L4 input event injector", l4/sys con | Running as D.02. Video mode is 800x600@16. tftp | Loading (nd)/l4/bin_org/run [292kB] loader | "(nd)/l4/bin_org/run" needs libld-l4.s.so loader | Setting libpath to (nd)/l4/bin_org/ loader | run: Starting application using libld-l4.s.so loader | run,#f: Loading binary tftp | Loading (nd)/l4/bin_org/libld-l4.s.so [483kB] loader | run,#f: Loading ldso loader | Capability support not supported. loader | run,#f: Starting libld-l4.s.so at 00013890 via 0000cc7c tftp | Loading (nd)/l4/cfg/l4lx26_hd_org.cfg [1kB] loader | sleeping for 2000 ms tftp | File not found: "./libloader.s.so" tftp | Loading (nd)/l4/bin_org//./libloader.s.so [652kB] tftp | Loading (nd)/l4/lx_org/vmlinuz26 [14007kB] loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary tftp | Loading (nd)/l4/bin_org/run [292kB] con | vc_loop(): vc[1] running as D.08 con | vc_open_out(): vc[1] 800x600@16, gmode:0x25 run | contxt_init(): 800x582, cols:100, lines:41, sb_lines:1041 tftp | Loading (nd)/l4/bin_org/libld-l4.s.so [483kB] loader | vmlinuz26,#10: Loading ldso loader | Capability support not supported. loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013890 via 0000cc70 tftp | File not found: "./libloader.s.so" tftp | Loading (nd)/l4/bin_org/./libloader.s.so [652kB] tftp | File not found: "vmlinuz26" tftp | TFTP error 1 tftp | File not found: "(nd)/l4/bin_org/vmlinuz26" l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (zugwan@ubuntu) (gcc version 4.1.2 20060928 ( l4lx : prerelease) (Ubuntu 4.1.1-13ubuntu5)) #1 Wed Dec 6 19:42:58 KST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (2 args): mem=512M root=/dev/hda1 l4lx | Image: 00400000 - 0070a000 [3112 KiB]. l4lx | Areas: Text: 00400000 - 0061f000 [2172kB] (a bit longer) l4lx | Data: 0061f000 - 00660824 [262kB] l4lx | Initdata: 00664000 - 00696000 [200kB] l4lx | BSS: 00698000 - 00708a20 [450kB] l4lx | l4lx_thread_create: Created thread 10.03 (server) l4lx | main thread will be 10.03 l4lx | l4env_register_pointer_section: addr = 00662000 size = 217088 l4lx | sec-w-init: virt: 0x00662000 to 0x00696fff [212 KiB] l4lx | sec-w-init: Number of physical regions: 1, 217088 Bytes l4lx | sec-w-init: 1: Phys: 0x01562000 to 0x01597000, Size: 217088 l4lx | l4env_linux_startup thread 3. l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 512MB l4lx | Main memory: virt: 0x00800000 to 0x207fffff [524288 KiB] l4lx | Main memory: Number of physical regions: 1, 536870912 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x21800000, Size: 536870912 l4lx | Filling lower ptabs... l4lx | Done (1139 entries). l4lx | l4lx_thread_create: Created thread 10.04 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.05 (Idler) l4lx | Starting L4FB via CON con | vc_loop(): vc[2] running as D.09 l4lx | l4lx_thread_create: Created thread 10.06 (L4ConInput) con | vc_open_out(): vc[2] 800x600@16, gmode:0x25 l4lx | l4fbcon: 800x582 2bypp, size: 947200 l4lx | l4lx_thread_create: Created thread 10.07 (CON refresher) l4lx | l4lx_thread_create: Created thread 10.08 (IRQ14) l4lx | l4lx_thread_create: Created thread 10.09 (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ5) l4lx | L4RM: [PF] write at 0x6b3da310, ip 00446f79, src 10.02 l4lx | [10.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault --PANIC, 'g' for exit------------------------------------IP: a00b634d (10.00) jdb: bt thread=10.02 backtrace (thread 10.02, fp=afeffcdc, pc=004017de): #1 afeffcdc 004017de #2 afeffd8c 0040207b #3 afeffdb8 00400d32 #4 afeffe5c 00400e24 #5 afefff7c 004027ad #6 afefffbc a00b88ea : __startup_main + 0x4a /home/zugwan/TUDOS/l4/pkg/l4env/lib/src/startup.c:78 #7 afefffec a00acb2c : l4th_thread_start + 0x7c /home/zugwan/TUDOS/l4/pkg/thread/lib/src/create.c:74 #8 afeffffc a00afd36 : l4th_thread_entry + 0x16 /home/zugwan/TUDOS/l4/pkg/thread/lib/src/l4.c:93 --kernel-bt-follows-- #0 c040176c f00068c0 #1 c040176c f000d92a #2 c04017c8 f000f33a #3 6b3da032 f002a383 (10.00) jdb: ---------------------------------- Is there any one give me an advice or has experienced this? Best regards, -- Jugwan Eom

2 6

missing l4exec
by halo.duan 15 Dec '06

15 Dec '06

Hi all I check out latest fiasco and l4linux-2.6-env and built it successful. but I find l4exec bin no where. I read Makefile of the l4/pkg/exec directory find it get no l4exec target(include instead) , so i change the target to l4exec. It's failed to build. so what happened. It need not l4exec any more or something error in my build environment or binutil. my system is linux-2.6.15 and gcc version is 4.0.1 best regards.

2 1

Wiki for updates
by Shakthi Kannan 15 Dec '06

15 Dec '06

Hi, I was wondering if it is possible to install any wiki for l4 hackers to update the documentation. Most of the documentation is outdated or it doesn't work with currenct CVS code - hiworld example, for instance: http://os.inf.tu-dresden.de/l4env/doc/html/bid-tut/node3.html Build steps also seem to be different for some of the documentation. Maybe those who are testing CVS code can update the wiki? Any thoughts? SK -- Shakthi Kannan http://www.shakthimaan.com ____________________________________________________________________________________ Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now.

2 1

L4Linux on L4Ka::Pistachio
by Christian, Martin, OPEE45 14 Dec '06

14 Dec '06

Hi! 1. Status Report ================ I've got a L4Ka::Pistachio running on an embedded PowerPC and my goal is to get a Linux running on top by end of January. This is part of my "Diplomarbeit" at the University of Leipzig. 2. Questions ============ a) Is the L4Env required for running L4Linux? b) How much time would it take to port L4Env to L4Ka::Pistachio? c) If L4Env was ported to L4Ka::Pistachio, could I run L4Linux without changes? d) What about the Fiasco port to PowerPC from Mathias Lange? He mentioned some problems, so it didn't work. Is it running now? Where could I get the source code? e) If Fiasco would be running on PowerPC, would it be possible to run L4Linux without changes? f) I've read something about L4Linux running on L4Ka::Pistachio with Kernel 2.4? Did I get that right? So I could at least get an old Linux kernel running on my system. g) Anything else? Best regards and thanks for your time, Martin.

2 1

Building Fiasco-UX
by Shakthi Kannan 11 Dec '06

11 Dec '06

Hi, I am trying to build Fiasco-UX as per the documentation: http://os.inf.tu-dresden.de/fiasco/ux/building.shtml on Ubuntu Dapper (Intel, x86). gcc is 4.0.3. g++ is 4.0.3. I have obtained the code from CVS. Did menuconfig: cd l4/kernel/fiasco make menuconfig Have enabled: * Target platform (choose UX) * Generate inline code I don't see the "Assembler IPC shortcut" option. Saved the config. On running: make I get the following errors: make[1]: Circular l4/kernel/fiasco/src/Modules.ux.o <- Modules.ux dependency dropped. make[1]: Circular .Modules.deps <- Modules.ux dependency dropped. make[1]: Circular l4/kernel/fiasco/src/rules.cml.o <- Modules.ux dependency dropped. make[1]: Circular l4/kernel/fiasco/src/rules.cml.o <- .Modules.deps dependency dropped. make[1]: Circular create-sources <- Modules.ux dependency dropped. make[1]: Circular create-sources <- globalconfig.out dependency dropped. make[1]: Circular create-sources <- .Modules.deps dependency dropped. l4/kernel/fiasco/src/Makefile.sub1:17: .Modules.deps: No such file or directory make[2]: *** No rule to make target `.Modules.deps'. Stop. make[1]: *** [create-sources] Error 2 make: *** [build] Error 2 Appreciate any help in building fiasco-ux. Thanks, SK -- Shakthi Kannan http://www.shakthimaan.com ____________________________________________________________________________________ Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com

3 5

segment fault for fiasco-ux
by halo.duan 11 Dec '06

11 Dec '06

Hi all I am newbie for L4 and just downloaded the fiasco last week. as i compiled as ux and run fiasco hello stuff. loading of sigma0 and roottask and irq0 is ok. but nothing displayed. as i use strace attach the fiasco process, it shown full screen segment fault. only think i can do is "kill -9 PID". any sugestion? best regards

2 1

Re: l4-hackers Digest, Vol 44, Issue 4
by cb huang 09 Dec '06

09 Dec '06

> > Hi, > > On Mon Dec 04, 2006 at 22:33:48 +0800, cb huang wrote: > > These days I'm studying the fiasco especially the IPC mechanism, so I > > want to get the paper The Fiasco Kernel: System Architecture, but it > seems > > that the paper is not yet published.Who can tell me where I can get it. > > I think this will never be published. It's also quite old and the IPC > path has changed significantly since then so it's probably not very > useful either. Yes, I know it's quite old, whereas I don't know whether there is another more useful one. Thanks for your reply!

2 1

Where can I get the paper The Fiasco Kernel: System Architecture
by cb huang 06 Dec '06

06 Dec '06

Hi These days I'm studying the fiasco especially the IPC mechanism, so I want to get the paper The Fiasco Kernel: System Architecture, but it seems that the paper is not yet published.Who can tell me where I can get it. Thanks a lot! -- cbhuang

2 1

Re: L4Linux and USB Keyboard/Mouse
by FERANDELLE Pascal 06 Dec '06

06 Dec '06

I added the UHCI HCD support to my config (thanks to lspci -v command ...), and now my keyboard is ok. Under DOpE, my mouse doesn't move from (0,0), but that's an old problem ... Pascal

1 0

L4Linux and USB Keyboard/Mouse
by FERANDELLE Pascal 05 Dec '06

05 Dec '06

On a PC with keyboard/mouse on USB, I booted L4Linux 2.6.17, but I only had keyboard running. That was not a problem when using only l4con. Now, with L4Linux 2.6.18, neither keyboard and mouse are running ... Everything is ok on a PC with keyboard/mouse on PS/2.

2 1

vbemode option in l4dope?
by "Gábor Bérczi (Gabucino)" 05 Dec '06

05 Dec '06

Greetings. I'd like to ask if it's planned to implement l4con's --vbemode command line option in l4dope too? I couldn't get grub's vbeset option to work in QEMU (always ends up in black screen), but l4con-s vbemode option does work. -- Gábor Bérczi

3 9

Can't start L4Linux-2.6.18
by FERANDELLE Pascal 04 Dec '06

04 Dec '06

In august, I tested L4Linux on PC, and everything was working fine with L4Linux-2.6.17. Now, I get the snapshots of 20061116, and rebuild everything. The L4Linux kernel is now 2.6.18. The build is ok, but I can't start it under Fiasco. Here is the log : Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Sat Nov 11 18:26:23 2006 compiled with gcc 3.4.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:4:9:0) Model: Pentium 4E (Prescott/Nocona) at 2793 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-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: 20480 bytes (5 pages) SIGMA0: Hello! ... ... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled! Of course, I have the exception_ipc feature enabled in Fiasco !!! If I rebuild L4Linux-2.6.17, with the L4Env from 20061116, and try to start it under Fiasco, there is no problem ...

2 3

L4Env for X.2 (L4Ka::Pistachio)?
by Christian, Martin, OPEE45 01 Dec '06

01 Dec '06

Hi! On "http://l4hq.org/projects/env/l4env/" I read about L4Env: "Support for X.2 (L4Ka::Pistachio) will follow shortly." Is someone working on it? How is the status? When could I expect a release? Will it be architecture/platform independent? Thanks, Martin.

2 1

Re:Timing problem on mem_fpage_unmap() in the fiasco kernel
by WanKeun Jo 24 Nov '06

24 Nov '06

Hi, I prevented the timing problem to occur by simply unset the l4linux-2.6 option "Show timing information on printks" before. When the option is set, then in the function 'vprintk()' of "l4linux-2.6/kernel/printk.c", the system get current jiffies and then converted it to the string and add it to log buffer. The system works well right before the following codes in the function. When I remove the following code, the system works well without adding timing information on log buffer. ------------------------------------------------ tlen = sprintf(tbuf, 590 "<%c>[%5lu.%06lu] ", 591 loglev_char, 592 (unsigned long)t, 593 nanosec_rem/1000); 594 595 for (tp = tbuf; tp < tbuf + tlen; tp++) 596 emit_log_char(*tp); 597 printed_len += tlen; ------------------------------------------------ However, when I add one of the above three statements - (1) tlen = sprintf(), (2) for(), (3) printed_len += tlen - then the timing error occur during the "Freeing INITRD". even one statement of them.. This is so strange to me and also to you. I'm just beginner in this kind of works, so there might something that I overlooked. Is there somebody who can give me an advice for this kind of ERRORs..?? Thank you.

2 1

fiasco compilation problems
by Hendrik Tews 24 Nov '06

24 Nov '06

I just failed in trying to build fiasco-ux: First I followed the fiasco building and using page (the hello module variant) using the public cvs: - The following dependencies are not mentioned: libncurses5-dev, autoconf, automake1.9, doxygen I don't understand autoconf: the configure scripts should be generated at the distributors site? When autoconf was missing, I got a message saying I need autoconf 2.50, it didn't say I need automake1.9. Here autoconf comes by default with 1.8. Further I don't understand doxygen: Wouldn't it be better to have a separate doc goal and the main make goal independent from doxygen? I appreciate the different config tools in l4 and fiasco as sign of big freedom in this world (and in Dresden in particular). ;-) However, it would make live easier for the casual l4 configurator (like me) if keybindings would agree and fiasco config had an exit button. - the fiasco-ux site says Enable at least the following configuration options: * Target platform (choose UX) * Assembler IPC shortcut * Generate inline code I could neither find IPC shortcut nor inline code. - Then I got the following message: Flex and Byacc. (If you don't have Byacc, but Bison, try setting "bison -y" in the L4 configuration menu under "Compilers and Tools". Other Yacc implementations might do it as well.) but neither the message nor the website says where to find the L4 config menu. Wouldn't it be possible to let the config automatically choose bison if byacc is not found? - the "-C l4" in in 2.a seems to prohibit relativ path for the builddir. Why not cd l4 before? - Point 3.a says "cd l4", but there is no l4 inside l4 - Somebody told me that the preferred way to download fiasco nowadays is to use one of the opentc snapshots. If thats true if would be nice to have a link to these snapshots. - Finally fiasco-ux and all the modules were compiled: tandem l4v2 38> ./fiasco Fiasco-UX on Linux 2.6.17-2-k7 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096d44 [sigma0-ux] Loading Module 0x00120000-0x002bd9f4 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Nov 23 10:27:00 2006 compiled with gcc 4.1.2 for Intel Pentium CPU: AuthenticAMD (F:23:2:0) Model: Athlon 64 X2 (Toledo) at 2418 MHz 32/512 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/512 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-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) ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /home/tews/Fiasco/current/l4/kernel/fiasco/src/kern/ux/hostproc.cpp:120 Now I tried the latest opentc snapshot. I ingored the opentc build instructions and applied the fiasco build instructions to this tree. At some stage it was complaining about gcc-4.1.2 being the wrong compiler version. I changed the compilers to gcc-3.4/g++-3.4 in the l4 config. After that make skipped a lot of dirs, because the goals were done before already. Shouldn't it recompile everything after changing the compiler? So I did make clean then and rebuild. But still I saw a lot of messages with ``g++'' (which would be 4.1.2). That's unproblematic? The compilation stoped eventually with make[3]: Entering directory `/home/tews/Fiasco/opentc-snap/l4/build/doc/building-howto' cp building.tex drops-building.tex cp: cannot stat `building.tex': No such file or directory make[3]: *** [drops-building.tex] Error 1 make[3]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/build/doc/building-howto' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/doc/building-howto' make[1]: *** [building-howto] Error 2 make[1]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/doc' make: *** [doc] Error 2 There seems a problem with the builddir, because tandem l4 29> find . -name building.tex ./doc/building-howto/building.tex However, the build/bin/x86_586/l4v2 dir looked already very full, so I decided to ignore the build instructions and tried: tandem l4v2 7> ./fiasco Fiasco-UX on Linux 2.6.17-2-k7 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096ce4 [sigma0-ux] Loading Module 0x00120000-0x002bda14 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Unknown compiled with gcc 4.1.2 for Intel Pentium CPU: AuthenticAMD (F:23:2:0) Model: Athlon 64 X2 (Toledo) at 2418 MHz 32/512 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/512 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-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) ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /home/tews/Fiasco/opentc-snap/l4/kernel/fiasco/src/kern/ux/hostproc.cpp:120 which is the same problem as before. Bye, Hendrik

2 1

TC and L4
by Burak OÐUZ 23 Nov '06

23 Nov '06

Hi, I have a few questions about L4 and trusted platforms. Are there any implementation of L4 which supports TSS 1.2 stack? Are there any interfaces supplied by L4 to access TPM? Are there any trusted platform application on L4? Thanks in advance.. Best regards.. -- burak() (ps: bf) METU CENG '06

4 3

Performance counter and NMI handling
by Jugwan Eom 22 Nov '06

22 Nov '06

Hi, I'm working to implement the Linux Oprofile functionality on L4/Fiasco environment. OProfile configures the performance counter to raise a NMI whenever the counter overflows. I modified the NMI handling codes in handle_slow_trap() to collect samples but I encountered an strange system behavior, REBOOTING without any information. If there is no user application activity, the system looks fine. Otherwise, the system reboots even if a very simple application like hello runs and the required time before reboot varies. I don't know what causes this behavior. IMHO, it seems a kind of triple fault. Is there any one give me an advice? Thanks in advance. -- Jugwan Eom

2 7

(no subject)
by Christian Roepke 21 Nov '06

21 Nov '06

Hello Ryan, try this one: http://www.ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.gz More information here: http://www.ertos.nicta.com.au/software/prebuilt/binaries.pml Kind regards, Hans > On Mon Nov 20, 2006 at 10:30:59 -0700, Ryan C. Spring wrote: >> I am cross-compiling the DROPS system for ARM and get compiler errors >> about "too many initializers" when it compiles the following statement >> from syscalls_impl.h (line 249) >> >> >> l4_threadid_t preempter = L4_INVALID_ID; >> l4_threadid_t pager = L4_INVALID_ID; >> >> >> When I initialize the unions without the defines, by hand as, it compiles. >> >> l4_threadid_t preempter; >> preempter.raw = (l4_umword_t)-1; >> l4_threadid_t pager; >> pager.raw = (l4_umword_t)-1; >> >> I'm using a TI-provided GCC 3.3.2 ARM crosscompiler. Is my >> cross-compiler to blame here? If so, could someone recommend a >> cross-compiler toolchain for ARM that doesn't error on this syntax? > > I'm using a self-made one, 3.4 based, which works. 4.1 is also known to > work. I can't remember we have tried 3.3 in the past. > > > > Adam -- Hans Christian Röpke Network Administration Applied Data Security Group Ruhr-Universität Bochum, IC 4/42 Universitätsstrasse 150 44780 Bochum, Germany http://www.prosec.rub.de

1 0

Re: Re: Timing problem on mem_fpage_unmap() in the fiasco kernel
by 조완근 21 Nov '06

21 Nov '06

Hi, I solved the timing problem. I just unset the "Show timing information on printks" in "kernel hacking". I found that when the system tries to free INITRD and vprintk() function tries to access any local buffer such as "char tbuf[50]", the system hangs on. I also found all the config files in "l4linux-2.6/arch/arm/configs" unset the option. The option can't work for arm architecture??? Do you know anything about that?? Thank you.

2 1

bug in cross-compiler?
by Ryan C. Spring 20 Nov '06

20 Nov '06

I am cross-compiling the DROPS system for ARM and get compiler errors about "too many initializers" when it compiles the following statement from syscalls_impl.h (line 249) l4_threadid_t preempter = L4_INVALID_ID; l4_threadid_t pager = L4_INVALID_ID; When I initialize the unions without the defines, by hand as, it compiles. l4_threadid_t preempter; preempter.raw = (l4_umword_t)-1; l4_threadid_t pager; pager.raw = (l4_umword_t)-1; I'm using a TI-provided GCC 3.3.2 ARM crosscompiler. Is my cross-compiler to blame here? If so, could someone recommend a cross-compiler toolchain for ARM that doesn't error on this syntax? Regards, Ryan -- Ryan C. Spring Doctoral Student University of Texas at El Paso +1 915-539-7311 www.spring-west.net/ryan

2 1

Re: Does the L4/Fiasco boot from CF card?
by chenggh 18 Nov '06

18 Nov '06

On Saturday 18 November 2006 18:42, Martin Pohlack wrote: > Hi Cheng, > > chenggh wrote: > > Hi, > > Today I want to boot the L4/Fiasco/L4Linux in the CF card. I copy all > > the necessary files into the CF card and install the Grub-0.97-os.1 in > > this CF card. My test machine is a VIA development board and in this > > board the CF card is connected with this machine by the IDE plugin. > > My grub menu.lst is as following: > > > > title L4Linux26/Fiasco+dope > > kernel (hd0,0)/boot/L4Linux/bootstrap > > modaddr 0x06000000 > > module (hd0,0)/boot/L4Linux/main -nowait -nokdb -serial_esc > > -comspeed 115200 -comport 1 > > module (hd0,0)/boot/L4Linux/sigma0 > > module (hd0,0)/boot/L4Linux/roottask task modname "bmodfs" > > attached 4 modules > > module (hd0,0)/boot/L4Linux/events > > module (hd0,0)/boot/L4Linux/names --events > > module (hd0,0)/boot/L4Linux/log --events > > module (hd0,0)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events > > module (hd0,0)/boot/L4Linux/simple_ts -t 300 --events > > module (hd0,0)/boot/L4Linux/rtc --events > > module (hd0,0)/boot/L4Linux/l4io --noirq --events > > module (hd0,0)/boot/L4Linux/l4exec --events > > module (hd0,0)/boot/L4Linux/l4dope --l4io --menubar > > --transparency module (hd0,0)/boot/L4Linux/loader --fprov=BMODFS > > linux26.cfg module (hd0,0)/boot/L4Linux/bmodfs > > module (hd0,0)/boot/L4Linux/vmlinuz26 > > module (hd0,0)/boot/L4Linux/linux26.cfg > > module (hd0,0)/boot/L4Linux/libloader.s.so > > module (hd0,0)/boot/L4Linux/libld-l4.s.so > > vbeset 0x117 506070 > > > > In the PC I have tested this configuration file and it is ok. Wh en I > > boot the VIA machine I choose the only one option to have this results. > > Booting L4Linux26/Fiasco+dope > > kernel (hd0,0)/boot/L4Linux/bootstrap > > > > Error 13 Invalid or unsupported executable format > > > > pass anykey to continue... > > Maybe the CF card reader is not fully ATA compatible? Maybe it emulates > SCSI? Even if it emulates an ATA drive, are you sure it is visible as > (hd0) to grub? Maybe you have to change the paths. I think the hd0 is visible to the grub. when I modify the grub option when booting I could use Tab-Completion in the grub command interface. But I change the path again. Thank you. cheng

1 0

Does the L4/Fiasco boot from CF card?
by chenggh 18 Nov '06

18 Nov '06

Hi, Today I want to boot the L4/Fiasco/L4Linux in the CF card. I copy all the necessary files into the CF card and install the Grub-0.97-os.1 in this CF card. My test machine is a VIA development board and in this board the CF card is connected with this machine by the IDE plugin. My grub menu.lst is as following: title L4Linux26/Fiasco+dope kernel (hd0,0)/boot/L4Linux/bootstrap modaddr 0x06000000 module (hd0,0)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,0)/boot/L4Linux/sigma0 module (hd0,0)/boot/L4Linux/roottask task modname "bmodfs" attached 4 modules module (hd0,0)/boot/L4Linux/events module (hd0,0)/boot/L4Linux/names --events module (hd0,0)/boot/L4Linux/log --events module (hd0,0)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,0)/boot/L4Linux/simple_ts -t 300 --events module (hd0,0)/boot/L4Linux/rtc --events module (hd0,0)/boot/L4Linux/l4io --noirq --events module (hd0,0)/boot/L4Linux/l4exec --events module (hd0,0)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,0)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg module (hd0,0)/boot/L4Linux/bmodfs module (hd0,0)/boot/L4Linux/vmlinuz26 module (hd0,0)/boot/L4Linux/linux26.cfg module (hd0,0)/boot/L4Linux/libloader.s.so module (hd0,0)/boot/L4Linux/libld-l4.s.so vbeset 0x117 506070 In the PC I have tested this configuration file and it is ok. Wh en I boot the VIA machine I choose the only one option to have this results. Booting L4Linux26/Fiasco+dope kernel (hd0,0)/boot/L4Linux/bootstrap Error 13 Invalid or unsupported executable format pass anykey to continue... I tried it many times and I think it could recognize the file and file system (now it is ext3 and I have ever tried ext2). But I don't know why is this prolem. Best wishes. Thank you. cheng

2 1

Re: What is mean of this log?
by chenggh 16 Nov '06

16 Nov '06

On Thursday 16 November 2006 21:19, Christian Stüble wrote: > Hi, > > Am Donnerstag, 16. November 2006 12:45 schrieb chenggh: > > Hi: > > When I boot the L4Linux with L4dope, There are some log statements like > > this: > > > > l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost > > synchronization, > > l4dope : throwing 3 bytes away. > > l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost > > synchronization, > > l4dope : throwing 3 bytes away. > > This looks like Linux is trying to access the input HW directly. I was able > to prevent this messages (and allow user I/O) by reconfiguring L4-Linux: 1) > Activate General/For small systems > 2) Then you can deactivate PC keyboard support etc. > 3) Also disable HW serial support > > > l4lx | Terminating L4Linux. > > l4lx | L4RM: [PF] read at 0x00000a28, ip 00000a29, src 10.02 > > l4lx | [10.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > This error happens here if I try to execute an older L4-Linux binary. Thank you very much. Now my l4dope and l4linux is ok. Nothing error could appear. The minicom log is like this: log | (hd0,1)/boot/L4Linux/log: unrecognized option `--events' log | Unrecognized option: - ? log | Usage: (hd0,1)/boot/L4Linux/log <options>. Option list: log | [ -h | --help ] - this help log | [ -v | --verbose ] - verbose mode log | [ -l | --local ] - flush to local console log | [ -L | --nolocal ] - do not flush to local console log | [ -s | --comport num ] - flush to specified serial interface (0) log | [ -e | --serial-esc ] - enter kdebug on esc on serial log | [ -b | --buffer num ] - buffered mode (0) log | [ --flushprio num ] - priority of flusher thread (0x20) log | [ -p | --prio num ] - priority of main thread (0x20) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:16.11.2006 Time:15:05:15 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00134000 7 12 MAPPED DMphys | 0x00134000-0x001cb000 -- -- DENIED DMphys | 0x001cb000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009e4000 7 12 MAPPED DMphys | 0x009e4000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bef000 -- -- DENIED DMphys | 0x00bef000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114b000 -- -- DENIED DMphys | 0x0114b000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01256000 -- -- DENIED DMphys | 0x01256000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x0134d000 -- -- DENIED DMphys | 0x0134d000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151b000 -- -- RESERVED DMphys | 0x0151b000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154d000 -- -- DENIED DMphys | 0x0154d000-0x01b00000 0 12 MAPPED DMphys | 0x01b00000-0x01b8c000 -- -- DENIED DMphys | 0x01b8c000-0x01c00000 0 12 MAPPED DMphys | 0x01c00000-0x06800000 0 22 MAPPED DMphys | 0x06800000-0x068b8000 0 12 MAPPED DMphys | 0x068b8000-0x077f9000 -- -- DENIED DMphys | 0x077f9000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b839000 0 12 MAPPED DMphys | 0x1b839000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 422900KB total, 422900KB free, 32KB reserved DMphys | 0x009e4000-0x00b80000 ( 1648KB, 2MB) DMphys | 0x00bef000-0x01080000 ( 4676KB, 5MB) DMphys | 0x0108a000-0x01100000 ( 472KB, 0MB) DMphys | 0x0114b000-0x01220000 ( 852KB, 1MB) DMphys | 0x01256000-0x01300000 ( 680KB, 1MB) DMphys | 0x0134d000-0x01400000 ( 716KB, 1MB) DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) DMphys | 0x0151b000-0x01540000 ( 148KB, 0MB) DMphys | 0x0154d000-0x01b00000 ( 5836KB, 6MB) DMphys | 0x01b8c000-0x068b8000 ( 79024KB, 77MB) DMphys | 0x077f9000-0x1b839000 (327936KB, 320MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00134000 ( 208KB, 0MB) DMphys | 0x001cb000-0x002d0000 ( 1044KB, 1MB) DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) DMphys | 0x0043a000-0x009e4000 ( 5800KB, 6MB) l4dope | DOpE(init): using L4 IO server l4dope | (hd0,1)/boot/L4Linux/l4dope: unrecognized option `--menubar' l4dope | DOpE(init): unknown option! l4dope | DOpE(init): using transparency io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-20000000 ( 512MB) type WB io | 1: 1e000000-20000000 ( 32MB) type UC io | 2: e8000000-ec000000 ( 64MB) type WC io | 3: e8000000-ec000000 ( 64MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/L4Linux/vmlinuz26" (14503kB) bmodfs | module "(hd0,1)/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "(hd0,1)/boot/L4Linux/libloader.s.so" (635kB) bmodfs | module "(hd0,1)/boot/L4Linux/libld-l4.s.so" (473kB) io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec1000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec101000-ec1017ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec102000-ec1020ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d400-d47f : VIA Technologies, Inc. IEEE 1394 Host Controller io | d800-d81f : VIA Technologies, Inc. USB io | dc00-dc1f : VIA Technologies, Inc. USB (#2) io | e000-e01f : VIA Technologies, Inc. USB (#3) io | e400-e40f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e800-e8ff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (root@fiasco-desktop) (gcc version 3.4.6 (Ubu l4lx : ntu 3.4.6-1ubuntu2)) #5 Thu Nov 16 22:52:26 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx : t=/dev/hda2 l4lx | Image: 00400000 - 00731000 [3268 KiB]. l4lx | Areas: Text: 00400000 - 00642000 [2312kB] (a bit longer) l4lx | Data: 00642000 - 0068bd8c [295kB] l4lx | Initdata: 0068e000 - 006bf000 [196kB] l4lx | BSS: 006c0000 - 0072f6f0 [445kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 00642000 size = 512000 l4lx | sec-w-init: virt: 0x00642000 to 0x006befff [500 KiB] l4lx | sec-w-init: Number of physical regions: 1, 512000 Bytes l4lx | sec-w-init: 1: Phys: 0x0142b000 to 0x014a8000, Size: 512000 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x07800000 to 0x17800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1611 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=60, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=61, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=62, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=63, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=64, size=800 l4dope | SharedMem(get_adr): address = f000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=66, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=67, size=800 l4dope | SharedMem(get_adr): address = 17000 l4dope | dope: addr=e0000000 size=31680KiB io | Remapping I/O memory e0000000-e1ef0000 cached io | Setting MTRR 4 to e0000000-e2000000 type WC l4dope | Mapped video memory at e0000000 to 04000000+000000 [31680kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=32440320(0x1ef0000) offset=0(0x0) l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=75, size=96000 l4dope | SharedMem(get_adr): address = 400000 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ17) l4lx | l4lx_thread_create: Created thread 10.0b (IRQ16) l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0d (IRQ14) l4lx | l4lx_thread_create: Created thread 10.0e (IRQ13) l4lx | l4lx_thread_create: Created thread 10.0f (IRQ11) l4lx | l4lx_thread_create: Created thread 10.10 (IRQ10) l4lx | l4lx_thread_create: Created thread 10.11 (IRQ9) l4lx | l4lx_thread_create: Created thread 10.12 (IRQ8) l4lx | l4lx_thread_create: Created thread 10.13 (IRQ7) l4lx | l4lx_thread_create: Created thread 10.14 (IRQ6) l4lx | l4lx_thread_create: Created thread 10.15 (IRQ5) l4lx | l4lx_thread_create: Created thread 10.16 (IRQ3) Best wishes. Thank you again. cheng

1 0

What is mean of this log?
by chenggh 16 Nov '06

16 Nov '06

Hi: When I boot the L4Linux with L4dope, There are some log statements like this: l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. l4lx | Terminating L4Linux. l4lx | L4RM: [PF] read at 0x00000a28, ip 00000a29, src 10.02 l4lx | [10.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault What is mean? Thank you. cheng

2 1

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 16 Nov '06

16 Nov '06

On Thursday 16 November 2006 18:17, Stefan Kalkowski wrote: > On Thursday 16 November 2006 11:03, chenggh wrote: > > Thanks for Helmuth very much. Now my l4dope and l4linux could support > > the keyboard and mouse:) I only modify the grub configuration and it is > > ok. > > what have you done ? Exactly, I also modifed the l4linux kernel configuration with disable mouse, keyboard and anything input. Former my grub menu.lst is like this: ... module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg vbeset 0x117 506070 Now it is like this: module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so vbeset 0x117 506070 Thanks for you very much. Basically I could use the L4Linux with graphical user interface. It is very surprising for me. It only use small disk space to boot a grahical application. Later I will publish the l4linux kickstart for the newbie like me to help them to install L4Linux without any mistakes. Best wishes. cheng

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 16 Nov '06

16 Nov '06

On Thursday 16 November 2006 16:55, Christian Helmuth wrote: > Hello chenggh, > > On Thu, Nov 16, 2006 at 07:58:52AM +0800, chenggh wrote: > > If I setup without L4Linux. I could see a graphical interface. But the > > mouse is always at (0,0) and i can't use the mouse anyway. Thanks for Helmuth very much. Now my l4dope and l4linux could support the keyboard and mouse:) I only modify the grub configuration and it is ok. Now I have the new problem. I can't move the mouse out of the l4linux console and it seems that the mouse movement has a range which is the border of l4linux console. And in the attachment there is my l4linux .config file. Please pay attention that my l4linux is 2.6.17 not the latest version 2.6.18. The grub configuration is as following: title L4Linux26/Fiasco+dope kernel (hd0,1)/boot/L4Linux/bootstrap modaddr 0x06000000 module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/L4Linux/sigma0 module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 4 modules module (hd0,1)/boot/L4Linux/events module (hd0,1)/boot/L4Linux/names --events module (hd0,1)/boot/L4Linux/log --events module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events module (hd0,1)/boot/L4Linux/rtc --events module (hd0,1)/boot/L4Linux/l4io --noirq --events module (hd0,1)/boot/L4Linux/l4exec --events module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so vbeset 0x117 506070 The minicom log is as following: log | (hd0,1)/boot/L4Linux/log: unrecognized option `--events' log | Unrecognized option: - ? log | Usage: (hd0,1)/boot/L4Linux/log <options>. Option list: log | [ -h | --help ] - this help log | [ -v | --verbose ] - verbose mode log | [ -l | --local ] - flush to local console log | [ -L | --nolocal ] - do not flush to local console log | [ -s | --comport num ] - flush to specified serial interface (0) log | [ -e | --serial-esc ] - enter kdebug on esc on serial log | [ -b | --buffer num ] - buffered mode (0) log | [ --flushprio num ] - priority of flusher thread (0x20) log | [ -p | --prio num ] - priority of main thread (0x20) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:16.11.2006 Time:09:34:53 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00134000 7 12 MAPPED DMphys | 0x00134000-0x001cb000 -- -- DENIED DMphys | 0x001cb000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009e4000 7 12 MAPPED DMphys | 0x009e4000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bef000 -- -- DENIED DMphys | 0x00bef000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114b000 -- -- DENIED DMphys | 0x0114b000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01256000 -- -- DENIED DMphys | 0x01256000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x0134d000 -- -- DENIED DMphys | 0x0134d000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151b000 -- -- RESERVED DMphys | 0x0151b000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154d000 -- -- DENIED DMphys | 0x0154d000-0x01b00000 0 12 MAPPED DMphys | 0x01b00000-0x01b8c000 -- -- DENIED DMphys | 0x01b8c000-0x01c00000 0 12 MAPPED DMphys | 0x01c00000-0x06800000 0 22 MAPPED DMphys | 0x06800000-0x068b8000 0 12 MAPPED DMphys | 0x068b8000-0x077f2000 -- -- DENIED DMphys | 0x077f2000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b839000 0 12 MAPPED DMphys | 0x1b839000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 422928KB total, 422928KB free, 32KB reserved DMphys | 0x009e4000-0x00b80000 ( 1648KB, 2MB) DMphys | 0x00bef000-0x01080000 ( 4676KB, 5MB) DMphys | 0x0108a000-0x01100000 ( 472KB, 0MB) DMphys | 0x0114b000-0x01220000 ( 852KB, 1MB) DMphys | 0x01256000-0x01300000 ( 680KB, 1MB) DMphys | 0x0134d000-0x01400000 ( 716KB, 1MB) DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) DMphys | 0x0151b000-0x01540000 ( 148KB, 0MB) DMphys | 0x0154d000-0x01b00000 ( 5836KB, 6MB) DMphys | 0x01b8c000-0x068b8000 ( 79024KB, 77MB) DMphys | 0x077f2000-0x1b839000 (327964KB, 320MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00134000 ( 208KB, 0MB) DMphys | 0x001cb000-0x002d0000 ( 1044KB, 1MB) DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) DMphys | 0x0043a000-0x009e4000 ( 5800KB, 6MB) bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/L4Linux/vmlinuz26" (14475kB) bmodfs | module "(hd0,1)/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "(hd0,1)/boot/L4Linux/libloader.s.so" (635kB) bmodfs | module "(hd0,1)/boot/L4Linux/libld-l4.s.so" (473kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-20000000 ( 512MB) type WB io | 1: 1e000000-20000000 ( 32MB) type UC io | 2: e8000000-ec000000 ( 64MB) type WC io | 3: e8000000-ec000000 ( 64MB) type WC l4dope | DOpE(init): using L4 IO server l4dope | (hd0,1)/boot/L4Linux/l4dope: unrecognized option `--menubar' l4dope | DOpE(init): unknown option! l4dope | DOpE(init): using transparency loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec1000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec101000-ec1017ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec102000-ec1020ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d400-d47f : VIA Technologies, Inc. IEEE 1394 Host Controller io | d800-d81f : VIA Technologies, Inc. USB io | dc00-dc1f : VIA Technologies, Inc. USB (#2) io | e000-e01f : VIA Technologies, Inc. USB (#3) io | e400-e40f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e800-e8ff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (root@fiasco-desktop) (gcc version 3.4.6 (Ubu l4lx : ntu 3.4.6-1ubuntu2)) #4 Wed Nov 15 22:47:04 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx : t=/dev/hda2 l4lx | Image: 00400000 - 0072e000 [3256 KiB]. l4lx | Areas: Text: 00400000 - 00642000 [2312kB] (a bit longer) l4lx | Data: 00642000 - 0068bd8c [295kB] l4lx | Initdata: 0068e000 - 006bf000 [196kB] l4lx | BSS: 006c0000 - 0072c930 [434kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 00642000 size = 512000 l4lx | sec-w-init: virt: 0x00642000 to 0x006befff [500 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 512000 Bytes l4lx | sec-w-init: 1: Phys: 0x0141c000 to 0x01488000, Size: 442368 l4lx | sec-w-init: 2: Phys: 0x0120f000 to 0x01220000, Size: 69632 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x07800000 to 0x17800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1614 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=60, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=61, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=62, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=63, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=64, size=800 l4dope | SharedMem(get_adr): address = f000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=66, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=67, size=800 l4dope | SharedMem(get_adr): address = 17000 l4dope | dope: addr=e0000000 size=31680KiB io | Remapping I/O memory e0000000-e1ef0000 cached io | Setting MTRR 4 to e0000000-e2000000 type WC l4dope | Mapped video memory at e0000000 to 04000000+000000 [31680kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=32440320(0x1ef0000) offset=0(0x0) l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=75, size=96000 l4dope | SharedMem(get_adr): address = 400000 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ17) l4lx | l4lx_thread_create: Created thread 10.0b (IRQ16) l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0d (IRQ14) l4lx | l4lx_thread_create: Created thread 10.0e (IRQ13) l4lx | l4lx_thread_create: Created thread 10.0f (IRQ11) l4lx | l4lx_thread_create: Created thread 10.10 (IRQ10) l4lx | l4lx_thread_create: Created thread 10.11 (IRQ9) l4lx | l4lx_thread_create: Created thread 10.12 (IRQ8) l4lx | l4lx_thread_create: Created thread 10.13 (IRQ7) l4lx | l4lx_thread_create: Created thread 10.14 (IRQ6) l4lx | l4lx_thread_create: Created thread 10.15 (IRQ5) l4lx | l4lx_thread_create: Created thread 10.16 (IRQ3) l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. Thank you. cheng

2 1

No mouse and keyboard with the L4Linux/DOpE
by chenggh 16 Nov '06

16 Nov '06

Hi: Now I boot the l4dope but I can't use the keyboard and mouse. In the l4linux console I could see the cursor flases and the mouse stayes in the at (0,0). But i can't input anyth character and I can't move the mouse. I have checked the former mailists. And adam said we couldn't use the usb mouse and keyboard. Now in my system I use the ps/2 mouse and ps/2 keyboard. And when I push the NumLock key and the light couldn't be on, it is off alyways. So i think the keyboard is dead and have nothing reponsing. In the L4/Fiasco booting process there are some warnings like this: bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/L4Linux/vmlinuz26" (14716kB) bmodfs | module "(hd0,1)/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "(hd0,1)/boot/L4Linux/libloader.s.so" (635kB) bmodfs | module "(hd0,1)/boot/L4Linux/libld-l4.s.so" (473kB) bmodfs | module "(hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg" (84 bmodfs : 4kB) l 4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. 4dope | L4INPUT: !!! W A R N I N G !!! loader | vmlinuz26: Starting application using libld-l4.s.so My grub configuration is as following: title L4Linux26/Fiasco+dope kernel (hd0,1)/boot/L4Linux/bootstrap modaddr 0x03000000 module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/L4Linux/sigma0 module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 5 modules module (hd0,1)/boot/L4Linux/events module (hd0,1)/boot/L4Linux/names -events module (hd0,1)/boot/L4Linux/log module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events module (hd0,1)/boot/L4Linux/rtc --events module (hd0,1)/boot/L4Linux/l4io -noirq --events module (hd0,1)/boot/L4Linux/l4exec --events module (hd0,1)/boot/L4Linux/l4dope -l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg vbeset 0x117 506070 Thank you. cheng

3 2

Re: No mouse and keyboard with the L4Linux/DOpE
by Christian Helmuth 16 Nov '06

16 Nov '06

Hello chenggh, On Thu, Nov 16, 2006 at 07:58:52AM +0800, chenggh wrote: > If I setup without L4Linux. I could see a graphical interface. But the mouse > is always at (0,0) and i can't use the mouse anyway. [...] > The minicom log is like this: [...] > l4lx | ======> L4Linux 2.6 starting... <======== No offense meant, but are you kidding? Please, send the log _without_ starting L4Linux. Thanks -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 16 Nov '06

16 Nov '06

On Thursday 16 November 2006 07:05, Adam Lackorzynski wrote: > On Wed Nov 15, 2006 at 20:55:00 +0800, chenggh wrote: > > On Wednesday 15 November 2006 20:18, chenggh wrote: > > > On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > > > > Hi, > > > > Here is my L4Linux booting log, Please look at it to help me. thank you. > > First, please try to do what Christian suggested: Try your setup > _without_ L4Linux, this helps to identify if L4Linux is the culprit or > not. If I setup without L4Linux. I could see a graphical interface. But the mouse is always at (0,0) and i can't use the mouse anyway. > Second thing, if you do not see any more output from Linux in the > log (via serial or in the terminal you run Fiasco-UX in) and your > output device (e.g. framebuffer) does not come up for some reason, like > in your current example, enable CONFIG_L4_SERIAL and > CONFIG_L4_SERIAL_CONSOLE. Then add console=ttyLv0 to your kernel command > line. With this Linux should print the boot up in minicom or xterm > (Fiasco-UX). The minicom log is like this: l4dope | DOpE(init): using L4 IO server l4dope | (hd0,1)/boot/L4Linux/l4dope: unrecognized option `--menubar' l4dope | DOpE(init): unknown option! l4dope | DOpE(init): using transparency loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec1000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec101000-ec1017ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec102000-ec1020ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d400-d47f : VIA Technologies, Inc. IEEE 1394 Host Controller io | d800-d81f : VIA Technologies, Inc. USB io | dc00-dc1f : VIA Technologies, Inc. USB (#2) io | e000-e01f : VIA Technologies, Inc. USB (#3) io | e400-e40f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e800-e8ff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4d, size=800 l4dope | SharedMem(get_adr): address = 5000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4e, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4f, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=50, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=51, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=53, size=800 l4dope | SharedMem(get_adr): address = 15000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=54, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | dope: addr=e0000000 size=31680KiB io | Remapping I/O memory e0000000-e1ef0000 cached io | Setting MTRR 4 to e0000000-e2000000 type WC l4dope | Mapped video memory at e0000000 to 04000000+000000 [31680kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=32440320(0x1ef0000) offset=0(0x0) l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (root@fiasco-desktop) (gcc version 3.4.6 (Ubu l4lx : ntu 3.4.6-1ubuntu2)) #3 Wed Nov 15 12:19:04 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx : t=/dev/hda2 l4lx | Image: 00400000 - 0073e000 [3320 KiB]. l4lx | Areas: Text: 00400000 - 0064e000 [2360kB] (a bit longer) l4lx | Data: 0064e000 - 0069ad8c [307kB] l4lx | Initdata: 0069e000 - 006d0000 [200kB] l4lx | BSS: 006d0000 - 0073cb30 [434kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 0069c000 size = 663552 l4lx | sec-w-init: virt: 0x0069c000 to 0x0073dfff [648 KiB] l4lx | sec-w-init: Number of physical regions: 1, 663552 Bytes l4lx | sec-w-init: 1: Phys: 0x0145b000 to 0x014fd000, Size: 663552 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0b800000 to 0x1b800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1598 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=75, size=96000 l4dope | SharedMem(get_adr): address = 400000 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ17) l4lx | l4lx_thread_create: Created thread 10.0b (IRQ16) l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0d (IRQ14) l4lx | l4lx_thread_create: Created thread 10.0e (IRQ13) l4lx | l4lx_thread_create: Created thread 10.0f (IRQ11) l4lx | l4lx_thread_create: Created thread 10.10 (IRQ10) l4lx | l4lx_thread_create: Created thread 10.11 (IRQ9) l4lx | l4lx_thread_create: Created thread 10.12 (IRQ8) l4lx | l4lx_thread_create: Created thread 10.13 (IRQ7) l4lx | l4lx_thread_create: Created thread 10.14 (IRQ6) l4lx | l4lx_thread_create: Created thread 10.15 (IRQ5) l4lx | l4lx_thread_create: Created thread 10.16 (IRQ3) It is end. cheng

1 0

Timing problem on mem_fpage_unmap() in the fiasco kernel
by WanKeun Jo 16 Nov '06

16 Nov '06

Hi, I've been working on porting DROPS to Bulverde board - PXA270. My senior already made DROPS work on OMAP board before. He worked with L4Linux-2.6.16, but I don't know exact version of fiasco kernel and L4Env packages because they are not specified. I got all the sources from my senior - not the latest things.. - and have tried them work on Bulverde board. My status is that I have an unsolvable error in fiasco kernel. On L4Linux-2.6.16's booting process, one step is "Freeing INITRD", and system halted on that point. By tracing codes, I got to know while the mem_fpage_unmap() function in l4/kernel/fiasco/src/kern/map_util.cpp executed, the system halted. And I put "delay codes" into that function's for() {}, and then the system continued to execute and boot succeed. I found this fact after I added printf() into that code in order to debug. On that point - "Freeing INITRD", whether the boot process goes next step or not depends on how much delay time is put on that code, mem_fpage_unmap(). If I make the delay time a little bit longer, then the system goes to next step at that point, but stops somewhere else after that. If I make the delay time too short, the system never go to next step. And the mem_fpage_unmap() is called a lot while the system works, but only in the "Freeing INITRD" part, the problem appears. I think this is a serious timing error, but I can't know what the problem is. I already tried all the combinations of kernel and L4Linux options before. when I tried to install the latest kernel and l4linux-2.6.18, the halting problem didn't appear. And I found that the latest kernel's mem_fpage_unmap() functions implementation has a lot of changes compared to the kernel I work with. Could you help me solve this problem?? Please don't say to me "use the latest one".. My senior already succeed on OMAP board with the old versions. Thank you.

3 2

Re: No mouse and keyboard with the L4Linux/DOpE
by Adam Lackorzynski 16 Nov '06

16 Nov '06

On Wed Nov 15, 2006 at 20:55:00 +0800, chenggh wrote: > On Wednesday 15 November 2006 20:18, chenggh wrote: > > On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > > > Hi, > > > > Here is my L4Linux booting log, Please look at it to help me. thank you. First, please try to do what Christian suggested: Try your setup _without_ L4Linux, this helps to identify if L4Linux is the culprit or not. Second thing, if you do not see any more output from Linux in the log (via serial or in the terminal you run Fiasco-UX in) and your output device (e.g. framebuffer) does not come up for some reason, like in your current example, enable CONFIG_L4_SERIAL and CONFIG_L4_SERIAL_CONSOLE. Then add console=ttyLv0 to your kernel command line. With this Linux should print the boot up in minicom or xterm (Fiasco-UX). Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 15 Nov '06

15 Nov '06

On Wednesday 15 November 2006 20:18, chenggh wrote: > On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > > Hi, > > Here is my L4Linux booting log, Please look at it to help me. thank you. l4dope | DOpE(init): using L4 IO server l4dope | (hd0,1)/boot/L4Linux/l4dope: unrecognized option `--menubar' l4dope | DOpE(init): unknown option! l4dope | DOpE(init): using transparency loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec1000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec101000-ec1017ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec102000-ec1020ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d400-d47f : VIA Technologies, Inc. IEEE 1394 Host Controller io | d800-d81f : VIA Technologies, Inc. USB io | dc00-dc1f : VIA Technologies, Inc. USB (#2) io | e000-e01f : VIA Technologies, Inc. USB (#3) io | e400-e40f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e800-e8ff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4d, size=800 l4dope | SharedMem(get_adr): address = 5000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4e, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4f, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=50, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=51, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=53, size=800 l4dope | SharedMem(get_adr): address = 15000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=54, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | dope: addr=e0000000 size=31680KiB io | Remapping I/O memory e0000000-e1ef0000 cached io | Setting MTRR 4 to e0000000-e2000000 type WC l4dope | Mapped video memory at e0000000 to 04000000+000000 [31680kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=32440320(0x1ef0000) offset=0(0x0) l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (root@fiasco-desktop) (gcc version 3.4.6 (Ubu l4lx : ntu 3.4.6-1ubuntu2)) #3 Wed Nov 15 12:19:04 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx : t=/dev/hda2 l4lx | Image: 00400000 - 0073e000 [3320 KiB]. l4lx | Areas: Text: 00400000 - 0064e000 [2360kB] (a bit longer) l4lx | Data: 0064e000 - 0069ad8c [307kB] l4lx | Initdata: 0069e000 - 006d0000 [200kB] l4lx | BSS: 006d0000 - 0073cb30 [434kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 0069c000 size = 663552 l4lx | sec-w-init: virt: 0x0069c000 to 0x0073dfff [648 KiB] l4lx | sec-w-init: Number of physical regions: 1, 663552 Bytes l4lx | sec-w-init: 1: Phys: 0x0145b000 to 0x014fd000, Size: 663552 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0b800000 to 0x1b800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1598 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=75, size=96000 l4dope | SharedMem(get_adr): address = 400000 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ17) l4lx | l4lx_thread_create: Created thread 10.0b (IRQ16) l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0d (IRQ14) l4lx | l4lx_thread_create: Created thread 10.0e (IRQ13) l4lx | l4lx_thread_create: Created thread 10.0f (IRQ11) l4lx | l4lx_thread_create: Created thread 10.10 (IRQ10) l4lx | l4lx_thread_create: Created thread 10.11 (IRQ9) l4lx | l4lx_thread_create: Created thread 10.12 (IRQ8) l4lx | l4lx_thread_create: Created thread 10.13 (IRQ7) l4lx | l4lx_thread_create: Created thread 10.14 (IRQ6) l4lx | l4lx_thread_create: Created thread 10.15 (IRQ5) l4lx | l4lx_thread_create: Created thread 10.16 (IRQ3) It is end. cheng

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by Christian Helmuth 15 Nov '06

15 Nov '06

Hello, On Wed, Nov 15, 2006 at 08:18:42PM +0800, chenggh wrote: > Now It has the same prolems with unavailabe mouse and keyboard. the menu.lst > is as following: > > title L4Linux26/Fiasco+dope > kernel (hd0,1)/boot/L4Linux/bootstrap > modaddr 0x06000000 > module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed > 115200 -comport 1 > module (hd0,1)/boot/L4Linux/sigma0 > module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 5 > modules > module (hd0,1)/boot/L4Linux/events > module (hd0,1)/boot/L4Linux/names --events > module (hd0,1)/boot/L4Linux/log > module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events > module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events > module (hd0,1)/boot/L4Linux/rtc --events > module (hd0,1)/boot/L4Linux/l4io --noirq --events > module (hd0,1)/boot/L4Linux/l4exec --events > module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency > module (hd0,1)/boot/L4Linux/loader --fprov BMODFS linux26.cfg > module (hd0,1)/boot/L4Linux/bmodfs > module (hd0,1)/boot/L4Linux/vmlinuz26 > module (hd0,1)/boot/L4Linux/linux26.cfg > module (hd0,1)/boot/L4Linux/libloader.s.so > module (hd0,1)/boot/L4Linux/libld-l4.s.so > module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg > vbeset 0x117 506070 > > And the linux26.cfg is like this: > verbose 0 > task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb root=/dev/hda2" > all_sects_writable For me it looks like you're still running L4Linux via loader. Anyway: * Be sure to limit your scenario to just l4env and dope (Remove all lines after .../l4dope.) * Try to run l4io w/o "--noirq" as this mode is seldom tested and will not work in the future. If the problem persists, please, send a complete log of your boot process. Ciao -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 15 Nov '06

15 Nov '06

On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > Hi, > > try to boot your configuration w/o L4Linux. Do mouse and keyboard work now > in dope? > > Cheers Now It has the same prolems with unavailabe mouse and keyboard. the menu.lst is as following: title L4Linux26/Fiasco+dope kernel (hd0,1)/boot/L4Linux/bootstrap modaddr 0x06000000 module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/L4Linux/sigma0 module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 5 modules module (hd0,1)/boot/L4Linux/events module (hd0,1)/boot/L4Linux/names --events module (hd0,1)/boot/L4Linux/log module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events module (hd0,1)/boot/L4Linux/rtc --events module (hd0,1)/boot/L4Linux/l4io --noirq --events module (hd0,1)/boot/L4Linux/l4exec --events module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg vbeset 0x117 506070 And the linux26.cfg is like this: verbose 0 task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb root=/dev/hda2" all_sects_writable Thank you. cheng

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by Christian Helmuth 15 Nov '06

15 Nov '06

Hi, try to boot your configuration w/o L4Linux. Do mouse and keyboard work now in dope? Cheers -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

L4Linux and virtualization
by Robert Gubler 14 Nov '06

14 Nov '06

Hello, I'd like to run two L4Linux 2.4 based kernels and one L4Linux 2.6 based kernel. Is this something that can be achieved relatively easily or would all running kernels need to be 2.6/2.4? How do the 'guest' kernels communicate to each other in an L4 environment? In User Mode Linux (UML) and Xen on the guest kernels there is built-in support for pseudo Ethernet devices; these devices are then bridged together on the host kernel. I understand the architecture is considerably different in L4, but is there some similar mechanism already in place that allows Ethernet/IP communication between the running Linux kernels? Thanks in advance, Rob

3 2

L4 API and ABI Documentation
by Till Backhaus 12 Nov '06

12 Nov '06

Dear L4-Hackers, to get started with L4 I'd like to take a look at the L4 API- Documentation and the L4 ABI-Documentation for the PowerPC. Unfortunately I didn't find them at your site. Maybe someone can point me to the right document(s)? Thanks in advance, Till Backhaus

2 1

new system call for L4
by Suresh Iyer 12 Nov '06

12 Nov '06

how do i implement a new system call for L4 ? I am tryiing out a new real time scheduling algorithm for L4? thanks suresh

2 1

IPC from L4Linux
by Daniel Vandersee 02 Nov '06

02 Nov '06

Hi there, when I place an ipc call from a l4linux task to an l4 server, I always get a task number, which, I think, is not assigned. Is for every l4linux task a new l4 task is generated/reserved? With kind regards, Daniel

3 5

kernel bug in combination with jdb
by Johannes Richter 01 Nov '06

01 Nov '06

Hi, I found a kernel bug; while selecting the partner of my task 6 in the kernel debugger with tab in the list of present tasks i got the message: id name pr wait to state ???.?? KERNEL BUG at EIP:0001eea8 ESP:000d39e4 -- PFA:00000006 ASSERTION_FAILED (Kmem::is_tcb_page_fault((Mword) kesp, 0)) in function static void Usermode::kernel_entry(ucontext*, long unsigned int, long unsigned int, long unsigned int, long unsigned int, long unsigned int, long unsigned int, long unsigned int, long unsigned int)progr in file ../src/kern/ux/usermode.cpp:204 cu - Joe

2 1

Re: FW: XGenOS / Fiasco
by William DUCK 28 Oct '06

28 Oct '06

On Sunday 22 October 2006 21:56, you wrote: > Hello, > > I must confess your mail came as a big surprise, since nobody seemed to > care about the XGeNOS project for quite some time, but of course the > surprise is a pleasing one ;-) > > Considering your thougths and ideas below, I'll try to figure out as > much as possible for the moment ... I've been thinking over some of > them, but it will take me some time to get through it all ... > > > I would want to know if this is possible to use fiasco and a uclibc-nptl > > rewrote in cyclone for a XGenOS fork. > > http://www.xgenos.org/ > > http://os.inf.tu-dresden.de/vfiasco/ > > Well, vfiasco is an interesting project and complements to some work I'm > going to do as a part of my PhD thesis. On the other hand from the > viewpoint of the u-kernel API an implementation of X.2 seems to be a > good idea, which would rather imply to use the pistachio kernel ... > http://cyclone.thelanguage.org/ > > Interesting. I never came across that before, but it seems this could > solve some problems of mine (not only XGeNOS related ...) > http://www.realitydiluted.com/nptl-uclibc/ > > http://www.busybox.net/cgi-bin/viewcvs.cgi/branches/uClibc-nptl/ > > uhm, I'd be happy if there was an alternative to uClibc as my previous > experiences with uClibc have shown that its code is from so many > different sources that it's sometimes quite hard to keep the overview. I > guess the code is quite hard to maintain which IMHO is not the perfect > basis for secure software ... But, I cannot see any alternative to > uClibc for the moment ... I'll probably have a look at Peter Anvins > klibc in some time, maybe that could be an alternate starting point for > a suitable C-library ... > > > Could we be able to merge the best ideas from these projects ? : > > > > http://www.marcus-brinkmann.org/hurd-ng.pdf > > > > http://www.research.ibm.com/K42/papers/eurosys06.pdf > > > > http://domino.research.ibm.com/comm/research_projects.nsf/pages/prose.ind > >ex.html > > Lots to read ;-) Give me some time to check that out ... > > > Which Device Driver Framework could be the best and that will let us > > reuse the > > maximum of linux drivers code ? : > > > > http://www.jaluna.com/doc/c5/html/BSPDevGuide/c3882.html > > > > http://sourceforge.net/projects/jaluna/ > > > > http://www.circlemud.org/~jelson/software/fusd/ > > <http://www.circlemud.org/%7Ejelson/software/fusd/> > > > > http://www.gelato.unsw.edu.au/IA64wiki/UserLevelDrivers > > Well, IMHO the device driver framwork is the crucial point of the whole > system. I've got some ideas that derive partly from some of the projects > mentioned above, and others (e.g the sawmill project, etc.). I agree > that reusage of existing driver code must be on of the project goals, > but if this turns out to be of some security risk, one should think of > some other solutions ... but that's just my EUR 0.02 ... > > > Could haskell be a good alternative to C ? : > > > > http://programatica.cs.pdx.edu/House/ > > > > http://www.ertos.nicta.com.au/research/sel4/ > > > > http://repetae.net/john/computer/jhc/ > > > > http://www.cse.unsw.edu.au/~chak/haskell/c2hs/ > > <http://www.cse.unsw.edu.au/%7Echak/haskell/c2hs/> > > I must confess I haven't dealt with Haskell yet, so I can't say anything > about that ... > > > Time is not a problem, I would to know only which basis could be the most > > suitable for an innovative project ... > > Let's stay on contact, any ideas are welcome. Pls. use the above > mail-address (ta(a)xgenos.org) if possible. I'm probably going to set up a > mailinglist in some time ... > > Best regards, > > -ta

1 0

DROPS L4Env I/O client API not applicable for C++ programs
by Marcel Winandy 24 Oct '06

24 Oct '06

Hello! I have just encountered a problem with the L4Env I/O client API libio.h if you try to use this in a C++ program. You get a syntax error because there is a variable having the name "class". But that is a C++ keyword. In l4/include/x86/l4/generic_io/types.h: **************************************** struct l4io_drv: "unsigned class:8;" struct l4io_pci_dev: "unsigned long class;" In l4/include/x86/l4/generic_io/libio.h: **************************************** "int l4io_pci_find_class(unsigned long class, ...)" Although these variable names are possible in C, you run in syntax errors when trying to use these API interfaces in a C++ program. I think these variables should get other names, shouldn't they? Kind regards Marcel -- Marcel Winandy http://www.prosec.rub.de/staff/winandy.html Applied Data Security Group, Ruhr-University Bochum, Germany

2 1

PowerPC Port
by William DUCK 20 Oct '06

20 Oct '06

Hello, DId/Will someone port Fiasco to Power Architecture ? http://www.power.org/members/developers/specs/PAPR_Version_2.0_28August06.p… http://www.power.org/resources/downloads/PowerISA_203.Public.pdf Best Regards, Will

1 0

Exokernel / Device drivers
by William DUCK 20 Oct '06

20 Oct '06

Hello, The more I go forward, the more questions come to me : http://lists.tunes.org/archives/tunes/1995-June/000617.html the exokernel paper says somewhere that all the exokernel does is to securely multiplex the cpu (that's time) and memory (that's space) ressources. that's what you said you want from a good os in your `why ...' paper. and some months ago, i observed that the os may be viewed as a device driver for these two because that's what device drivers should do: securely multiplex some hardware ressource http://lists.gnu.org/archive/html/l4-hurd/2006-08/msg00005.html "In contract to our approach [L4], [Exokernel] is based on the philosophy that a kernel should /not/ provide abstractions but only a minimal set of primitives. Consequently, the Exokernel interface is architecture dependent . . . We believe that dropping the abstractional [sic] approach could only be justified by substantial performance gains. . . . It might turn out that the right abstractions are even more efficient than securely multiplexing hardware primitives or, on the other hand, that abstractions are too inflexible." http://tunes.org/wiki/Decentralized So would it be possible to build a general purpose OS without a kernel ? Isn't just a matter of language *and/or* hardware architecure ? Could we imagine a full application-level OS and link the apps directly to the drivers => so the "kernel" would be the device drivers framework ? Or at least the ressource management system ... Best Regards, Will

1 0

about L4Linux supporting for 312MHz Intel XScale Bulverde (PXA270) processor
by Wenbin Zhang 19 Oct '06

19 Oct '06

Hello, I notice in the L4Linux website, you mentioned that The ARM port currently runs on the following platforms: * PLEB The University of New South Wales' embedded hardware * Supports both PLEB1 (SA1100) and PLEB2 (XScale PXA255) * TuxScreen - StrongARM based phone platform. * Intel's IDXP450 Xscale development platform (XScale IXP450). Now I have a Motorola E680i cell phone, it is using 312MHz Intel XScale Bulverde (PXA270) processor, which is using the 5th generation of the ARM architecture. Is it supported by L4Linux currently? Thank you very much! Wenbin

2 1

Open /dev/console problem with the new l4linux-2.6.18 on Xscale
by WanKeun Jo 18 Oct '06

18 Oct '06

Hi, I first had tried to install l4linux-2.6.17 with fiasco kernel on Xscale. I got error which I already posted before on boot process. That was due to bugs in fiasco kernel, by Adam Lackorzynski's advice. so I updated Fiasco kernel & l4linux-2.6.18 from CVS. Again, I tried to boot, but failed with the following warning message: "Warning: Unable to open an initial console" After loading ramdisk on boot process, the system fail to look up the /dev/console file in ramdisk. So like before, I added devfs options to fs/Kconfig for mounting devfs filesystem again and then tried to boot, but failed.... You said before "enabling devfs option" is no option as it's gone with 2.6.18. "devfs" is completely obsoleted by "udev"?? Then How can I use devfs filesystem and succeed to open the initial console file and boot?? Thank you so much...

2 1

Cannot access to CVS
by ernesto bascon 17 Oct '06

17 Oct '06

I get the following errors trying to getting Fiasco from your remote CVS: eto@eto ~/l4/fiasco $ cvs -z3 -d :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs checkout l4linux-2.6 cvs checkout: Updating l4linux-2.6 cvs checkout: failed to create lock directory for `/home/remote-cvs/l4linux-2.6' (/home/remote-cvs/l4linux-2.6/#cvs.lock): Permission denied cvs checkout: failed to obtain dir lock in repository `/home/remote-cvs/l4linux-2.6' cvs [checkout aborted]: read lock failed - giving up Any ideas?

2 2

How does Fiasco implement hard real-time function?
by chenggh 17 Oct '06

17 Oct '06

Hi: I want to know how Fiasco implments the hard real-time function. Can you recommend some papers or souce code to me? Thank you. chenggh

2 1

Fiasco.image with debugging information
by 김광식 15 Oct '06

15 Oct '06

   Hi,    I work with fiasco kernel in arm platform.    I want to debug fiasco kernel with debugging tool.    But, I need to get fiasco kernel object with debuging information.    First I put this flags in Makefile.   ----------------------------------------------------  vi kernel/fiasco/build/Makefile ...  CFLAGS        += -g  CPPFLAGS += -g  SFLAGS += -g ... -----------------------------------------------------    after make, fiasco.image has no debugging information.    and also I try  this flags. no change. ----------------------------------------------------  vi kernel/fiasco/build/Makefile .. CARCHFLAGS_arm += -g CPPARCHFLAGS_arm += -g ASFLAGS_arm += -g ... -----------------------------------------------------    So I try to roottask(l4env).  I put this flags in config file. ----------------------------------------------------  vi l4/mk/modes.inc ... CARCHFLAGS_arm += -g CPPARCHFLAGS_arm += -g ASFLAGS_arm += -g ... -----------------------------------------------------  after make, roottask has a debugging information.    How can I get fiasco.image with debugging information?       

2 1

Boot problem with the new version of l4linux on Xscale
by WanKeun Jo 14 Oct '06

14 Oct '06

Hi! I tried to run Fiasco-L4Linux on Xscale board. I'm using L4Linux-2.6.17 version. First, I made a bootstap image (=bootstrap.raw) and loaded on Xscale and run it. But some server programs' ranges were overlapped, so I fixed some server programs' DEFAULT_RELOC_arm address, and then started working. During the boot process, "Warning: Unable to open an initial console" is warned and halt. I checked on boot process after ram disk is loaded, dev file path lookup fails.. So as to mount dev file system again after loading ram disk, I added "devfs options" to fs/Kconfig. And then the warning message is not presented. But after that, I got a new error message --------------------------------------------------------------------------------------------- Assertion failed: 'space() == current_space()' in /home/jowkju/project/Microkernel/Fiasco/Fiasco_Xscale/l4/kernel/fiasco/src/kern/thread- pagefault.cpp:82 at f0005400 --------------------------------------------------------------------------------------------- This error may occur during the "init" program in ram disk execute. However, there may not be errors in init program because it works well in the 2.6.16 version. And maybe the problem occurs during the context switching between "init" program and other threads... The following is the whole messages from boot starts. --------------------------------------------------------------------------------------------- Starting kernel... Hello from Startup::stage2 Initialize page table Vmem_alloc::init() allocated zero page @0xf0400000[phys=0xa3800000] Vmem_alloc::TEST allocate zero-mapped page... [0xefc00000] done free zero-mapped page... done allocate zero-filled page... [0xefc01000] done free zero-filled page... done allocate no-zero-filled page... [0xefc02000] done free no-zero-filled page... done SERIAL ESC: allocated IRQ 22 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco(arm)! DD-L4(x0)/arm microkernel (C) 1998-2006 TU Dresden Rev: Fri Sep 15 09:49:11 2006 compiled with gcc 3.4.4 for XScale SIGMA0[2.0]: Hello World! SIGMA0: KIP is at: a0001000 SIGMA0 free region: : a0000000, a3ffffff SIGMA0 alloc region: : a0000000, a003ffff owner: 1 SIGMA0 alloc region: : a004c000, a005f7ff owner: 1 SIGMA0 alloc region: : a3800000, a3ffffff owner: 1 Roottask. Command line found: "roottask task modname "bmodfs" module module module module module" 66172kB ( 64MB) total RAM (reported by bootloader) 56652kB ( 56MB) received RAM from Sigma0 7868kB ( 8MB) reserved RAM for RMGR Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:5 Roottask: Loading 12 modules. #05: loading "names" from [a146c000-a14761a4] to [a0109000-a0110e20][a0111000-a011b000] entry at a0041060 via trampoline page code #06: loading "log" from [a1477000-a148730c] to [a0160000-a0167f18][a0168000-a01956d4] entry at a004205c via trampoline page code #07: loading "dm_phys -v" from [a1488000-a14a61a4] to [a01b0000-a01c4c78][a01c5000-a01ce000] entry at a0043064 via trampoline page code #08: loading "simple_ts -t 10" from [a14a7000-a14ba30c] to [a0290000-a029a1f0][a029b000-a02a35a0] entry at a0044068 via trampoline page code #09: loading "l4exec" from [a14bb000-a14f71a4] to [a01e0000-a0212348][a0213000-a022c000] entry at a0045060 via trampoline page code #0a: loading "bmodfs" from [a14f8000-a151d1a4] to [a0240000-a025b0a8][a025c000-a0273000] passing module libloader.s.so [ a151e000-a1547eec ] passing module shared_test [ a1548000-a1549700 ] passing module vmlinuz26.arm [ a154a000-a173c5b4 ] passing module rd1 [ a173d000-a1b3d000 ] passing module l4linux.cfg [ a1b3d000-a1b3d0b0 ] entry at a00460ec via trampoline page code #0b: loading "loader --fprov=BMODFS l4linux.cfg" from [a1b3e000-a1b721a4] to [a02c0000-a02eaff4][a02eb000-a0309000] entry at a004707c via trampoline page code simplets| Configured for 10 tasks. DMphys | DMphys memory map: DMphys | phys. memory 0xa0000000-0xa4000000 (from L4 kernel info page) DMphys | using 0xa0000000-0xa4000000 DMphys | Memory area Pool PS Flags DMphys | 0xa0000000-0xa0068000 -- -- RESERVED DMphys | 0xa0068000-0xa00bb000 -- -- DENIED DMphys | 0xa00bb000-0xa00cf000 -- -- RESERVED DMphys | 0xa00cf000-0xa0109000 0 12 MAPPED DMphys | 0xa0109000-0xa011b000 -- -- DENIED DMphys | 0xa011b000-0xa0160000 0 12 MAPPED DMphys | 0xa0160000-0xa0196000 -- -- DENIED DMphys | 0xa0196000-0xa01b0000 0 12 MAPPED DMphys | 0xa01b0000-0xa01cd000 -- -- RESERVED DMphys | 0xa01cd000-0xa01e0000 0 12 MAPPED DMphys | 0xa01e0000-0xa022c000 -- -- DENIED DMphys | 0xa022c000-0xa0240000 0 12 MAPPED DMphys | 0xa0240000-0xa0273000 -- -- DENIED DMphys | 0xa0273000-0xa0290000 0 12 MAPPED DMphys | 0xa0290000-0xa02a4000 -- -- DENIED DMphys | 0xa02a4000-0xa02c0000 0 12 MAPPED DMphys | 0xa02c0000-0xa0309000 -- -- DENIED DMphys | 0xa0309000-0xa0400000 0 12 MAPPED DMphys | 0xa0400000-0xa1500000 0 20 MAPPED DMphys | 0xa1500000-0xa151e000 0 12 MAPPED DMphys | 0xa151e000-0xa1b3e000 -- -- DENIED DMphys | 0xa1b3e000-0xa1c00000 0 12 MAPPED DMphys | 0xa1c00000-0xa3800000 0 20 MAPPED DMphys | 0xa3800000-0xa4000000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 48960KB total, 48960KB free, 32KB reserved DMphys | 0xa00cf000-0xa0109000 ( 232KB, 0MB) DMphys | 0xa011b000-0xa0160000 ( 276KB, 0MB) DMphys | 0xa0196000-0xa01b0000 ( 104KB, 0MB) DMphys | 0xa01cd000-0xa01e0000 ( 76KB, 0MB) DMphys | 0xa022c000-0xa0240000 ( 80KB, 0MB) DMphys | 0xa0273000-0xa0290000 ( 116KB, 0MB) DMphys | 0xa02a4000-0xa02c0000 ( 112KB, 0MB) DMphys | 0xa0309000-0xa151e000 ( 18516KB, 18MB) DMphys | 0xa1b3e000-0xa3800000 ( 29448KB, 29MB) bmodfs | Passed the following modules: bmodfs | module "libloader.s.so" (168kB) bmodfs | module "shared_test" (6kB) bmodfs | module "vmlinuz26.arm" (1994kB) bmodfs | module "rd1" (4096kB) bmodfs | module "l4linux.cfg" (1kB) loader | sleeping for 1000 ms exec | vmlinuz26.arm: Loading exec | vmlinuz26.arm: Interpreter section found, contains "/usr/lib/ld.so.1" exec | vmlinuz26.arm: Has no symbols exec | vmlinuz26.arm: Has no lines exec | libloader.s.so: Loading exec | libloader.s.so: Has no symbols exec | libloader.s.so: Has no lines exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol l4sys_fixup_abs_syscalls is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00006400 => 00016400 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26.arm: Setting section flag 0800 loader | vmlinuz26.arm: Starting l4env-style application loader | vmlinuz26.arm,#c: Starting at l4loader_init (00016440) exec | vmlinuz26.arm: Linking exec | vmlinuz26.arm: Relocating entry 00216000 => 00216000 loader | vmlinuz26.arm,#c: Continue at l4env_init (00016b60, libloader.s.so) l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (jowkju@jowk) (gcc version 3.4.4) #44 Sat Oct l4lx : 14 12:21:10 KST 2006 l4lx | Binary name: vmlinuz26.arm l4lx | Kernel command line (9 args): root=1:0 mem=16M load_ramdisk=1 ramdisk l4lx : _size=4096 l4env_rd=rd1 console=ttyLv0 l4ser.vkey_irq=46 panicblink=0 l4lx : lang=us l4lx | Image: 00200000 - 00434000 [2256 KiB]. l4lx | Areas: Text: 00200000 - 0039c000 [1648kB] (a bit longer) l4lx | Data: 0039c000 - 003e2fb0 [283kB] l4lx | Initdata: 00200000 - 00215000 [84kB] l4lx | BSS: 003e8000 - 00434000 [304kB] l4lx | l4lx_thread_create: Created thread 0c.03 (tamer) l4lx | Using tamed mode. l4lx | l4lx_thread_create: Created thread 0c.04 (server) l4lx | main thread will be 0c.04 l4lx | l4env_register_pointer_section: addr = 00200000 size = 2310144 l4lx | sec-w-init: virt: 0x00200000 to 0x00433fff [2256 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 4, 2310144 Bytes l4lx | l4env_linux_startup thread 4. l4lx | sec-w-init: 1: Phys: 0xa0309000 to 0xa04a1000, Size: 1671168 l4lx | sec-w-init: 2: Phys: 0xa011b000 to 0xa0160000, Size: 282624 l4lx | sec-w-init: 3: Phys: 0xa00cf000 to 0xa0109000, Size: 237568 l4lx | sec-w-init: 4: Phys: 0xa0273000 to 0xa0290000, Size: 118784 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 16MB l4lx | Main memory: virt: 0x00500000 to 0x014fffff [16384 KiB] l4lx | Main memory: Number of physical regions: 1, 16777216 Bytes l4lx | Main memory: 1: Phys: 0xa2800000 to 0xa3800000, Size: 16777216 l4lx | Filling lower ptabs... l4lx | Done (650 entries). l4lx | l4env_rd_path: rd1 l4lx | Loading: rd1 l4lx | INITRD: Size of RAMdisk is 4096KiB l4lx | RAMdisk from 01500000 to 01900000 [4096KiB] l4lx | l4lx_thread_create: Created thread 0c.05 (IRQ CPU0) l4lx | l4lx_thread_create: Created thread 0c.06 (timer.i0) Linux version 2.6.17-l4 (jowkju@jowk) (gcc version 3.4.4) #44 Sat Oct 14 12:21:10 KST 2006 CPU: Fiasco [0001f000] revision 0 (ARMv4) cpu_sa1100_proc_init Machine: L4 Memory policy: ECC disabled, Data cache writeback CPU0: D write-through cache CPU0: cache: 512 bytes, associativity 1, 8 byte lines, 64 sets INITRD: 01500000 - 01900000 Built 1 zonelists Kernel command line: root=1:0 mem=16M load_ramdisk=1 ramdisk_size=4096 l4env_rd=rd1 console=ttyLv0 l4ser.vkey_irq=46 panicblink=0 lang=us l4lx_irq_init: l4lx_irq_max = 50 l4lx_irq_init: creating IRQ thread on cpu 0 irq_thread: Starting IRQ thread on CPU 0 PID hash table entries: 128 (order: 7, 512 bytes) l4lx_irq_timer_startup(0) timer_irq_thread: Starting timer IRQ thread. l4ser_init_ports Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 5MB 16MB = 21MB total Memory: 16152KB available (1556K code, 608K data, 84K init) Mount-cache hash table entries: 512 ROOT FS, MOUNT TREE INITIALIZATION COMPLETED checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd INITRD: Freeing memory. NET: Registered protocol family 16 NET: Registered protocol family 2 l4lx | l4lx_thread_create: Created thread 0c.07 (Idler) IP route cache hash table entries: 256 (order: -2, 1024 bytes) TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 512 (order: -1, 2048 bytes) TCP: Hash tables configured (established 1024 bind 512) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) devfs: 2004-01-31 Richard Gooch (rgooch(a)atnf.csiro.au) devfs: devfs_debug: 0x0 devfs: boot_options: 0x1 io scheduler noop registered (default) L4 serial driver l4ser_init_ports ttyLv0 at MMIO 0x1 (irq = 46) is a L4 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize nbd: registered device at major 43 ts: Compaq touchscreen protocol output TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 4096KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) readonly. Mounted devfs on /dev execve for /sbin/init Allocated 0d.00 Assertion failed: 'space() == current_space()' in /home/jowkju/project/Microkernel/Fiasco/Fiasco_Xscale/l4/kernel/fiasco/src/kern/thread-pagefault.cpp:82 at f0005400 Return reboots, "k" enters L4 kernel debugger... BUG: soft lockup detected on CPU#0! --------------------------------------------------------------------------------------------- How can I solve this problem?? One thing to notice is that there's no problem like the above in the previous version of l4linux. In the previous version, boot process works well. Again, how can I solve this problem?? Thank you

2 1

how-to questions
by Ratko Rudič 11 Oct '06

11 Oct '06

Hello again, while playing with l4 I got couple of (easy) questions. 1. Can DOpE write a log anywhere on filesystem? 2. Where can I see how much memory I can assign to vmlinuz (how much memory uses DOpE and L4)? 3. What are those 4 slide bars by the linux window in DOpE? 4. How can I run more that one Linux process? 5. Can I use pistachio in place of fiasco? If so, how? 6. How do I halt L4 and DOpE? Hope it's not too much to answer. ratko

4 5

vbe info block
by Ratko Rudič 09 Oct '06

09 Oct '06

Helo again, The boot process (with dresdens's grub) stops with: "Did not found VBE info block in multiboot info. Grub has to set the video mode with the vbset command" vbeprobe in grub returns: 0x109, 0x10a, 0x10b, 0x10c I tried with "vbeset 0x117", "vbeset 0x109" and "vbeset 0x10c" in menu.lst, but get: "Mode 0x117 is not supported" Then I tried with debian's grub 0.95 but it doesnt recognize "modaddr". Any ideas? ratko

2 2

crt0_tramppage
by Ratko Rudič 07 Oct '06

07 Oct '06

Hi all! In the last stage of L4Linux-2.6 compile I get "undefined reference to crt0_tramppage" and similar crt0 errors. /usr/.../l4v2/libloader.s.so: undefined reference to 'crt0_tramppage'. .... What am I missing? I searched 2006 and 2005 archives and found a post on "Thu Feb 24 11:01:11 2005" but no definite answer that would help me. Greetings, Ratko Rudič

4 3

Assertion failed in Fiasco-UX
by Marcel Winandy 06 Oct '06

06 Oct '06

Hello! When I try to start fiasco-ux on my Linux system, it stops with the following message: ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /DROPS/l4/kernel/fiasco-ux/src/kern/ux/hostproc.cpp:120 If I run the same binaries on different machines there is no problem and fiasco-ux starts as expected. The only difference between my machine and the others seems to be a different hosting Linux kernel. Are there any Linux-specific problems known? I am not sure, but this seems to be a bug in fiasco-ux. Kind regards, Marcel -- Marcel Winandy http://www.prosec.rub.de/staff/winandy.html Applied Data Security Group, Ruhr-University Bochum, Germany

2 2

L4 and ARM TrustZone
by Francis M. David 06 Oct '06

06 Oct '06

Is anyone looking at how TrustZone can be used in NICTA's ARM implementation? -Francis

2 1

TFTP does not work with QEMU
by Daniel Vandersee 05 Oct '06

05 Oct '06

Hello, when I try to run tftp under QEMU 0.8.2 with an emulated pcnet or ne2k-pci network card I get the following error. However, tftp under VMWare works just fine. Any help would be appreciated. Kind regards, Daniel > names | Starting thread listening for `exit' events > simplets| Configured for 30 tasks. > rtc | Date:02.10.2006 Time:14:42:15 > io | do_args(): Disabling internal IRQ handling. > tftp | NICs supported: E1000, EEPRO100, NE2000/PCI, PCNET32/PCI, RTL8139, > tftp | Tulip, VIA 86C100 > io | PCI: Using configuration type 1 > io | PCI: Probing PCI hardware > io | PCI: Probing PCI hardware (bus 00) > > KERNEL: d.3 (tcb=c0341800) killed: > Unhandled trap > > EAX 12378000 EBX 000f0000 ECX 00000000 EDX 00009fa0 > ESI 00000000 EDI 01044e30 EBP 0102ff8c ESP 0102ff7c > EIP 000f9f9b EFLAGS 00013206 > CS 001b SS 0023 DS 0023 ES 0023 FS 0023 GS 0043 > trap 13 (General Protection), error 00000018, from user mode > (internal event regarding GDT entry no. 0x03) > io | PCI: PIIX3: Enabling Passive Release on 00:01.0 > io | Limiting direct PCI/PCI transfers. > io | Activating ISA DMA hang workarounds. > io | 00000000-ffffffff : PCI mem > io | e0000000-e07fffff : PCI device 1234:1111 (Technical Corp.) > io | e1000000-e100001f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LA > io : NCE] > io | 0000-ffff : PCI IO > io | 0cf8-0cff : PCI conf1 > io | b000-b03f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI > io | c000-c00f : Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] > io | c020-c03f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]

3 4

Difference between Fiasco and L4Linux...
by Dustin Oprea 02 Oct '06

02 Oct '06

I think I'm missing something really obvious, but what's the difference between Fiasco and L4Linux... It appears they're made by the same group. I use QNX RTOS at work, and I'm interested in using the microkernel instead of the full-on monolothic kernel at home with my Fedora installation. What goes in first: Fiasco, or L4Linux? Dustin Oprea

2 1

Re: Difference between Fiasco and L4Linux...
by chenggh 02 Oct '06

02 Oct '06

On Monday 02 October 2006 10:46, Dustin Oprea wrote: > I think I'm missing something really obvious, but what's the difference > between Fiasco and L4Linux... It appears they're made by the same group. Fiasco is the microkernel but L4Linux is not. L4Linux is the variation of Linux kernel running on top of Fiasco and it is loaded as the module of Fiasco when running. They made the L4Linux in order to have a good portability of Linux application into the L4/Fiasco. > I use QNX RTOS at work, and I'm interested in using the microkernel > instead of the full-on monolothic kernel at home with my Fedora > installation. What goes in first: Fiasco, or L4Linux? First you must compile the Fiasco and L4Linux of course you need a modified grub version to boot the Fiasco successfully. I think you should download all the souce code of L4 and L4Linux and try to compile. :) chenggh

1 0

L4Linux on Xscale
by 조완근 01 Oct '06

01 Oct '06

Hi, Sorry, I forgot to say that I tried arm-linux-gcc version 2.95.3, 3.3.1, 3.4.4.. but all the results are same...   Thank you..

2 1

L4Linux on Xscale
by Wan-Keun Jo 30 Sep '06

30 Sep '06

Hi, I tried to install Fiasco-L4Linux on Xscale-PXA255. I saw a "hello message" with fiasco kernel, sigma0, roottask, hello programs yesterday. When I start to compile L4linux, I got the following errors... ================================================================== /l4linux-2.6$ make CHK include/linux/version.h CC arch/l4/kernel/asm-offsets.s cc1: error: invalid option `abi=apcs-gnu' (1) cc1: error: bad value (armv4) for -march= switch (2) cc1: error: bad value (armv4) for -mcpu= switch make[1]: *** [arch/l4/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 ================================================================== >> Question 01: Error (1): I solved by fixing the following code arch/l4/Makefile:77: CFLAGS_ABI :=$(call cc-option,-mapcs-32,-mabi=apcs-gnu) $(call cc-option,-mno-thumb- interwork,) [change to] CFLAGS += $(call cc-option,-mapcs-32,$(call cc-option,-mabi=apcs-gnu),) $(call cc-option, -mno-thumb-interwork,) Error (1) is solved, but what is the difference between them?? (I just fix it, I don't know why...) >> Question 02: Error (2): I read what "-march" option is on gcc manual, and found the permissible values for it are armv2, armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, armv6, armv6j, iwmmxt, ep9312 In the file "arch/l4/Makefile:82 CFLAGS += -D__LINUX_ARM_ARCH__=4 -march=armv4" I just tried each values one by one for -march option, but all failed. How can I fix it and compile well??? Thank you!!

1 0

L4Linux and USB mass storage
by Andreas Niederl 26 Sep '06

26 Sep '06

Hi, I'm having problems using a USB connected mass storage device with L4Linux. On device detection an out of memory error happens when the cache is allocated: NET: Registered protocol family 1 NET: Registered protocol family 17 Waiting 15sec before mounting root device... l4lx | l4lx_thread_create: Created thread 0e.0c (IRQ1) input: AT Translated Set 2 keyboard as /class/input/input0 logips2pp: Detected unknown logitech mouse model 1 input: PS/2 Logitech Mouse as /class/input/input1 Vendor: ST325082 Model: 3AS Rev: Type: Direct-Access ANSI SCSI revision: 02 oom-killer: gfp_mask=0xd1, order=0 <0040a605> show_trace+0x15/0x20 <0040a6f7> dump_stack+0x17/0x20 <0043227b> out_of_memory+0x6b/0x90 <0043336c> __alloc_pages+0x26c/0x2a0 <004469d4> kmem_getpages+0x34/0xa0 <00447689> cache_grow+0x99/0x180 <004478ed> cache_alloc_refill+0x17d/0x1c0 <00447af8> kmem_cache_alloc+0x48/0x5 0 <00571fbc> sd_revalidate_disk+0x2c/0x100 <005722ad> sd_probe+0x21d/0x310 <00512244> driver_probe_device+0x54/0xb0 <005122b0> __device_attach+0x10/0x20 <005118db> bus_for_each_drv+0x4b/0x70 <00512314> device_attach+0x54/0x60 <00511a05> bus_add_device+0x25/0x90 <00510a5a> device_add+0xda/0x160 <0056da33> scsi_sysfs_add_sdev+0x33/0x180 <0056bef9> scsi_add_lun+0x199/0x360 <0056c1db> scsi_probe_and_add_lun+0x11b/0x200 <0056c9b1> __scsi_scan_target+0xa1/0xe0 <0056caec> scsi_scan_channel+0x6c/0x90 <0056cb76> scsi_scan_host_selected+0x66/0xb0 <0056cbd4> scsi_scan_host+0x14/0x20 <00594dee> usb_stor_scan_thread+0x4e/0x150 <00424994> kthread+0x94/0xc0 <00407619> kernel_thread_start+0x29/0x30 <004075ee> ret_kernel_thread_start+0x6/0x8 I'm using L4Linux-2.6.17 and tried it on a machine with 512MB memory with 256MB reserved for L4Linux as well as on a machine with 1GB memory and 768MB for L4Linux. Delaying the device detection by booting into a Ramdisk and then loading the respective modules and udev resulted in the same behaviour. Has anybody else experienced such problems when using USB disks with L4Linux? Regards, Andi

2 2

IO address acess on L4linux for ARM
by 김광식 23 Sep '06

23 Sep '06

   IO peripheral Address region in my platform is 0xfffb0000 - 0xfffeffff    I want to add device driver in L4linux.    in L4linux device driver  ...  *(volatile unsigned char *)0xfffb0000 = 'c';  ...    following case made error result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f 0000003600000037 failed CLI: 0000000c.00000004    How can I access IO Address?

2 1

Re: Maybe it is a bug of L4/Fiasco or L4Linux
by chenggh 19 Sep '06

19 Sep '06

On Tuesday 19 September 2006 04:17, Adam Lackorzynski wrote: > Hi, > > On Mon Sep 18, 2006 at 11:19:27 +0800, chenggh wrote: > > When I use netpipe to test the performance of L4Linux based on top of > > L4/Fiasco there is something as following: > > > > kernel BUG at include/linux/netdevice.h:886! > > Trap: 6: 0000 [#1] > > Modules linked in: > > CPU: 0 > > EIP: f032:[<0056f317>] Not tainted VLI > > EFLAGS: 00013246 (2.6.17-l4 #1) > > EIP is at rtl8139_poll+0xd7/0xf0 > > eax: 00000006 ebx: 0001d43c ecx: 0000c07f edx: 0000d43c > > esi: 01331400 edi: b09fff10 ebp: b09fff00 esp: b09ffedc > > ds: 4000 es: ea0c ss: 0000 > > Process swapper (pid: 0, threadinfo=b09fe000 task=0066b940) > > Stack: 01331400 01331660 00000040 00000001 0001d400 01331660 013314c0 > > 01331400 00003e13 b09fff20 005a8262 01331400 b09fff10 0000012c 00000001 > > 007207d8 0000000a b09fff38 0041a7a9 007207d8 00000000 0000000c 00000000 > > b09fff48 Call Trace: > > <0040bec0> show_stack_log_lvl+0x90/0xc0 <0040c08b> > > show_registers+0x14b/0x1c0 > > <0040c2bd> die+0xfd/0x200 <00000000> _start+0xffc00000/0x50 > > <005a8262> net_rx_action+0x72/0x110 <0041a7a9> __do_softirq+0x49/0xb0 > > <00407bc8> do_softirq+0x48/0x50 <0041a8c5> irq_exit+0x35/0x40 > > <00407993> do_IRQ+0x23/0x30 <0050b052> irq_thread_hw+0x1f2/0x330 > > <a00a8a4c> 0xa00a8a4c <a00abc76> 0xa00abc76 > > Code: 41 04 00 02 20 00 c7 86 c0 00 00 00 00 01 10 00 0f ba 76 2c 05 e8 > > 4a 4a e9 ff 31 c0 83 7d e8 00 0f 94 c0 83 c4 18 5b 5e 5f c9 c3 <0f> 0 > > b 76 03 e0 03 64 00 eb b6 eb 0d 90 90 90 90 90 90 90 90 90 > > EIP: [<0056f317>] rtl8139_poll+0xd7/0xf0 SS:ESP 0023:b09ffed4 > > <0>Kernel panic - not syncing: Fatal exception in interrupt > > panic: going to sleep forever, bye > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 107084 dirty entry 107080. > > eth1: Tx descriptor 0 is 0008a042. (queue head) > > eth1: Tx descriptor 1 is 0008a042. > > eth1: Tx descriptor 2 is 0008a5ea. > > eth1: Tx descriptor 3 is 0008a5ea. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 4 dirty entry 0. > > eth1: Tx descriptor 0 is 0008a4ef. (queue head) > > eth1: Tx descriptor 1 is 0008a5ea. > > eth1: Tx descriptor 2 is 0008a5ea. > > eth1: Tx descriptor 3 is 0008a5ea. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 4 dirty entry 0. > > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > > eth1: Tx descriptor 1 is 0008a5ea. > > eth1: Tx descriptor 2 is 0008a5ea. > > eth1: Tx descriptor 3 is 0008a5ea. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 4 dirty entry 0. > > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > > eth1: Tx descriptor 1 is 0008a03c. > > eth1: Tx descriptor 2 is 0008a03c. > > eth1: Tx descriptor 3 is 0008a03c. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > > > And every time the netpipe program don't exit normally and the L4Linux > > is dead so that I must reboot it again. Maybe it is a bug but I am not > > sure. Thank you. > > Hard to tell what's going wrong here, I guess I need to reproduce this > to say anything about this. This is some Realtek 100Mbit NIC, right? Do > you give any special options to NPtcp? > Are both sides L4Linux or just one, if the latter, which side? > > > > Adam In the sender I use command as "./NPtcp -h receive_ip -o mylog" and in the receiver I only use "./NPtcp". Oh, I use two different types netcard, Realtek 100Mbit and Intel 1000M. When I use Realtek or Intel anyway as the sender port the error information is same. I only use one L4Linux as a bridge and the structure is like this: Slackware 10.2 <-------------> L4Linux/Fiasco <-------------> Slackware 10.1 192.168.1.2(sender) <------->192.168.1.1 192.168.0.1<------------------->192.168.0.2(receiver) 192.168.1.2(receiver) <------->192.168.1.1 192.168.0.1<------------------->192.168.0.2(sender) In the L4Linux/Fiasco I use two different ethernet card as Realtek 100M and Intel 1000M. The error information is from the minicom log. And in this test the NPtcp application doesn't exit normally and I have to reboot when the minicom has the error information. Thank you. chenggh

1 0

Re: Maybe it is a bug of L4/Fiasco or L4Linux
by Adam Lackorzynski 18 Sep '06

18 Sep '06

Hi, On Mon Sep 18, 2006 at 11:19:27 +0800, chenggh wrote: > When I use netpipe to test the performance of L4Linux based on top of > L4/Fiasco there is something as following: > > kernel BUG at include/linux/netdevice.h:886! > Trap: 6: 0000 [#1] > Modules linked in: > CPU: 0 > EIP: f032:[<0056f317>] Not tainted VLI > EFLAGS: 00013246 (2.6.17-l4 #1) > EIP is at rtl8139_poll+0xd7/0xf0 > eax: 00000006 ebx: 0001d43c ecx: 0000c07f edx: 0000d43c > esi: 01331400 edi: b09fff10 ebp: b09fff00 esp: b09ffedc > ds: 4000 es: ea0c ss: 0000 > Process swapper (pid: 0, threadinfo=b09fe000 task=0066b940) > Stack: 01331400 01331660 00000040 00000001 0001d400 01331660 013314c0 01331400 > 00003e13 b09fff20 005a8262 01331400 b09fff10 0000012c 00000001 007207d8 > 0000000a b09fff38 0041a7a9 007207d8 00000000 0000000c 00000000 b09fff48 > Call Trace: > <0040bec0> show_stack_log_lvl+0x90/0xc0 <0040c08b> > show_registers+0x14b/0x1c0 > <0040c2bd> die+0xfd/0x200 <00000000> _start+0xffc00000/0x50 > <005a8262> net_rx_action+0x72/0x110 <0041a7a9> __do_softirq+0x49/0xb0 > <00407bc8> do_softirq+0x48/0x50 <0041a8c5> irq_exit+0x35/0x40 > <00407993> do_IRQ+0x23/0x30 <0050b052> irq_thread_hw+0x1f2/0x330 > <a00a8a4c> 0xa00a8a4c <a00abc76> 0xa00abc76 > Code: 41 04 00 02 20 00 c7 86 c0 00 00 00 00 01 10 00 0f ba 76 2c 05 e8 4a 4a > e9 ff 31 c0 83 7d e8 00 0f 94 c0 83 c4 18 5b 5e 5f c9 c3 <0f> 0 > b 76 03 e0 03 64 00 eb b6 eb 0d 90 90 90 90 90 90 90 90 90 > EIP: [<0056f317>] rtl8139_poll+0xd7/0xf0 SS:ESP 0023:b09ffed4 > <0>Kernel panic - not syncing: Fatal exception in interrupt > panic: going to sleep forever, bye > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 107084 dirty entry 107080. > eth1: Tx descriptor 0 is 0008a042. (queue head) > eth1: Tx descriptor 1 is 0008a042. > eth1: Tx descriptor 2 is 0008a5ea. > eth1: Tx descriptor 3 is 0008a5ea. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 4 dirty entry 0. > eth1: Tx descriptor 0 is 0008a4ef. (queue head) > eth1: Tx descriptor 1 is 0008a5ea. > eth1: Tx descriptor 2 is 0008a5ea. > eth1: Tx descriptor 3 is 0008a5ea. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 4 dirty entry 0. > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > eth1: Tx descriptor 1 is 0008a5ea. > eth1: Tx descriptor 2 is 0008a5ea. > eth1: Tx descriptor 3 is 0008a5ea. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 4 dirty entry 0. > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > eth1: Tx descriptor 1 is 0008a03c. > eth1: Tx descriptor 2 is 0008a03c. > eth1: Tx descriptor 3 is 0008a03c. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > > And every time the netpipe program don't exit normally and the L4Linux is > dead so that I must reboot it again. Maybe it is a bug but I am not sure. > Thank you. Hard to tell what's going wrong here, I guess I need to reproduce this to say anything about this. This is some Realtek 100Mbit NIC, right? Do you give any special options to NPtcp? Are both sides L4Linux or just one, if the latter, which side? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

L4 Bootimage tools
by Spring, Ryan C 18 Sep '06

18 Sep '06

Which tools are available to generate monolithic bootimages for l4 on platforms that don't support elf? I have seen the dite tool from NICTA; are there also other options? Thanks, Ryan Spring --- Ryan Spring Doctoral Student University of Texas at El Paso (UTEP) Cell: +1 915-539-7311 (when in USA) Alt Cell: +49 179-9624406 (when in Germany) http://www.spring-west.net/ryan Auch aus Steinen, die einem in den Weg gelegt werden, kann man Schönes bauen. J.W. Goethe

2 1

Maybe it is a bug of L4/Fiasco or L4Linux
by chenggh 18 Sep '06

18 Sep '06

Hi, everyone: When I use netpipe to test the performance of L4Linux based on top of L4/Fiasco there is something as following: kernel BUG at include/linux/netdevice.h:886! Trap: 6: 0000 [#1] Modules linked in: CPU: 0 EIP: f032:[<0056f317>] Not tainted VLI EFLAGS: 00013246 (2.6.17-l4 #1) EIP is at rtl8139_poll+0xd7/0xf0 eax: 00000006 ebx: 0001d43c ecx: 0000c07f edx: 0000d43c esi: 01331400 edi: b09fff10 ebp: b09fff00 esp: b09ffedc ds: 4000 es: ea0c ss: 0000 Process swapper (pid: 0, threadinfo=b09fe000 task=0066b940) Stack: 01331400 01331660 00000040 00000001 0001d400 01331660 013314c0 01331400 00003e13 b09fff20 005a8262 01331400 b09fff10 0000012c 00000001 007207d8 0000000a b09fff38 0041a7a9 007207d8 00000000 0000000c 00000000 b09fff48 Call Trace: <0040bec0> show_stack_log_lvl+0x90/0xc0 <0040c08b> show_registers+0x14b/0x1c0 <0040c2bd> die+0xfd/0x200 <00000000> _start+0xffc00000/0x50 <005a8262> net_rx_action+0x72/0x110 <0041a7a9> __do_softirq+0x49/0xb0 <00407bc8> do_softirq+0x48/0x50 <0041a8c5> irq_exit+0x35/0x40 <00407993> do_IRQ+0x23/0x30 <0050b052> irq_thread_hw+0x1f2/0x330 <a00a8a4c> 0xa00a8a4c <a00abc76> 0xa00abc76 Code: 41 04 00 02 20 00 c7 86 c0 00 00 00 00 01 10 00 0f ba 76 2c 05 e8 4a 4a e9 ff 31 c0 83 7d e8 00 0f 94 c0 83 c4 18 5b 5e 5f c9 c3 <0f> 0 b 76 03 e0 03 64 00 eb b6 eb 0d 90 90 90 90 90 90 90 90 90 EIP: [<0056f317>] rtl8139_poll+0xd7/0xf0 SS:ESP 0023:b09ffed4 <0>Kernel panic - not syncing: Fatal exception in interrupt panic: going to sleep forever, bye NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 107084 dirty entry 107080. eth1: Tx descriptor 0 is 0008a042. (queue head) eth1: Tx descriptor 1 is 0008a042. eth1: Tx descriptor 2 is 0008a5ea. eth1: Tx descriptor 3 is 0008a5ea. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 4 dirty entry 0. eth1: Tx descriptor 0 is 0008a4ef. (queue head) eth1: Tx descriptor 1 is 0008a5ea. eth1: Tx descriptor 2 is 0008a5ea. eth1: Tx descriptor 3 is 0008a5ea. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 4 dirty entry 0. eth1: Tx descriptor 0 is 0008a5ea. (queue head) eth1: Tx descriptor 1 is 0008a5ea. eth1: Tx descriptor 2 is 0008a5ea. eth1: Tx descriptor 3 is 0008a5ea. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 4 dirty entry 0. eth1: Tx descriptor 0 is 0008a5ea. (queue head) eth1: Tx descriptor 1 is 0008a03c. eth1: Tx descriptor 2 is 0008a03c. eth1: Tx descriptor 3 is 0008a03c. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out And every time the netpipe program don't exit normally and the L4Linux is dead so that I must reboot it again. Maybe it is a bug but I am not sure. Thank you. chenggh

1 0

The fiasco kernel and roottask I build are too large to put in the floppy.
by Zheng Da 17 Sep '06

17 Sep '06

I found the two files in drops-demo-floppydisk-current.img are quite small. -rwxr-xr-x 1 root root 166060 2005-08-15 15:53 fiasco -rwxr-xr-x 1 root root 61545 2005-08-15 15:41 roottask But the ones I build are so large that there are on enough space for them in the floppy. -rwxr-xr-x 1 zhengda zhengda 639K 2006-09-16 00:25 bin/x86_586/l4v2/roottask -rwxr-xr-x 1 zhengda zhengda 358K 2006-09-16 00:08 l4/kernel/fiasco/build/main I got fiasco from CVS, and followed the steps showed in http://os.inf.tu-dresden.de/fiasco/use.html I want to create a hard disk image, and then there will be enough space. Unfortunately, I don't know how to create a hard disk image. So does anyone have some ideas? Thank you.

2 1

PXE enabled GRUB
by Adam Lackorzynski 15 Sep '06

15 Sep '06

Hi, this might be of interest to you. I have added PXE network driver support for my GRUB patch set recently. This enables GRUB to load files via the network using any PXE capable NIC, including latest e1000, Broadcom, e100, 3coms, etc. cards. The patch, README and binary are at the usual place at: http://os.inf.tu-dresden.de/~adam/grub/0.97/ Refer to the README file for details. If you have a NIC that has PXE and does not work, please let me know. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

List of L4Linux kernel parameters
by Andreas Niederl 15 Sep '06

15 Sep '06

Hi, does a list of the L4Linux kernel parameters (e.g. l4ser.vkey_irq) exist somewhere? Regards, Andi

3 3

Drops BID questions
by Andreas Niederl 14 Sep '06

14 Sep '06

Hi, the Building DROPS HOWTO states that by executing 'make' in the l4 directory everything will be built including Fiasco. My first question now is if there are any prerequisites for the BID to include Fiasco building, because Fiasco doesn't get touched by the BID for me. I also wanted to ask if Fiasco is included in the install target of the top-directory Makefile and if there are any plans to include an install target for L4Linux. For the latter, I've already made up something by reusing a slightly modified arch/i386/boot/install.sh script and added install targets to the Makefiles in arch/l4 and arch/l4/boot. Regards, Andi

2 3

get error when compiling fiasco-1.1 with gcc 4.1.2
by Zheng Da 14 Sep '06

14 Sep '06

I got fiasco-1.1-oskit.tar.bz2.tar and fiasco-1.1.tar.bz2.tar, and unpacked them into one directory. I have build the kernel successfully with gcc 3.x. But when my gcc updated to 4.1.2, I can't build the kernel at all. The two tar-balls are unpacked to the directory /storage/soft/l4/tmp/fiasco- 1.1 And the error I got is as follow: make[3]: Entering directory `/storage/soft/l4/tmp/fiasco-1.1/oskit/libkern' gcc -c -MD -DHAVE_CONFIG_H -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -iquote -I.. -I.. -I../flux/c -nostdinc -g -O2 -march=i586 -Wall ../libkern/x86/base_cpu_init.c In file included from ../libkern/x86/base_cpu_init.c:22: ../flux/x86/base_trap.h:105: error: array type has incomplete element type make[3]: *** [base_cpu_init.o] Error 1 make[3]: Leaving directory `/storage/soft/l4/tmp/fiasco-1.1/oskit/libkern' make[2]: *** [libkern/all.MAKE] Error 2 make[2]: Leaving directory `/storage/soft/l4/tmp/fiasco-1.1/oskit' make[1]: *** [all] Error 2 make[1]: Leaving directory `/storage/soft/l4/tmp/fiasco-1.1/oskit' make: *** [../oskit] Error 2 Quite strange. Does anyone compile fiasco1.1 successfully with gcc 4.x?

2 3

Documentation generation and the build directory
by Andreas Niederl 12 Sep '06

12 Sep '06

Hi, I am using a build directory for building L4Env (O=build in Makeconf.local) and I am getting errors about missing files from the documentation rather often. An example would be: ! LaTeX Error: File `dataspaces' not found. I then have to manually copy the file from the documentation directory to the subdirectory of the build directory as in cp doc/l4env-concept/dataspaces.fig build/doc/l4env-concept Is this normal behaviour or am I doing something wrong, such that the files don't get copied to the subdirectory in build? Regards, Andi

2 2

As a beginner, hello, not working due to trap...
by WanKeun Jo 11 Sep '06

11 Sep '06

Hello, I'm WanKeun Jo. Thank you for your response, Adam Lackorzynski .. I attach more info about my system... >> grub's config file. ------------------------------------------------------ title Hello_World kernel (hd0,5)/fiasco/bootstrap -comport 1 -serial modaddr 0x02000000 module (hd0,5)/fiasco/fiasco -nokdb module (hd0,5)/fiasco/sigma0 module (hd0,5)/fiasco/roottask module (hd0,5)/fiasco/hello ------------------------------------------------------ >> Error Messages ----------------------------------------------------------------------- ......... 64 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 16384 bytes (4 pages) EAX 00000000 EBX 00000014 ECX 00000005 EDX f0019e3d ESI 00000001 EDI 00004000 EBP f001ba08 ESP f001b9fc EIP f0012634 EFLAGS 00200046 CS 0008 SS 0010 DS 0023 ES 0023 FS 0023 GS 0023 trap 3 (Breakpoint), error 00000000, from kernel mode Panic: terminated due to trap Return reboots, "k" enters L4 kernel debugger... Rebooting ----------------------------------------------------------------------- >> My kernel configuration file http://dongtak.postech.ac.kr/~jowkju/mstsc/globalconfig.out How can I solve this problem?? Thank you!!!! - WanKeun Jo.

2 1

Project Ideas?
by Eric M. Hielscher 10 Sep '06

10 Sep '06

Hi all, My name is Eric Hielscher, and perhaps some of you will remember me as the student from Amsterdam who visited your group briefly this August. I'm looking to do a project related to L4 this semester in an attempt to familiarize myself with the codebase in preparation for my applying for PhD positions in the fall but after a short look at the websties haven't found an up-to-date listing of project ideas. Is there such a page? If not, do you have some ideas for properly-sized and properly-difficult projects that you'd like to see done? Thanks and regards, -- Eric Hielscher http://ehielscher.org

2 1

As a beginner, hello, not working due to trap...
by 조완근 10 Sep '06

10 Sep '06

Hello!!   I'm a totally newbie at L4-Fiasco. I have tried to run the hello program with the fiasco kernel since yesterday. I just want the following commands in menu.lst of grub work well so that I can see the "hello" message.   ------------------------------------------------------ title       Hello_World kernel      (hd0,5)/fiasco/bootstrap -comport 1 -serial modaddr     0x02000000 module      (hd0,5)/fiasco/fiasco -nokdb module      (hd0,5)/fiasco/sigma0 module      (hd0,5)/fiasco/roottask module      (hd0,5)/fiasco/hello ------------------------------------------------------ I can solve the "modaddr" problem with grub-0.97 by installing grub-0.90 in a floppy disk. And then I'm now in a stuck with the following error.   ----------------------------------------------------------------------- ......... 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4K or 4M pages) 12k u-ops T Cache (8-way associative)     8 KB L1 D Cache (4-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 16384 bytes(4 pages) .... Registers' contents showed.... trap 3 (Breakpoint), error 00000000 from kernel mode Panic: terminated due to trap Return reboots, "k" enters L4 kernel debugger... -----------------------------------------------------------------------   I've already tried modifying kernel option so many times. But it didn't work.   How can I solve this problem??     Thank you!!   Jo.

2 1

dice bug?
by Spring, Ryan C 06 Sep '06

06 Sep '06

When I compile the following idl statement: library kpr { interface memserv { void foo([out] fpage *thepage,[in] int size); }; }; It produces the following memserv-client.c ... if (l4_ipc_fpage_received(_dice_result)) else { ... This causes compile errors because of the empty if. This is obviously an epsilon change to fix, just wondered if this is a bug in the dice compiler or is my idl somehow wrong? Regards, Ryan Spring --- Ryan Spring Doctoral Student University of Texas at El Paso (UTEP) Cell: +1 915-539-7311 (when in USA) Alt Cell: +49 179-9624406 (when in Germany) http://www.spring-west.net/ryan

2 1

No mouse with L4Linux/DOpE
by FERANDELLE Pascal 29 Aug '06

29 Aug '06

Hi, I try to use L4Linux-2.6/DOpE under Fiasco on a PC, which has keyboard and mouse on the USB bus. I have no problem with the keyboard, either with con or l4dope, but for DOpE, the mouse pointer appears at (0,0), but I can't move it. The mouse is well detected on the USB bus by the kernel. Thanks for help. Pascal

2 1

Re: How can I download the L4Linux-2.6.16
by chenggh 29 Aug '06

29 Aug '06

On Tuesday 29 August 2006 16:05, Andreas Niederl wrote: > Hi, > > chenggh wrote: > > Hi: > > I want to use the L4Linux-2.6.16 but according to the instruction of > > L4Linux website the latest version is L4Linux-2.6.17. How can I download > > it? If I use the "cvs -z3 -d > > :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs co l4linux-2.6" to > > download the L4Linux-2.6 what is the detailed version of L4Linux-2.6? > > The L4Linux currently sitting in CVS is based on 2.6.17. You can get the > version of a Linux source tree by reading the first 5 lines of its > Makefile: > > someone@somewhere src % cd l4linux-2.6 > someone@somewhere l4linux-2.6 % head -n5 Makefile > VERSION = 2 > PATCHLEVEL = 6 > SUBLEVEL = 17 > EXTRAVERSION = -l4 > NAME=Crazed Snow-Weasel Sorry, I think I can't express my meaning correctly. I want to download the L4linux-2.6.16 package. But now if I download the l4linux-2.6 with cvs the l4linux-2.6 is based on linux-2.6.17 not 2.6.16. But how I download the L4Linux-2.6.16? Thank you! chenggh

3 2

How can I download the L4Linux-2.6.16
by chenggh 29 Aug '06

29 Aug '06

Hi: I want to use the L4Linux-2.6.16 but according to the instruction of L4Linux website the latest version is L4Linux-2.6.17. How can I download it? If I use the "cvs -z3 -d :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs co l4linux-2.6" to download the L4Linux-2.6 what is the detailed version of L4Linux-2.6? Thank you! chenggh

2 1

Is there a service in L4 packages like shell in Linux?
by chenggh 29 Aug '06

29 Aug '06

Hi, I think if a servive in l4/pkgs like shell in Linux exists it will help the L4-user very much. We could start or stop a seriver like creating or destroying a process in Linux. I don't know whether there is a server like this? If it is not done I want to have a development with this server. thank you! chenggh

2 1

Amount of threads per task?
by Oskar Senft 28 Aug '06

28 Aug '06

Hi L4 Hackers! When creating new threads within the L4Linux kernel, I "sometimes" (whatever that means) get the following output and error: *l4lx | l4lx_thread_create: Created thread 0e.1a (Command) --Thread names exhausted!--------------------------------IP: 0050758e What does that mean? After pressing "g", the system continues running. However when I try to kill the thread later, I get the following: --Unknown TID to delete thread name!---------------------IP: 0050760a Is it not possible to create more than 0x19 = 25 threads within the L4Linux kernel? Or am I doing anything wrong? Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

3 5

L4Linux threads - interrupt context
by Oskar Senft 28 Aug '06

28 Aug '06

Hi L4Linux hackers! When creating threads within the L4Linux kernel and running the command l4x_prepare_irq_thread(current_thread_info()); the thread obviously ;-) is being run in the interrupt context. This means the thread (let's call it thread X) must not sleep and is restricted in other ways. This implies, that I cannot run Linux functions that would cause the thread X to sleep - that's clear. On top of that, let's create the following scenario: some other task issues an IPC call to the described L4Linux thread X waiting for IPC. For handling the call, thread X would need to use Linux functions causing thread X to sleep. This will cause a kernel panic, deadlock or other severe errors. Our idea for solving that is to use *another* "normal" *Linux* thread (let's call it Z) not running in interrupt context. This thread Z would sleep until it is awakened by the L4Linux thread X and then call the Linux function that causes thread Z to sleep. But: the L4Linux thread X would have to send a reply to the IPC call immediately. So, I would need another L4 thread Y (not known to L4Linux), acting as a notifier thread for the calling task. This thread would receive the IPC notify call, go into a L4 semaphore waiting to be woken by thread Z. So, the simple IPC call from another task which should use a Linux function requires *three* threads to run ... If we had the possiblity to send the reply to an incoming IPC from _another_ thread than the called thread, this at least would eliminate the notifier thread Y. If we had the possibility to run L4Linux threads (like thread X) in some Linux context where it could sleep, this could even eliminate both threads Y and Z. Is there a simpler solution? Is it possible to make it easier? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 1

NICTA-Ericsson secure-OS collaboration
by Gernot Heiser 26 Aug '06

26 Aug '06

For those who haven't looked at l4hq.org recently: NICTA and Ericsson have announced a research collaboration, among others on secure embedded operating systems. This is based on NICTA's L4-embedded/Iguana operating system. Gernot

1 0

L4.sec implementation and formal verification
by William DUCK 26 Aug '06

26 Aug '06

Hello Misters, As you are microkernel experts, I am asking your help. I am attempting to build up a team. I believe it's time for a full-fledge verified OS. If somebody is interested in functional programming and in formal methods to help to implement the L4.sec kernel , he is welcome :) Here is an example of a protocol formalisation : network stack : http://www.cl.cam.ac.uk/~pes20/Netsem/ If you want to contact me, my mail is guillaume_dot_fortaine_at_wanadoo_dot_fr I will set up a mailing-list, a web server, a wiki and an IRC Best Regards, Guillaume FORTAINE

2 1

Re: L4Linux threads - interrupt context
by Bjoern Doebel 25 Aug '06

25 Aug '06

2 3

TPM Emulator with L4Linux
by Andreas Niederl 24 Aug '06

24 Aug '06

Hi, has anybody successfully used the TPM Emulator[1] module with L4Linux? I have been trying using it with TrouSerS[2] but fail on starting tcsd with the following two errors (always one of them but never both at the same time): gentoo-l4 TDDL[4480]: tddl.c:105 Calling write to driver gentoo-l4 tpm_emulator tpm_emulator-0.4/./linux_module.c:113: Debug: tpm_ioctl(21505, 0808e500) gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:4156: Debug: tpm_handle_command() gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:3473: Info: The tag value sent to for a command (0x6564) is invalid gentoo-l4 TCS[4480]: tcs_utils.c:260 ERROR: TCS GetCapability failed with result = 0x1e and gentoo-l4 TDDL[4483]: tddl.c:105 Calling write to driver gentoo-l4 tpm_emulator tpm_emulator-0.4/./linux_module.c:113: Debug: tpm_ioctl(21505, 0808e500) gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:4156: Debug: tpm_handle_command() gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:4160: Error: tpm_unmarshal_TPM_REQUEST() failed gentoo-l4 TDDL[4483]: tddl.c:148 ERROR: Zero bytes read from device /dev/tpm gentoo-l4 TCS[4483]: tcs_utils.c:260 ERROR: TCS GetCapability failed with result = 0x1087 I guess that something is going wrong with the call to ioctl from tddl but wasn't able to figure it out yet. Are there modifications necessary for using modules with L4Linux? Regards, Andi [1] http://tpm-emulator.berlios.de/ [2] http://trousers.sourceforge.net/

2 2

L4Linux with serial console / IRQ usage
by Andreas Niederl 24 Aug '06

24 Aug '06

Hi, I have been trying to get a serial console on L4Linux with the stub drivers and encountered the message 'l4ser: vkey_irq not set - input disabled!'. Unfortunately I don't know which IRQ number is required here. I tried passing some different values to L4Linux which resulted in the error message 'irq_thread: RMGR denied IRQ 4: Code 0x1'. I'd be grateful for some hints on that. I also noticed that there are several different ways for handling IRQs (omega0, rmgr, l4io, ...) which require different options for some servers and L4Linux. Are there any documents describing the IRQ handling in L4Env and how to follow one of these ways consistently? /boot/grub/menu.lst: title L4Linux-2.6 kernel /boot/bootstrap -serial modaddr 0x02000000 module /boot/bin/fiasco -nowait -nokdb -serial -serial_esc -comport 1 module /boot/bin/sigma0 module /boot/bin/roottask task modname "bmodfs" attached 5 modules module /boot/bin/names module /boot/bin/log module /boot/bin/dm_phys module /boot/bin/simple_ts -t 300 module /boot/bin/rtc module /boot/bin/l4io --noirq module /boot/bin/tftp -i module /boot/bin/bmodfs module /boot/bin/libld-l4.s.so module /boot/bin/libloader.s.so module /boot/bin/run-script module /boot/bin/vmlinuz26 module /boot/bin/drops-rd.rd module /boot/bin/loader --fprov=BMODFS run-script /boot/bin/run-script: modpath "/boot/bin" sleep 2 task "vmlinuz26" "mem=64M load_ramdisk=1 ramdisk_size=17000 root=/dev/ram l4env_rd=/boot/bin/drops-rd.rd console=ttyLv0 l4ser.vkey_irq=4" priority 0xA0 all_sects_writable Regards, Andi

3 15

No keyboard with L4Linux
by FERANDELLE Pascal 23 Aug '06

23 Aug '06

I boot L4Linux-2.6 on Fiasco, using l4con on a graphical console, and the drops ramdisk. Everything boots well, and I obtain the "dropsbox login:", but, unfortunately, I have no keyboard entry ... In the previous kernel messages, there is one saying : i8042.c: Can't read CTR while initializing i8042 Can it be related to my problem ? Thanks Pascal

2 1

Re: Booting L4Linux/Fiasco with root=/dev/hda
by Bjoern Doebel 23 Aug '06

23 Aug '06

1 0

Booting L4Linux/Fiasco with root=/dev/hda
by FERANDELLE Pascal 23 Aug '06

23 Aug '06

I try to boot L4Linux (kernel 2.6.17) on Fiasco, on a PC which has already RedHat Enterprise Linux 4.0 installed, with root=/dev/hda3. The Linux kernel begins to boot, but after the messages : ... kjournald starting. Commit interval 5 seconds EXT3 FS on hda3, internal journal EXT3-fs: mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) Warning: unable to open an initial console Nothing else appears on the screen, but I can see the station is still alive, because the disk led is still highlightening frequently, then everything stops, and I have the message "Restarting system" on the screen. Nothing else happens ... Any idea, first for the opening problem of the console, and then, about what can happen after that, would be nice !!! Thanks Pascal PS : here is my grub.conf file and my linux26.cfg file --- grub.conf --- title L4_Linux 2.6 root (hd0,0) kernel /l4_linux/bootstrap vbeset 0x117 modaddr 0x06000000 module /l4_linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module /l4_linux/sigma0 module /l4_linux/roottask task modname "bmodfs" attached 4 modules module /l4_linux/events module /l4_linux/names -events module /l4_linux/log module /l4_linux/dm_phys --isa=0x00800000 -v --events module /l4_linux/simple_ts -t 300 --events module /l4_linux/rtc --events module /l4_linux/l4io -noirq --events # module /l4_linux/l4exec --events module /l4_linux/con -l4io --events # module /l4_linux/l4dope -l4io --events module /l4_linux/bmodfs --events module /l4_linux/libld-l4.s.so module /l4_linux/libloader.s.so module /l4_linux/linux26.cfg module /l4_linux/vmlinuz26 module /l4_linux/loader --fprov=BMODFS linux26.cfg --- linux26.cfg --- modpath "(hd0,0)/l4_linux" task "vmlinuz26" "earlyprintk=yes mem=64M video=l4fb root=/dev/hda3" all_sects_writable

1 0

Where is the definition of hi_server_loop() function?
by chenggh 23 Aug '06

23 Aug '06

Hi, Everyone: Now I am reading the document of Building Infrastructures for DROPS Tutorial. And in the server side the code is like this: #include <stdio.h> #include <l4/names/libnames.h> #include "hiworld-server.h" char LOG_tag[9]="hiserver"; static int count; void hi_print_component(CORBA_Object _dice_corba_obj, CORBA_Environment *_dice_corba_env){ printf("Hi world\n"); count++; } int hi_count_component(CORBA_Object _dice_corba_obj, CORBA_Environment *_dice_corba_env){ return count; } int main(void){ if(names_register("hiworld")==0){ printf("Error registering at nameserver\n"); return 1; } hi_server_loop(0); } In the main routine there is function named hi_server_loop. But I don't where is the function definition. i checked the hiworld-server.h and there is no definition. ths chenggh

2 1

Problem of l4lx_thread kmalloc
by 강후영 22 Aug '06

22 Aug '06

Hi, I created l4lx_threads by "l4lx_thread_create()". But when these threads alloccate some memory by kmalloc(), fault error always occurs as fallow, l4lx | L4RM: [PF] read at 0x999999b0, eip 0042e30a, src E.0B l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault What is the problem? Is there some size limitation of kmalloc for thease threads? I tried to allocate a few KBs. Best regards

2 1

L4 bug report
by chenggh 21 Aug '06

21 Aug '06

hi, everyone: Today I use ubuntu 6.06 to compile the l4. There are some error messages like this: make[2]: Entering directory `/home/fiasco/L4/l4/tool/gcc-wrap' ... Building .general.d make[2]: Leaving directory `/home/fiasco/L4/l4/tool/gcc-wrap' make[2]: Entering directory `/home/fiasco/L4/l4/tool/gcc-wrap' ... Generating drops-ar.Linux sed '\ s,@system@,Linux,g;\ s,@ar@,ar,g;\ s,@nm@,nm,g;\ s,@ranlib@,ranlib,g;\ s,@cc@,gcc,g;\ s,@cxx@,g++,g;\ s,@l4dir@,,g;\ s,@dropsdir@,/home/fiasco/L4/,g;\ s,@compilerincdir@,/usr/lib/gcc/i486-linux-gnu/3.4.6/include,g;\ s,@libgcc@,/usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a,g;\ s,@libgcc_eh@,/usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc_eh.a,g;\ s,@default_system@,x86_586-l4v2,g;\ s,@default_arch@,x86,g;\ s,@default_cpu@,586,g;\ s,@default_l4api@,l4v2,g; \ ' drops-ar.in > drops-ar.Linux.new sed: -e expression #1, char 452: unterminated address regex make[2]: *** [drops-ar.Linux] Error 1 make[2]: Leaving directory `/home/fiasco/L4/l4/tool/gcc-wrap' make[1]: *** [gcc-wrap] Error 2 make[1]: Leaving directory `/home/fiasco/L4/l4/tool' make: *** [tool] Error 2 I doubted that it is sed version's problem. In ubuntu 6.06 the sed is NU sed version 4.1.4. chenggh

2 2

l4linux-2.6 does not build
by Stefan Scheler 19 Aug '06

19 Aug '06

Hello, current cvs version of l4linux does not build (please see attached log). Resolving this by putting the headers manually in the right place gives more errors like that. There must be something broken in the build process. Thanks for help. Stefan Creating asm-l4/api-l4env -> asm/api symlink Creating asm-l4/l4lxapi/impl symlink Creating asm-l4/l4x-i386 -> asm/l4x symlink Creating asm-l4/l4-arch/asm symlink Creating asm-l4/i386-arch/asm symlink CHK include/linux/version.h UPD include/linux/version.h SYMLINK include/asm -> include/asm-l4 SPLIT include/linux/autoconf.h -> include/config/* CC arch/l4/kernel/asm-offsets.s In file included from include/asm-l4/l4-arch/asm/processor.h:12, from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/spinlock.h:50, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/segment.h:8:28: l4/sys/segment.h: No such file or directory In file included from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/spinlock.h:50, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/processor.h:25:26: l4/sys/types.h: No such file or directory In file included from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/spinlock.h:50, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/processor.h:407: error: syntax error before "l4_threadid_t" include/asm-l4/l4-arch/asm/processor.h:407: warning: no semicolon at end of struct or union include/asm-l4/l4-arch/asm/processor.h:408: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:409: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:410: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:411: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:412: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:413: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:414: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:426: error: syntax error before '}' token In file included from arch/l4/kernel/asm-offsets.c:8: include/linux/sched.h:804: error: field `thread' has incomplete type In file included from include/asm-l4/l4-arch/asm/suspend.h:6, from include/linux/suspend.h:5, from arch/l4/kernel/asm-offsets.c:11: include/asm-l4/l4-arch/asm/desc.h: In function `write_ldt_entry': include/asm-l4/l4-arch/asm/desc.h:116: warning: implicit declaration of function `fiasco_ldt_set' include/asm-l4/l4-arch/asm/desc.h: In function `load_TLS': include/asm-l4/l4-arch/asm/desc.h:130: warning: implicit declaration of function `fiasco_gdt_set' include/asm-l4/l4-arch/asm/desc.h:130: error: dereferencing pointer to incomplete type include/asm-l4/l4-arch/asm/desc.h:130: error: dereferencing pointer to incomplete type make[1]: *** [arch/l4/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2

3 3

build problems with dice
by chenggh 17 Aug '06

17 Aug '06

hi: when I try to compile the dice, there are some errors like this: /home/chenggh/L4/l4/tool/dice/src/CDCEParser.cpp:264: undefined reference to `dce_flex_debug' CCORBAParser.o: In function `CCORBAParser::Import(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:93: undefined reference to `GetCurrentBufferCorba()' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:154: undefined reference to `RestoreBufferCorba(void*, bool)' CCORBAParser.o: In function `CCORBAParser::Parse(void*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, bool, bool)': /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:231: undefined reference to `corba_flex_debug' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:245: undefined reference to `RestoreBufferCorba(void*, bool)' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:257: undefined reference to `GetCurrentBufferCorba()' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:241: undefined reference to `corbain' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:242: undefined reference to `StartBufferCorba(_IO_FILE*)' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:236: undefined reference to `corba_flex_debug' CPreProcess.o: In function `CPreProcess::PreProcess(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, bool)': /home/chenggh/L4/l4/tool/dice/src/CPreProcess.cpp:343: undefined reference to `incin' /home/chenggh/L4/l4/tool/dice/src/CPreProcess.cpp:344: undefined reference to `incout' /home/chenggh/L4/l4/tool/dice/src/CPreProcess.cpp:348: undefined reference to `inclex()' ./src/parser/dce/libdce.a(parser.o): In function `dceparse()': /home/chenggh/L4/l4/tool/dice/src/parser/dce/parser.yy:3577: undefined reference to `dcelex(yystype*)' ./src/parser/dce/libdce.a(parser.o): In function `dceparse()': /usr/share/bison/bison.simple:574: undefined reference to `dcelex(yystype*)' ./src/parser/corba/libcorba.a(parser.o): In function `corbaparse()': /usr/share/bison/bison.simple:574: undefined reference to `corbalex(yystype*)' ./src/parser/gcc-c/libg I checked the old mailist again. Somebody else encountered the same problem with me. I use g++3.3.6 and bison 1.35. My host OS is ubuntu 5.10. How to fix it? thank you chenggh

2 1

L4Linux-2.6.17 on Fiasco
by FERANDELLE Pascal 12 Aug '06

12 Aug '06

Hi, I try to run L4Linux-2.6.17 on Fiasco, on native PC, and I have problems. As I got the following error : ... l4lx | Filling lower ptabs l4lx | Done (1643 entries) l4lx | l4lx_thread_create: Created thread 0e.05 (timer.i0) DMphys | ds 36, client E.00, rights 0x0003, has 0x0001 DMphys | [8.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): DMphys | DMphys: bad permissions l4lx | L4RM: dataspace at 0x00400000-0x00614fff, id 36 at 8.00 l4lx | L4RM: dataspace manager call failed ("permission denied") l4lx | L4RM: [PF] write at 0x004025ec, ip 0040b53c, src E.02 l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault after looking at the mailing list, it seems the "Use ldso for loading" option has to be configured for L4Linux. I did so, but now, the load stops with the following messages : loader | vmlinuz26 : Starting application using libld-l4.s.so loader | vmlinuz26,#e : Loading binary loader | vmlinuz26,#e : Loading ldso loader | vmlinuz26,#e : Starting libld-l4.s.so at 00013870 via 0000bf60 then messages from io about PCI configuration, and go to jdb with message : (e.00) jdb: --__main() returned My grub.conf file is as following : title L4_Linux 2.6 root (hd0,0) kernel /l4_linux/bootstrap modaddr 0x06000000 module /l4_linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module /l4_linux/sigma0 module /l4_linux/roottask task modname "bmodfs" attached 4 modules module /l4_linux/events module /l4_linux/names -events module /l4_linux/log module /l4_linux/dm_phys --isa=0x00800000 -v --events module /l4_linux/simple_ts -t 300 --events module /l4_linux/l4io -noirq --events module /l4_linux/l4exec --events # module /l4_linux/con -l4io -cpuload --events module /l4_linux/bmodfs --events module /l4_linux/libld-l4.s.so module /l4_linux/libloader.s.so module /l4_linux/linux26.cfg module /l4_linux/vmlinuz26 module /l4_linux/loader --fprov=BMODFS linux26.cfg and my linux26.cfg file : modpath "(hd0,0)/l4_linux" task "vmlinuz26" "earlyprintk=yes mem=64M root=/dev/hda3" all_sects_writable Any help would be great !!! Thanks Pascal

2 1

Re: current_thread_info
by Oskar Senft 12 Aug '06

12 Aug '06

Hi! >>> You need to call l4x_prepare_irq_thread(current_thread_info()) in your >>> thread before doing anything serious in there. >> Ok, sounds good. Unfortunately I cannot find it in my snapshot (May >> 5th, 2006) - since when should it have been in? > > l4x_setup_ti_thread_stack_irq(current_thread_info()) Great, thank you! That solved my problem. Could you please add the necessary line EXPORT_SYMBOL(l4x_setup_ti_thread_stack_irq); in arch/l4/kernel/main.c ? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 1

The "region overlap" problem in the L4/Fiasco hello example
by chenggh 12 Aug '06

12 Aug '06

Hi,everyone: When I boot the hello example in the L4/Fiasco. there is a "region overlap" in the booting information. I don't why it could be like this. The grub configuration and the error information is following: Grub: title fiasco_hello_new kernel (hd0,1)/boot/fiasco_hello_new/bootstrap -comport 1 -serial module (hd0,1)/boot/fiasco_hello_new/main -nokdb module (hd0,1)/boot/fiasco_hello_new/sigma0 module (hd0,1)/boot/fiasco_hello_new/roottask module (hd0,1)/boot/fiasco_hello_new/hello minicom_log: L4 Bootstrapper Loading (hd0,1)/boot/fiasco_hello_new/main Kernel at 00002000-0038f408 Detected new-style DD-L4(v2)/Fiasco x86 Loading (hd0,1)/boot/fiasco_hello_new/sigma0 Loading (hd0,1)/boot/fiasco_hello_new/roottask loaded module section: [0028d000-00324e13) .Roottask syms/lines (copy) overlaps with: [00300000-0038f408) (hd0,1)/boot/fiasco_hello_new/main [00002000-0005ae70) (hd0,1)/boot/fiasco_hello_new/main [0005b000-0005fcfd) (hd0,1)/boot/fiasco_hello_new/main [00090000-0009432d) (hd0,1)/boot/fiasco_hello_new/sigma0 [00095340-00096824) (hd0,1)/boot/fiasco_hello_new/sigma0 [0009f000-00100000) BIOS area [00100000-0010dc04) bootstrap [0013f000-0028ccb0) Modules Memory [00300000-0038f408) (hd0,1)/boot/fiasco_hello_new/main [1dff0000-ffffffff) Deep Space region overlap Thanks! Cheng

4 3

current_thread_info
by Oskar Senft 11 Aug '06

11 Aug '06

Hi L4Linux experts! Is it right, that the function current_thread_info (and dependent functions like "current") should not be called from threads which are created by "l4lx_thread_create"? I always get pagefaults while trying this ... *l4lx | L4RM: [PF] read at 0x99999c50, ip 004f9afe, src E.16 Is there a possibility to enable this function? Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 1

Re: L4Linux + Fiasco-ux
by Daniel Vandersee 10 Aug '06

10 Aug '06

Adam Lackorzynski wrote: > On Wed Aug 09, 2006 at 17:47:16 +0200, Daniel Vandersee wrote: > >>Adam Lackorzynski wrote: >> >>>Please enable "Use ldso for loading" in the L4Linux configuration. >>>Should also be default by tomorrow. >>> >> >>Thank you, but now the loader complains about a missing libld-l4.s.so >>which I can't find anywhere. > > > libld-l4.s.so is built in the ldso package. > I dowloaded the ldso package and recompiled l4linux (with ldso) as well as l4env, but I'm afraid this was wasn't the problem - I still get the same error. > loader | vmlinuz26.ux: Starting application using libld-l4.s.so > loader | vmlinuz26.ux,#f: Loading binary > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/libld-l4 > fuxfprov: .s.so" by D.02 > loader | vmlinuz26.ux,#f: Loading ldso > loader | vmlinuz26.ux,#f: Starting libld-l4.s.so at 00013e40 via 0000bba8 > fuxfprov| open "./libloader.s.so" by F.00 > fuxfprov| Can't open "./libloader.s.so": -2 > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/./libloa > fuxfprov: der.s.so" by F.00 > fuxfprov| open "vmlinuz26.ux" by F.00 > fuxfprov| Can't open "vmlinuz26.ux": -2 > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/vmlinuz2 > fuxfprov: 6.ux" by F.00 > l4lx | ======> L4Linux 2.6 starting... <======== > l4lx | Linux version 2.6.17-l4 (user@kubuntu) (gcc-Version 3.3.6 (Ubuntu 1: > l4lx : 3.3.6-8ubuntu1)) #4 Wed Aug 9 18:41:29 CEST 2006 > l4lx | Binary name: vmlinuz26.ux > l4lx | Kernel command line (9 args): mem=64M load_ramdisk=1 ramdisk_size=163 > l4lx : 84 root=1:0 l4env_rd=/home/user/ext/l4env_060809/DROPS/bin/x86_58 > l4lx : 6/l4v2/rd1 panicblink=0 lang=de video=l4fb:640x400@16,xpos:10,ypos:10 > l4lx : ,refreshsleep:150,title:DamnSmallLinux noirq > l4lx | Image: 00400000 - 0068f000 [2620 KiB]. > l4lx | Areas: Text: 00400000 - 005c6000 [1816kB] (a bit longer) > l4lx | Data: 005c6000 - 006025ac [241kB] > l4lx | Initdata: 00606000 - 00626000 [128kB] > l4lx | BSS: 00626000 - 0068d1c0 [412kB] > l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) > l4lx | Using tamed mode. > l4lx | l4lx_thread_create: Created thread 0f.04 (server) > l4lx | main thread will be 0f.04 > l4lx | l4env_register_pointer_section: addr = 00604000 size = 569344 > l4lx | sec-w-init: virt: 0x00604000 to 0x0068efff [556 KiB] > l4lx | Noncontiguous region for sec-w-init > l4lx | sec-w-init: Number of physical regions: 2, 569344 Bytes > l4lx | sec-w-init: 1: Phys: 0x0141c000 to 0x0148d000, Size: 462848 > l4lx | sec-w-init: 2: Phys: 0x00ae6000 to 0x00b00000, Size: 106496 > 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: 64MB > l4lx | Main memory: virt: 0x00800000 to 0x047fffff [65536 KiB] > l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes > l4lx | Main memory: 1: Phys: 0x0a400000 to 0x0e400000, Size: 67108864 > l4lx | Filling lower ptabs... > l4lx | Done (1260 entries). > l4lx | l4env_rd_path: /home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2 > l4lx : /rd1 > l4lx | Loading: /home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/rd1 > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/rd1" by > fuxfprov: F.04 > l4lx | INITRD: Size of RAMdisk is 16384KiB > l4lx | RAMdisk from 04800000 to 05800000 [16384KiB] > l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) > DMphys | ds 81, client F.00, rights 0x0003, has 0x0001 > DMphys | [7.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): > DMphys | DMphys: bad permissions > l4lx | L4RM: dataspace at 0x00400000-0x005c5fff, id 81 at 7.00 > l4lx | L4RM: dataspace manager call failed ("permission denied") > l4lx | L4RM: [PF] write at 0x00402860, ip 0040b2bc, src F.02 > l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > l4lx | unhandled page fault > > --PANIC, 'g' for exit-------------------------------ESP:00629d20 EIP:a00bdcd3 > (f.00) jdb: ^ Kind regards, Daniel

3 3

L4Linux output on serial line?
by Andreas Niederl 09 Aug '06

09 Aug '06

Hi, I would like to have the output from the L4Linux kernel on the serial line for debugging purposes because Qemu doesn't allow me to scroll back in its output window. Could somebody give me hints on how to doing that? I already configured Grub for having serial support from bootstrap and Fiasco. Regards, Andi

1 1

exec doesn't respect all_sects_writable
by Andreas Niederl 09 Aug '06

09 Aug '06

Hi, I wanted to run a current L4Linux using the CVS version of DROPS and got a page fault when the Linux code is self-modified. I was told to use the option all_sects_writable for the loader, but this apparently does not work when not using ldso. Exec seems to ignore this option and maps in the L4Linux space read only. This looks like a bug to me. Regards, Andi

2 2

L4Linux + Fiasco-ux
by Daniel Vandersee 09 Aug '06

09 Aug '06

Hello, when I try to run L4Linux (compiled for ux) on top of Fiasco-ux I get the following error: $./lx con ... > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/rd1" by > fuxfprov: F.04 > l4lx | INITRD: Size of RAMdisk is 16384KiB > l4lx | RAMdisk from 04800000 to 05800000 [16384KiB] > l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) > DMphys | ds 67, client F.00, rights 0x0003, has 0x0001 > DMphys | [7.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): > DMphys | DMphys: bad permissions > l4lx | L4RM: dataspace at 0x00400000-0x005c5fff, id 67 at 7.00 > l4lx | L4RM: dataspace manager call failed ("permission denied") > l4lx | L4RM: [PF] write at 0x004026d0, ip 0040b2bc, src F.02 > l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > l4lx | unhandled page fault > > --PANIC, 'g' for exit-------------------------------ESP:0000893c EIP:000223b3 > (f.00) jdb: I tried several L4Linux configurations without success. Any help would be appreciated. Kind regards, Daniel

2 1

L4 Semaphore in L4Linux
by Oskar Senft 09 Aug '06

09 Aug '06

Hi! Is it possible to use the L4 Semaphore and Lock within a L4Linux kernel module somehow? I believe, that both is already used within the L4Linux kernel itself, but the symbols are not exported to other kernel module. When I now try to use them, the linker tells that the following symbols are undefined: "l4semaphore_restart_down" "l4semaphore_restart_up" "l4thread_myself" "l4semaphore_thread_l4_id" If I try to add the libsemaphore.a, the situation gets worse and the following symbols are undefined. "LOG_flush" "_exit" "l4thread_create_long" l4thread_get_prio" "l4sigma0_kip_kernel_has_feature" "l4thread_l4_id" "l4thread_myself" "l4thread_data_set" "l4thread_data_get" "LOG_logL" "l4thread_set_prio" "l4thread_data_allocate_key" Even adding more libs to the L4Linux kernel module does not resolve all symbols - I'm not even sure if that could work at all. These are the libs already linked in (and making the kernel module work - without semaphores / locks): libdm_generic.a \ libl4env.a \ libl4env_err.a \ libgeneric_blk-server.a \ libl4sys.a \ libnames.a \ libroot.o.a \ libdiet_c.a \ I also tried to simply load the kernel module with unresolved symbols - in hope that the running kernel would solve it - to no success. Does anyone have a solution to this? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 500 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 4

Semaphore library error on L4Env/Fiasco-UX
by Andreas Niederl 08 Aug '06

08 Aug '06

Hi, using the current CVS version of Fiasco and L4Env I get the following error on startup of the system with Fiasco-UX: exec | Startup: semaphore lib initialization failed (-1)! The task on which it fails varies depending on which startup script from l4/tool/runux is executed but it's always the first or second task that starts. L4Env is compiled with gcc-3.3.6 and Fiasco with gcc-4.0.2. Is this a known problem? Regards, Andi

2 3

Re: HURDNG : Which type of OS design could we have to think nowadays ?
by Ernst Rohlicek jun. 08 Aug '06

08 Aug '06

Hello Guillaume, Hello list, This is a long post and I hope to have made it somewhat interesting as well. Please stay with me :-) > Here is the start point of my reflexion : > > http://lists.gnu.org/archive/html/l4-hurd/2006-04/msg00053.html In this post, Mr. Shapiro compares roads of action for a next-generation Hurd and starts out with: "This will sound strange coming from me, but it may turn out that HurdNG should build it's own microkernel. I do not think this is a good idea, but let me try to enumerate the alternatives and articulate the advantages and disadvantages as I see them." His conclusions are true: Using something existing is great, PROVIDED it fits reasonably well - and it must fit almost the way it came. You may be able to retro-fit a few bits here and there, but that's it. It is also my experience that if you try to change a program in fundamental ways, it's easier to redo it rather than trying to re-orient it. Think of changing a KDE application into a GNOME application ... and the closer you get toward the kernel, the more work you have with re-orienting it. You have translated your design into code (created an "instance" so to speak) and we all know that C code is not friends with large re-writes. Another thing is that FAR too many people shy away from starting out anew. We're not a commercial company with time pressure. We have learned from the last "iteration", know a lot of the issues and mistakes - plus, we have time. Instead of patching and re-orienting and hoping, we should enter the next iteration and put to use what we've learned. Another snippet from the above message: "If, after you look at the alternatives, you still think that building or modifying a micro-kernel sounds good, try to assemble a team. If you can't, stop and look for another way. In my opinion, the L4-Hurd and mainstream Hurd communities simply do not have the (human) resources to build both a microkernel and an OS before most of this list has died of old age." Yup, there's action required... if not, well ... read again about that age thing. Just wanted to point that out... > I believe that we can do extremely complex and reliable software with > a few people, thanks to the powerful formal and design tools available > now. > > Time is maybe our worst ennemy : more and more technologies are > created day by day and we need to understand and to be able to use > them And it's maybe our better friend : as the hardware/software > becomes more and more complex, the tools to develop them becomes more > powerful too. > > The tools developed to understand and create complex systems give us > the ability to design and implement an OS design secure & reliable. You mention some interesting methods and utilities. I've used formal design myself (IBM's Rational - great tool) and it really takes away a lot of burden. You can change some relationships in the design view and they get translated / "instantiated" right into code. Usually you have to just fill in the blanks and application logic. I wonder if the things you mentioned can be used not just for modeling specific types of applications and relationships, but for more generic (Hurd servers, maybe even kernel?) programs. Could you find out about that? Rationale: In projects you often just HAVE to re-adapt the design of your program after iteration 1 ... and any way of quickly re-adapting the code to fit the new design is just GOLD. That's in my opinion why there is things like re-factoring, meta-programming, formal and model-based design and lots of scripting (prototyping?) languages. Would you implement a proof-of-concept or prototype rather in Python or in ANSI C ? With manual memory allocation, char arrays, buffers, pointers, Makefiles, autotools stuff...? Guillaume, your idea is quite on the spot, I believe. I personally acknowledge that you can do great prototypes with formal design and high-level languages. Look over to the development of the seL4 / L4.sec kernel: http://ertos.nicta.com.au/research/sel4/tech.pml They themselves use a machine simulator, which catches all kernel requests and hands them to the "kernel", which is developed outside of the simulator in the Haskell programming language. I'm convinced that they're able to go through design and verification iterations so much faster. And besides, their specification = implementation looks almost the same as a model description from model-based engineering. I guess that later, when the algorithms have been optimized and they found that they've developed a useful design for their requirements, they might actually implement it in C (though comparison shows that the Haskell GHC compiler also produces very fast code), search for "performance" or "slow" here: http://www.haskell.org/haskellwiki/Introduction But that Haskell thing just as a side note. It's important to point out that fast prototyping, fast design verification (and -adaption until we know, "This is it, we have it"), fast creation of code instances from a model or directly use a high-level language for initial design creation is almost a key point. > -The first one is the start of any important project : developers can > have the possibility to share complex ideas with minimum requirements > and to integrate them in a coherent environment. ( see > http://www.gnu.org/software/hurd/ => 23 years old and even the goals > are not well defined ) That's an under-estimated point ... and yet a vital one. > -The second feature provide any user the ability to develop on it with > existing materials and to have the support of developers of legacy OS. Yes, transition is important. Going too far out with GNU Hurd means no good. > -The third one needs that a device driver framework needs to be > rapidly envisaged. ( again http://www.gnu.org/software/hurd/ => no > good driver kit at this date, the same for linux : > http://www.kroah.com/log/2006/05/24/, 15 years later ). Who wants to > have an OS that boots only a black screen with a beep sound ? If we > follow the Moore law, an OS design of the future would be thought for > quadruple play ( mobility, audio, video, Internet ) and security of > course. Yes, being able to fulfill use-cases is important. Besides, any developer for a possibly next-gen OS wants to listen to some MP3s :-) > Abstraction will be the solution, Putting more and more layers of abstraction between the hardware and the program logic usually is no good. What exactly do you mean with abstraction? Or: What kind of abstraction do you mean? > I believe that HurdNG had to focus one 2 things ( lol :-), easy to tell, > hard to design ) : security and performance. Security because all > devices are becoming more and more connected and performance because of > the Moore's law. Security indeed is becoming more and more important; as as maintainability and modularity. > *First option : > > Should we support 386 and let the OS die with this obselete hardware or > think to the future and enjoy the power of 64 bits and multicore that > are becoming standards ? > > The ideas have to go more far that the present, if the HURDNG ( forget > now UNIX:-) ) want to be a good option/successor to Linux. > > A Single Adress Space OS ( 64 bits = 256 Tb, we have time before > exploiting all this power => it would be moore easy to get rid of ACL > because of easier implementation of persistence) and a language/main > library thought for massive multithread (CSP or Concurrent/Parallel > Haskell => get rid of C/ maybe GNU/UNIX/POSIX too :-) ) . > > http://www.torsion.org/ > > http://www.cs.dartmouth.edu/~dfk/papers/kotz:addrtrace.pdf > > http://www.wotug.org/ > > http://www.eros-os.org/pipermail/e-lang/1999-November/003069.html > > http://tunes.org/wiki/Orthogonal_Persistence Persistence: Well, I'm not sure whether orthogonal persistence (in my interpretation this is quite similar to hiberation / suspend to disk) is really required - better: what it's benefits in a general-purpose OS for non-embedded CPUs are... After all you can still store your caps on disk, if you would like to. Design for old HW or for the future: I would not design a new OS for a machine you can't buy in stores anymore since 5 years (in 2001 we had Athlons and Pentium 3 / 4). Rationale: If you say that a new OS will have a lifetime of 10 years, then you will think back and say, "Why the hell did they let themselves get restricted by CPUs, which were several generations behind - already back then?!" Looking from today's perspective: If you design a little bit "too big" or "far ahead" for today's measures (64-bits where possible, massively threaded and laid out for SMP, among many other decisions), then today's design might still be ... hm, well at least MAKE SENSE in 10 years. > *Second option : > > Explore new ideas, maybe too innovative (Have to carefully choose/adapt > the language). > > http://lists.gnu.org/archive/html/l4-hurd/2006-04/msg00053.html > > I would add a fourth option : Get rid of a kernel : Well, you need need some kind of authority. "Processes can all be equal, but some have to be more equal." And the Exokernel idea is probably great for very specialized purposes, so remember that GNU/Hurd is supposed to be a general-use OS. If I misunderstood, we can further discuss of course. > http://www.tunes.org "Reflective OS" sounds tempting, though I personally think this belongs more into AI - intelligent, integrated assistants and the like. Of course it's okay that you mention it - I guess we all honor your right to bring new things to the table :-) > "Isaac is an operating system purely made by dynamicaly interconnected > prototype object. Each macro-object run on top of the processor. > > IsaacOS is not an interface with a standard kernel. IsaacOS is fully > made with only object. No file, no process, no kernel, just and only > object." > > http://isaacos.loria.fr/index.html I have yet to read up on "prototype-based" languages and this specific language here - hm, "based on Smalltalk", "uses GCC", "fast code like C", "used for writing operating systems", " Generally, I believe that we don't have to use C anymore to write hardware-near programs - back then in the 70s, 80s and even still in the 90s it was fine, but not today. There are fast alternatives with better facilities. BTW, think back to the 70's when C was invented. Back then it must have been like, "Oh my god, this is high-tech - are you sure you want to use that new, crazy 'C' language for your OS?" ... why are we so shy to use something newer and safer than C? (Safer as in eg. type safety) There are alternatives are in place. As motivation, here is a link to a WORKING implementation of Unix in C++, which is even binary compatible with Linux: http://www.unixlite.org/index.html So it is possible. As mentioned in my reply-paragraphs above, I suggest one of the following for a new kernel for GNU/Hurd - should seL4 / L4.sec and Coyotos be too far off the goals and requirements ... wait, WHAT goals and requirements BTW? - But I digress. ;-) Anyway, in that case, I would suggest using one or more or a mix of the following roads: 1. Using an intermediate prototyping language and/or some (needs TBD) model-based approach 2. Using an intermediate high(er)-level language for prototyping and starting implementation in C once we're sure about a (for our purposes) complete and sound design 3. Writing in a high(er)-level language which can be compiled into fast code (as fast like C), but which does not allow you to shoot yourself in the foot (too often) and which allows for relatively easy re-orientation of the code. For any of that to work, we need to know (and then get clearer) about things like: Goals, ideas, what Hurd really could do better than others ... how your computer(s) would work differently if it would be running your ideal version of Hurd, according to your ideas...? What are your ideas BTW? > Best Regards, > > Guillaume FORTAINE > Likewise, thanks for the input. --Ernst Rohlicek jun.

1 0

GDB on Fiasco-UX?
by Andreas Niederl 07 Aug '06

07 Aug '06

Hi, is Fiasco-UX suited for debugging with GDB? I noticed the lines generic.inc: [ -n "$RUN_GDB" ] && gdb_wrap="gdb $GDB_ARGS --args" generic.inc: $gdb_wrap $FIASCODIR/$FIASCO in l4/tools/runux/generic.inc and tried to run GDB by setting the RUN_GDB variable to something when calling one of the predefined ux-scripts, but it always results in segmentation faults concerning the calls to the cli and sti instructions. GDB output: Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Aug 3 18:16:37 2006 compiled with gcc 4.0.2 for Intel Pentium 4 Detaching after fork from child process 5989. Program received signal SIGSEGV, Segmentation fault. Dirq::alloc (this=0xce93f, t=0x639f5000, ack_in_kernel=802816) at auto/processor.h:128 128 asm volatile ("cli" : : : "memory"); (gdb) $ gdb --version GNU gdb Red Hat Linux (6.3.0.0-1.84rh) Regards, Andi

2 2

Can we really think at a new OS design nowadays ?
by Guillaume FORTAINE 06 Aug '06

06 Aug '06

Hello, Here is the start point of my reflexion : http://lists.gnu.org/archive/html/l4-hurd/2006-04/msg00053.html I believe that we can do extremely complex and reliable software with a few people, thanks to the powerful formal and design tools available now. Moreover, I think that this OS has to support three key things to be able to survive ( an essential key to have a long term development ) : synergy ,transition & usability. -The first one is the start of any important project : developers can have the possibility to share complex ideas with minimum requirements and to integrate them in a coherent environment. ( see http://www.gnu.org/software/hurd/ => 23 years old and even the goals are not well defined ) -The second feature provide any user the ability to develop on it with existing materials and to have the support of developers of legacy OS. ( see www.tunes.org => maybe too innovative and this : http://symbolx.org/ddf_news.html ). -The third one needs that a device driver framework needs to be rapidly envisaged. ( again http://www.gnu.org/software/hurd/ => no good driver kit at this date, the same for linux : http://www.kroah.com/log/2006/05/24/, 15 years later ). Who wants to have an OS that boots only a black screen with a beep sound ? If we follow the Moore law, an OS design of the future would be thought for quadruple play ( mobility, audio, video, Internet ) and security of course. Time is maybe our worst ennemy : more and more technologies are created day by day and we need to understand and to be able to use them And it's maybe our better friend : as the hardware/software becomes mor and more complex, the tools to develop them becomes more powerful too. The tools developed to understand and create complex systems give us the ability to design and implement an OS design secure & reliable. Here are my guidelines to start : _ First : Users collaboration :_ http://www.opencroquet.org _Second - Formal tools :_ http://www.fmeurope.org Z method : http://czt.sourceforge.net/ http://www.zuser.org/ B-method : http://en.wikipedia.org/wiki/B-Method http://rodin-b-sharp.sourceforge.net/index.html _Second - Software design :_ http://planetmde.org/ http://distributed-software.blogspot.com _ Third - Language Designer's Toolkit :_ http://lambda-the-ultimate.org/node/1562 http://hlvm.org/ Abstraction will be the solution, Best Regards, Guillaume FORTAINE

4 5

Invalid l4x_hybrid_return ?
by Oskar Senft 04 Aug '06

04 Aug '06

Hi L4Linux experts! We are currently doing some experiments with L4Linux L4BD and encounter a problem during a connect call by IPC (see logs). l4x_hybrid_return: Invalid hybrid return for 21.03 (0x00000000, d, 402, -1, b7a2a25e)! l4x_hybrid_return: Currently running: 00.00 I don't know what this error means and how we produced that. We use the L4Linux L4BD as shipped with L4Linux without any patches. What can we do? Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 500 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (osk@olaptop) (gcc version 3.3.6 (Debian 1:3. l4lx : 3.6-13)) #4 Thu Aug 3 15:19:50 CEST 2006 l4lx | Binary name: vmlinuz26-minimal l4lx | Kernel command line (6 args): mem=64M noreplacement l4bd.l4blk_name=b l4lx : lockenc root=/dev/hda1 panicblink=0 lang=de l4lx | Image: 00400000 - 00727000 [3228 KiB]. l4lx | Areas: Text: 00400000 - 0063d000 [2292kB] (a bit longer) l4lx | Data: 0063d000 - 00681520 [273kB] l4lx | Initdata: 00684000 - 006a8000 [144kB] l4lx | BSS: 006a8000 - 00725060 [500kB] l4lx | l4lx_thread_create: Created thread 21.03 (server) l4lx | main thread will be 21.03 l4lx | l4env_register_pointer_section: addr = 0063d000 size = 958464 l4lx | l4env_linux_startup thread 3. l4lx | sec-w-init: virt: 0x0063d000 to 0x00726fff [936 KiB] l4lx | sec-w-init: Number of physical regions: 1, 958464 Bytes l4lx | sec-w-init: 1: Phys: 0x006ea000 to 0x007d4000, Size: 958464 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Main memory: virt: 0x00800000 to 0x047fffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x11400000 to 0x15400000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1075 entries). l4lx | l4lx_thread_create: Created thread 21.04 (timer.i0) l4lx | Starting L4FB via CON con | vc_loop(): vc[2] running as D.08 l4lx | l4lx_thread_create: Created thread 21.05 (L4ConInput) con | vc_open_out(): vc[2] 1024x768@16, gmode:0x35 l4lx | l4fbcon: 1024x750 2bypp, size: 1540096 l4lx | l4lx_thread_create: Created thread 21.06 (CON refresher) l4lx | atexit(function = 0x00526130) called l4lx | l4x_hybrid_return: Invalid hybrid return for 21.03 (0x00000000, d, 40 l4lx : 2, -1, b7a2a25e)! l4lx | l4x_hybrid_return: Currently running: 00.00 backtrace (thread 21.03, fp=0080defc, pc=005e4273): #1 005e4273 : l4blk_driver_open_call + 0x53 ... v/drops-060505/l4/pkg/generic_blk/idl/OBJ-x86-l4v2/blk-client.c:82 #2 005e341e : l4blk_open_driver + 0xbe ... /devenv/drops-060505/l4/pkg/generic_blk/lib/client/src/driver.c:133 #3 00698e9a : l4bd_init + 0x3a /home/osk/tmp/drops-060505/l4linux-2.6-minimal/drivers/block/l4bd.c:317 #4 0068479b : do_initcalls + 0x2b /home/osk/tmp/drops-060505/l4linux-2.6-minimal/init/main.c:576 #5 0068483c : do_basic_setup + 0x1c /home/osk/tmp/drops-060505/l4linux-2.6-minimal/init/main.c:615 #6 00400090 : init + 0x30 /home/osk/tmp/drops-060505/l4linux-2.6-minimal/init/main.c:687 #7 00406389 : kernel_thread_start + 0x29 ... s-060505/l4linux-2.6-minimal/arch/l4/kernel/arch-i386/process.c:199 #8 0040635e : ret_kernel_thread_start + 0x6 ... s-060505/l4linux-2.6-minimal/arch/l4/kernel/arch-i386/process.c:174 #9 0040001c : rest_init + 0x1c /home/osk/tmp/drops-060505/l4linux-2.6-minimal/init/main.c:399 #10 0068471b : start_kernel + 0x16b /home/osk/tmp/drops-060505/l4linux-2.6-minimal/init/main.c:546 #11 0068ad3f : l4env_linux_startup + 0xbf ... /osk/tmp/drops-060505/l4linux-2.6-minimal/arch/l4/kernel/main.c:695 #12 000186d3 : l4th_thread_start + 0x73 ... pdate-060505-134059/drops-060505/l4/pkg/thread/lib/src/create.c:72 #13 0001b9a6 : l4th_thread_entry + 0x16 ... opsupdate-060505-134059/drops-060505/l4/pkg/thread/lib/src/l4.c:93 #14 00420804 : .text.lock.rcupdate + 0xa /home/osk/tmp/drops-060505/l4linux-2.6-minimal/kernel/rcupdate.c:603

2 3

Re: The future of L4
by Guillaume FORTAINE 03 Aug '06

03 Aug '06

Hello all, Here are two interesting links : http://www.nondot.org/sabre/os/articles http://www.ps.uni-sb.de/alice/ Best regards, Guillaume FORTAINE

1 0

multithreaded tcp echo server problem & flips
by David Silcott 03 Aug '06

03 Aug '06

hello all, I've ported my multithreaded tcp server to L4 using flips but I am having some problems getting it to run properly. It is a quite a bit to explain so I've written a simple tcp echoserver to demonstrate my problem. The following happens when the server starts and the client connects and send data. 1. Echoserver starts and listens on port 2222 2. client connects, server creates a child_server thread to service client and starts listening again 3. client sends string to child_server thread which is received. child_server however is unable to complete send(echo), it seems to be blocked at this point. 4. The send is only completed when another client attempts a connect(..and the server moves on from the accept(..) statement). I have appended my code at the bottom of this mail maybe someone can spot my mistake and highlight it. To check if I've used the threads properly I also wrote a program in which each thread prints the numbers from 0 to 9 and that runs fine. So I am pointing my finger and the recv(), accept() and send() functions in my echo server :-| Any suggestions will be greatly appreciated. cheers david ============================================================================= /*** GENERAL INCLUDES ***/ #include <stdlib.h> #include <stdio.h> #include <unistd.h> #include <sys/socket.h> #include <sys/types.h> #include <netinet/in.h> #include <arpa/inet.h> #include <string.h> /*** L4 INCLUDES ***/ #include <l4/names/libnames.h> #include <l4/thread/thread.h> #include <l4/log/l4log.h> #include <l4/dm_mem/dm_mem.h> #define BUF_SIZE 100 l4_threadid_t srv; char LOG_tag[9] = "tcpecho"; int data_key; struct th_data{ int c; //socket char foo[10]; //.... }; /* exit handler */ void child_exit(l4thread_t thread, void * data); void child_exit(l4thread_t thread, void * data){ struct th_data *ptr = (struct th_data *)data; /* close the connection and free up memory used by data structure*/ close(ptr->c); free(ptr); } /* declare exit function descriptor */ L4THREAD_EXIT_FN(exit_fn,child_exit); void child_server(void *data); void child_server(void *data){ char databuf[BUF_SIZE]; struct th_data *dptr = (struct th_data *)data; int ret, sock, n; void *ret_val; l4thread_t id; sock = dptr->c; LOG("got socket\n"); /* register exit function */ ret = l4thread_on_exit(&exit_fn, // exit function descriptor data // data pointer ); if (ret < 0){ /* register error function failed */ LOG_Error("Register error function failed\n"); } id = l4thread_myself(); LOG("Server thread starting with id %u\n",id); /* we are up */ if (l4thread_started(ret_val) < 0){ /* startup notification failed */ LOG_Error("Startup notification failed\n"); } LOG("Entering loop to wait for requests on socket %d.... \n",sock); while (1){ LOG("At top of while loop\n"); if((n = recv(sock, databuf, BUF_SIZE-1, 0)<=0)){ LOG_Error("recv failed %d returned \n",n); break; } databuf[4] = '\0'; databuf[5] = '\n'; LOG("GOT MESSAGE\n"); LOG(">%s; sending ....\n",databuf); databuf[0] = 'X'; send(sock,databuf,6,0); memset(databuf,0,BUF_SIZE); LOG("Looping\n"); } /* Call on exit function to terminate */ l4thread_exit(); } /* Start the server */ int main(int argc, char *argv[]){ int c, s,err, ret_val, errcount=0; struct sockaddr_in addr; if ((argc < 2) || strcmp("--nowait", argv[1])) while (names_waitfor_name("ifconfig", &srv, 30000) == 0) { LOG("Client(main): \"mini_ifconfig\" not available, keep trying..."); } memset(&addr, 0, sizeof(addr)); addr.sin_addr.s_addr = htonl(INADDR_ANY); addr.sin_family = AF_INET; addr.sin_port = htons(2222); LOG("try to open socket"); if ((s=socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) { LOG("Couldn't create socket"); return -1; } if (bind(s, (struct sockaddr *)&addr, sizeof(struct sockaddr)) < 0) { LOG("Couldn't bind"); return -1; } LOG("bound to socket %d, call listen",s); if ((err=listen(s, 1)) < 0) { LOG("listen(%d): %d", s, err); return -1; } LOG("echo server is up and accepting..."); names_register("echoserver"); while(1){ struct sockaddr dummyaddr; int addrlen; l4thread_t th; struct th_data *th_dptr; LOG("waiting for another connection\n"); if ((c=accept(s, &dummyaddr, &addrlen)) < 0) { LOG("accept(%d): %d", s, c); if (++errcount > 10) { LOG("maximum error count reached---giving up..."); exit(1); } continue; } LOG("Allocating thread data struct\n"); th_dptr = (struct th_data*)l4dm_mem_allocate( sizeof(struct th_data), L4DM_CONTIGUOUS); memset(th_dptr,0,sizeof(struct th_data)); th_dptr->c = c; LOG("Got a connection request, creating thread to handle client on socket %d\n", c); th = l4thread_create( child_server ,(void *)th_dptr ,L4THREAD_CREATE_SYNC); ret_val = l4thread_startup_return(th); /* Thread started ... listening for other requests */ LOG("thread created ... listening again\n"); } return 0; } __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 4

Re: The future of L4
by Guillaume FORTAINE 03 Aug '06

03 Aug '06

Hello all, I believe that the Mozart-Oz language could be a marvellous start point : object-oriented, concurrency, logic verification, security (planned)... What do we need now ? A good kernel design : security, asynchronous IPC, threading, real time scheduler A compiler : parser and optimization ( i think a sort of Elsa & Mozart-oz front-end for llvm ) A driver development environment : I believe the most time consuming part Forget Glibc .... or a poor fork of this => a new library design will be a good challenge too ;-) ! Powerful tools to reengineer legacy programs : http://www.program-transformation.org/Transform/WebHome 1 year of work and 100 very good programmers at least, and I think we will be able to enjoy it ... ;-) ! I am contacting some of the hall of fame, preparing my weapons, no problem. Makus & Neal were too weak because too few, but thanks to their effort, they show us the good way : we can revolutionize the world : linux was only a start point, it's time to port open source philosophy and community to a "military grade" quality ;-) ! Nowadays, is GNU really GNU is not Unix ( I would say GNU is only Linux ... ). Open source life behind a legacy OS ( 30 years ) design : Unix ( & C language too...) Hey guys, 15 years of development and I send you a mail with a LiveCd : very impressive, all my hardware is detected ( sound & video ok) => better than M$ ... But the security and the " raw" performance are indeed disappointing ( debian.org hacked 2 times in 2 years => 2000 developers behind ... ) kernel.org shut down one week ( ext3 ... ) Why an asynchronous IPC and a massively multithread model ? Asynchronous, like in real life : each one takes it times ;-) ! Massively multithread : performance, of course :-) ! I believe that security could be "easily" implemented with a good logic framework, we have marvellous tools to do that. Best regards, Guillaume FORTAINE

2 1

Re: The future of L4
by Guillaume FORTAINE 01 Aug '06

01 Aug '06

Hello, I believe we need only one language and not multiple languages : why ? There are few developers for L4, no need to divide them .... C++ is for me the best language ever : In the order ;-) !: Hardware design : http://www.systemc.org/ Low level optimization : http://llvm.org llvm is for fpga programming (used by los alamos ;-) !) : High level programming : c++ with concurrency : u++ http://plg.uwaterloo.ca/~usystem/uC++.html Metaprogramming : http://opencxx.sourceforge.net/ No language was so powerful ! If you hate unix, you can try plan9 : http://cm.bell-labs.com/plan9/ Future plans : An alpha kernel for work ( mix of L4.x2 v6 and L4.sec) A robust file system ( I think data log like nilfs with encryption support => trustedFS) A device driver development framework (like linux driver develoment kit) Support for sound/video I sincerely believe that we need to focus on the best things that Linux produces and put our efforts to simplify them (one file system, sound system, video system, desktop environment system) to reasonably produce an alpha os usable and not to wait 2020 or so to have only an IDE driver ... Best Regards, Guillaume FORTAINE

3 2

The future of L4
by Guillaume FORTAINE 31 Jul '06

31 Jul '06

Hello all, I believe it's time to use ne tools to develop a robust l4 based os. here are my suggestions : c++ multithreaded language : http://plg.uwaterloo.ca/~usystem/uC++.html c++ library : http://cxx.uclibc.org/ Could we replace glibc with uclibc++ and ntpl with the uc++ language ? build system : http://www.exactcode.de/oss/exact-build/index.html parrallel and asychronous api: https://gforge.inria.fr/projects/kaapi/ (scheduler and api for l4) => focused on performance : could not we consider a pc as an asynchronous platform ? video server : http://xcb.freedesktop.org/wiki/ X.org was not thought for multithread. It's time to change ;-) ! parser: http://www.cs.berkeley.edu/~smcpeak/elkhound/ compiler : http://llvm.org/ (used by los alamos laboratory ;-) !) Sound : http://www.alsa-project.org/ system development environment : http://www.t2-project.org/ A new concept : a meta-distribution (port for hurd planned :-) !) debuggers : http://www.cs.berkeley.edu/~dsw/oink.html http://valgrind.org/ I believe with this new tools we can construct the best system ever ... Best Regards, Guillaume FORTAINE

3 2

DICE_NO_REPLY error
by Michael Scheibel 27 Jul '06

27 Jul '06

Hello list, we have compiled the following interface with DICE 2.2.9: UInt32 genBuf( [out, size_is(*bufLen), max_is(MAX_BUFFER_SIZE)] UInt8** buf, [out] UInt32* bufLen, [out, size_is(*buf2Len), max_is(MAX_BUFFER_SIZE)] UInt8** buf2, [out] UInt32* buf2Len); UInt32 is defined as unsigned long, UInt8 as unsigned char, and MAX_BUFFER_SIZE is 4096. DICE options are -ftrace-server=printf -ftrace-client=printf -fforce-corba-alloc -P-DRAM_BASE=0x0 -P-DUSE_DIETLIBC=y -P-DSYSTEM_x86_l4v2 -P-DARCH_x86 -P-DCPUTYPE_ -P-DL4API_l4v2 -template -Bpia32 -Biv2 -BmC Running the generated stubs we noticed that ~0.89% of the IPC transactions fail. In such a case the parameters passed to the server still contain their initialization values on return. The client trace says "ipc error c0" and the server trace says "DICE_NO_REPLY". We would be happy about some hints what's going wrong here... Michael -- Sirrix AG security technologies - http://www.sirrix.com 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 message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

3 9

where are the headers?
by Alan Grimes 20 Jul '06

20 Jul '06

I'm planning out how to port Minix to L4 and I can't find any of the hearders. http://tudos.de/l4env/doc/html/bid-tut/node2.html I have CVS'd just about everything on your downloads page yet ./l4/include, ./l4/lib and ./l4/bin do not exist. I feel that many of the choices regarding the layout of the source code and the usage of the more sophisticated tools only serve to obfuscate the system to new users. =( -- Don't let your schoolwork get in the way of your learning. ### NEW E-MAIL: agrimes(a)speakeasy.net ###

7 9

gdb on Fiasco
by FERANDELLE Pascal 13 Jul '06

13 Jul '06

I took a copy of the floppy demo image on the Fiasco site, and try to use gdb on fiasco, from a PC/Linux with serial line, and gdb 6.4. I create a new grub entry to launch fiasco without the flags -noserial, -nowait and -nokdb, and the hello module. Boot seems ok, I suppose fiasco enters kdb and waits for a connexion from the serial line. On the PC/Linux, I launch gdb, and enter commands : set remotebaud 115200 target remote /dev/ttyS0 A dialog seems to establish with the target as I have the messages : Remote debugging using /dev/ttyS0 Sending packet: $Hc-1#09...Ack Packet received: Sending packet: $qC#b4...Ack Packet received: Sending packet: $qOffsets#4b...Ack Packet received: Sending packet: $?#3f...Ack Packet received: S05 Sending packet: $Hg0#df...Ack Packet received: Sending packet: $p8#a8...Ack Packet received: Sending packet: $g#67...Ack Packet received: 0000000001000000041e03 Sending packet: $m0,8#01...Ack Timed out. Timed out. Timed out. ... but the PC running Fiasco is resetting !!! Any information will be helpful ... Thanks Pascal

2 1

Running L4Linux on fiasco-ux?
by Michael J. Emswiler 05 Jul '06

05 Jul '06

Is it possible to run l4linux under fiasco-ux with X-11 apps? I am just testing various scenarios and playing around getting familiar with how things work. Here is the command I tried and the results : ./fiasco -G 1024x768@16 -m 256 -l names -l "dm_phys --mem=0x01400000,0x0a000000,0xffffffff" -l l4dope-ux -l l4ovlwm -l "vmlinuz26.ux mem=128M root=/dev/hda1 no-scroll" And the end result was: <snip> Roottask: Loading 5 modules. #05: loading "names" from [0ea3f000-0ea8440c] to [002d0000-002d776a][002d8000-002e4000] entry at 0000d360 via trampoline page code symbols at [0ea86000-0ea88000] (8kB), lines at [0da56000-0da5d000] (28kB) #06: loading "dm_phys --mem=0x01400000,0x0a000000,0xffffffff" from [0e9b3000-0ea3ed22] to [01500000-015130ca][01514000-0151e000] entry at 0000e388 via trampoline page code symbols at [0ea81000-0ea86000] (20kB), lines at [0ea73000-0ea81000] (56kB) #07: loading "l4dope-ux" from [0e874000-0e9b2c6a] to [01b00000-01b374cc][01b38000-01b7e000] entry at 0000f364 via trampoline page code symbols at [0ea67000-0ea73000] (48kB), lines at [0ea41000-0ea67000] (152kB) #08: loading "l4ovlwm" from [0e7c4000-0e873519] to [00b30000-00b49c34][00b4a000-00b78000] entry at 00010360 via trampoline page code symbols at [0ea3b000-0ea41000] (24kB), lines at [0ea27000-0ea3b000] (80kB) #09: loading "vmlinuz26.ux mem=128M root=/dev/hda1 no-scroll" from [0da5d000-0e7c37fb] to [00400000-0061880c][00619000-006585ac] [0065a000-0068c090][0068e000-00704000] entry at 00011388 via trampoline page code symbols at [0e98d000-0ea27000] (616kB), lines at [0e80a000-0e98d000] (1548kB) ROOT: task 9.00 at 00407db0 is trying to get page 00000000 which is reserved --double page fault---------------------------------ESP:001ac54c EIP:00137246 (4.00) jdb: ^ I realize it may not be best to run l4linux directly off /dev/hda1 that way ... but this is a dedicated test system. I will be directly booting into drops on that machine, once I figure out how to configure grub to do it :-) -- Thanks, MikeE ------------------------------------------------------- -- Thanks, MikeE

3 2

Re: panic in L4Linux booting process
by Adam Lackorzynski 04 Jul '06

04 Jul '06

On Tue Jul 04, 2006 at 23:07:37 +0800, chenggh wrote: > # module (hd0,1)/boot/faisco_L4/con -l4io -cpuload --events > # module (hd0,1)/boot/fiasco_L4/tftp -i > module (hd0,1)/boot/fiasco_L4/bmodfs --events > module (hd0,1)/boot/fiasco_L4/vmlinuz26 > module (hd0,1)/boot/fiasco_L4/linux26.cfg > module (hd0,1)/boot/fiasco_L4/libloader.s.so > # module (hd0,1)/boot/fiasco_L4/ramdisk.rd > module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS linux26.cfg > > Now there is no panic error. But there is no more information to be > output. The minicom log is like this: > > l4lx | PF: F.04: pfaddr = b0ffe002 pc = 00016db6 (rw) > l4lx | PF: F.04: pfaddr = b0fff002 pc = 00016db6 (rw) > l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) > l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) > l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) > l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) > > When executing here the light of harddisk would flush very frequently. > Later the light stop flushing and nothing could be output. That sounds good, I guess. The system is booting and when it's done the disk LEDs go out. But you need some sort of output. In your grub configuration you have disabled con, i.e. you have the plain VGA output, right? For that, you also need to have enabled the VGA option in Linux (CONFIG_VGA_CONSOLE). When you use con, you should enable the framebuffer driver (CONFIG_L4_FB_DRIVER). When using con you also need to set the video mode in the grub entry, i.e. just add vbeset 0x117 to your grub entry you're booting. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: panic in L4Linux booting process
by chenggh 04 Jul '06

04 Jul '06

On Tuesday 04 July 2006 18:18, Adam Lackorzynski wrote: > On Tue Jul 04, 2006 at 12:18:41 +0800, chenggh wrote: > > #2 00660b4f : mount_block_root + 0x8f > > /home/chenggh/test/l4linux-2.6/init/do_mounts.c:312 > > #3 00660d87 : mount_root + 0x87 > > /home/chenggh/test/l4linux-2.6/init/do_mounts.c:386 > > Now I see it, the Linux is not configured at all and thus does not know > which root filesystem to mount and panics. > I.e. you cannot only write: > > module (hd0,1)/boot/fiasco_L4/bmodfs --events > module (hd0,1)/boot/fiasco_L4/vmlinuz26 > module (hd0,1)/boot/fiasco_L4/libloader.s.so > module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26 > > because that only loads the bare vmlinuz26 file without any > kernel command line configuration. Depending on what you want to do > (e.g. use a ramdisk or boot from disk) your configuration should more > look like: > > module (hd0,1)/boot/fiasco_L4/bmodfs --events > module (hd0,1)/boot/fiasco_L4/vmlinuz26 > module (hd0,1)/boot/fiasco_L4/linux26.cfg > module (hd0,1)/boot/fiasco_L4/libloader.s.so > module (hd0,1)/boot/fiasco_L4/ramdisk.rd > module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS linux26.cfg > > > The linux26.cfg file should look like: > > modpath "(hd0,1)/boot/fiasco_L4" > task "vmlinuz26" "earlyprintk=yes mem=64M root=1:0 load_ramdisk=1 > ramdisk_size=2100 l4env_rd=ramdisk.rd" > > If you want to boot from disk, something like this could work: > > modpath "(hd0,1)/boot/fiasco_L4" > task "vmlinuz26" "earlyprintk=yes mem=64M root=/dev/hda1" > > Then you do not need to load the ramdisk, of course. I modify my grub menu.list like this: title fiasco_L4Linux-2.6 kernel (hd0,1)/boot/fiasco_L4/bootstrap modaddr 0x06000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" attached 3 modules module (hd0,1)/boot/fiasco_L4/events module (hd0,1)/boot/fiasco_L4/names -events module (hd0,1)/boot/fiasco_L4/log module (hd0,1)/boot/fiasco_L4/dm_phys --isa=0x00800000 -v --events module (hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events module (hd0,1)/boot/fiasco_L4/rtc --events module (hd0,1)/boot/fiasco_L4/l4io -noirq --events module (hd0,1)/boot/fiasco_L4/l4exec --events # module (hd0,1)/boot/faisco_L4/con -l4io -cpuload --events # module (hd0,1)/boot/fiasco_L4/tftp -i module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/linux26.cfg module (hd0,1)/boot/fiasco_L4/libloader.s.so # module (hd0,1)/boot/fiasco_L4/ramdisk.rd module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS linux26.cfg Now there is no panic error. But there is no more information to be output. The minicom log is like this: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 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: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427892kB ( 418MB) received RAM from Sigma0 23276kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:3 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 13 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys --isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074b66ce ] passing module (hd0,1)/boot/fiasco_L4/linux26.cfg [ 074b7000-074b705b ] passing module (hd0,1)/boot/fiasco_L4/libloader.s.so [ 074b8000-0755b661 ] entry at 00069120 via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) #0e: loading "(hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS linux26.cfg" from [0755c000-076406f5] to [01300000-0132792a][01328000-01353000] entry at 0006a094 via trampoline page code symbols at [1b86e000-1b875000] (28kB), lines at [1b854000-1b86e000] (104kB) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:04.07.2006 Time:21:19:06 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x0013a000 7 12 MAPPED DMphys | 0x0013a000-0x001d2000 -- -- DENIED DMphys | 0x001d2000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e4000 -- -- DENIED DMphys | 0x002e4000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043c000 -- -- DENIED DMphys | 0x0043c000-0x009e8000 7 12 MAPPED DMphys | 0x009e8000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bf1000 -- -- DENIED DMphys | 0x00bf1000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108b000 -- -- DENIED DMphys | 0x0108b000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114e000 -- -- DENIED DMphys | 0x0114e000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01258000 -- -- DENIED DMphys | 0x01258000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01353000 -- -- DENIED DMphys | 0x01353000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01416000 -- -- DENIED DMphys | 0x01416000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154e000 -- -- DENIED DMphys | 0x0154e000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x066b2000 0 12 MAPPED DMphys | 0x066b2000-0x0755c000 -- -- DENIED DMphys | 0x0755c000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b854000 0 12 MAPPED DMphys | 0x1b854000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 424112KB total, 424112KB free, 32KB reserved DMphys | 0x009e8000-0x00b80000 ( 1632KB, 2MB) DMphys | 0x00bf1000-0x01080000 ( 4668KB, 5MB) DMphys | 0x0108b000-0x01100000 ( 468KB, 0MB) DMphys | 0x0114e000-0x01220000 ( 840KB, 1MB) DMphys | 0x01258000-0x01300000 ( 672KB, 1MB) DMphys | 0x01353000-0x01400000 ( 692KB, 1MB) DMphys | 0x01416000-0x01500000 ( 936KB, 1MB) DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) DMphys | 0x0154e000-0x066b2000 ( 83344KB, 81MB) DMphys | 0x0755c000-0x1b854000 (330720KB, 323MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x0013a000 ( 232KB, 0MB) DMphys | 0x001d2000-0x002d0000 ( 1016KB, 1MB) DMphys | 0x002e4000-0x00400000 ( 1136KB, 1MB) DMphys | 0x0043c000-0x009e8000 ( 5808KB, 6MB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/fiasco_L4/vmlinuz26" (14354kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/linux26.cfg" (1kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/libloader.s.so" (654kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec11ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec120000-ec13ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec160000-ec1600ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec161000-ec1617ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec162000-ec1620ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d01f : Intel Corp. 82544GC Gigabit Ethernet Controller (Copper io : ) io | d400-d4ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d800-d87f : VIA Technologies, Inc. IEEE 1394 Host Controller io | dc00-dc1f : VIA Technologies, Inc. USB io | e000-e01f : VIA Technologies, Inc. USB (#2) io | e400-e41f : VIA Technologies, Inc. USB (#3) io | e800-e80f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | ec00-ecff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 882922 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 26225 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00006340 => 00016340 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#f: Starting at l4loader_init (00016bd0) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 00400000 => 00400000 exec | vmlinuz26: Packed 719273 bytes of symbols exec | vmlinuz26: Packed 1770776 bytes of lines loader | vmlinuz26,#f: Continue at l4env_init (00016be0, libloader.s.so) l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (root@slackware) (gcc version 3.3.6) #2 Mon J l4lx : ul 3 08:57:36 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (3 args): earlyprintk=yes mem=64M root=/dev/hdb1 l4lx | Image: 00400000 - 006f0000 [3008 KiB]. l4lx | Areas: Text: 00400000 - 00615000 [2132kB] (a bit longer) l4lx | Data: 00615000 - 0065c50c [285kB] l4lx | Initdata: 00660000 - 00690000 [192kB] l4lx | BSS: 00690000 - 006eee50 [379kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 0065e000 size = 598016 l4lx | sec-w-init: virt: 0x0065e000 to 0x006effff [584 KiB] l4lx | sec-w-init: Number of physical regions: 1, 598016 Bytes l4lx | sec-w-init: 1: Phys: 0x0141b000 to 0x014ad000, Size: 598016 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | PF: F.04: pfaddr = 0065e002 pc = 00666c5b (rw) l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043c000 to 0x0063c000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x05800000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1643 entries). l4lx | PF: F.04: pfaddr = 006852c7 pc = 0066cf84 (rw, T) l4lx | PF: F.04: pfaddr = 006844af pc = 00668b73 (rw, T) l4lx | PF: F.04: pfaddr = b01fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b01ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) l4lx | PF: F.04: pfaddr = b02fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b02ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.06 (IRQ12) l4lx | PF: F.04: pfaddr = b03fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b03ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.07 (Idler) l4lx | PF: F.04: pfaddr = b04fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b04ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.08 (IRQ17) l4lx | PF: F.04: pfaddr = b05fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b05ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.09 (IRQ16) l4lx | PF: F.04: pfaddr = b06fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b06ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ15) l4lx | PF: F.04: pfaddr = b07fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b07ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ14) l4lx | PF: F.04: pfaddr = b08fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b08ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ13) l4lx | PF: F.04: pfaddr = b09fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b09ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ11) l4lx | PF: F.04: pfaddr = b0afe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0aff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ10) l4lx | PF: F.04: pfaddr = b0bfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0bff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0f (IRQ9) l4lx | PF: F.04: pfaddr = b0cfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0cff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.10 (IRQ7) l4lx | PF: F.04: pfaddr = b0dfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0dff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.11 (IRQ6) l4lx | PF: F.04: pfaddr = b0efe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0eff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.12 (IRQ5) l4lx | PF: F.04: pfaddr = b0ffe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0fff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) When executing here the light of harddisk would flush very frequently. Later the light stop flushing and nothing could be output. chenggh

1 0

Re: panic in L4Linux booting process
by Adam Lackorzynski 04 Jul '06

04 Jul '06

On Tue Jul 04, 2006 at 12:18:41 +0800, chenggh wrote: > #2 00660b4f : mount_block_root + 0x8f > /home/chenggh/test/l4linux-2.6/init/do_mounts.c:312 > #3 00660d87 : mount_root + 0x87 > /home/chenggh/test/l4linux-2.6/init/do_mounts.c:386 Now I see it, the Linux is not configured at all and thus does not know which root filesystem to mount and panics. I.e. you cannot only write: module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/libloader.s.so module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26 because that only loads the bare vmlinuz26 file without any kernel command line configuration. Depending on what you want to do (e.g. use a ramdisk or boot from disk) your configuration should more look like: module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/linux26.cfg module (hd0,1)/boot/fiasco_L4/libloader.s.so module (hd0,1)/boot/fiasco_L4/ramdisk.rd module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS linux26.cfg The linux26.cfg file should look like: modpath "(hd0,1)/boot/fiasco_L4" task "vmlinuz26" "earlyprintk=yes mem=64M root=1:0 load_ramdisk=1 ramdisk_size=2100 l4env_rd=ramdisk.rd" If you want to boot from disk, something like this could work: modpath "(hd0,1)/boot/fiasco_L4" task "vmlinuz26" "earlyprintk=yes mem=64M root=/dev/hda1" Then you do not need to load the ramdisk, of course. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: panic in L4Linux booting process
by chenggh 04 Jul '06

04 Jul '06

On Tuesday 04 July 2006 00:52, Adam Lackorzynski wrote: > On Mon Jul 03, 2006 at 10:32:25 +0800, chenggh wrote: > > l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) > > l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) > > l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) > > l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) > > l4lx | panic: going to sleep forever, bye > > Then go into the kernel debugger and issue bttf.4 to get a backtrace of > thread f.4. Please show me this backtrace. If there are no line > information in the backtrace please look the addresses up in an objdump > of vmlinux. All the log is following and the backtrace of thread f.4 is in the end of the log: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 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: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427896kB ( 418MB) received RAM from Sigma0 23272kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:2 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 12 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys --isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074b66ce ] passing module (hd0,1)/boot/fiasco_L4/libloader.s.so [ 074b7000-0755a661 ] entry at 000690ec via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) #0e: loading "(hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26" from [0755b000-0763f6f5] to [01300000-0132792a][01328000-01353000] entry at 0006a090 via trampoline page code symbols at [1b86e000-1b875000] (28kB), lines at [1b854000-1b86e000] (104kB) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:04.07.2006 Time:11:57:04 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x0013a000 7 12 MAPPED DMphys | 0x0013a000-0x001d2000 -- -- DENIED DMphys | 0x001d2000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e4000 -- -- DENIED DMphys | 0x002e4000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043c000 -- -- DENIED DMphys | 0x0043c000-0x009e8000 7 12 MAPPED DMphys | 0x009e8000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bf1000 -- -- DENIED DMphys | 0x00bf1000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108b000 -- -- DENIED DMphys | 0x0108b000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114e000 -- -- DENIED DMphys | 0x0114e000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01258000 -- -- DENIED DMphys | 0x01258000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01353000 -- -- DENIED DMphys | 0x01353000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01416000 -- -- DENIED DMphys | 0x01416000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154e000 -- -- DENIED DMphys | 0x0154e000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x066b2000 0 12 MAPPED DMphys | 0x066b2000-0x0755b000 -- -- DENIED DMphys | 0x0755b000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b854000 0 12 MAPPED DMphys | 0x1b854000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 424116KB total, 424116KB free, 32KB reserved DMphys | 0x009e8000-0x00b80000 ( 1632KB, 2MB) DMphys | 0x00bf1000-0x01080000 ( 4668KB, 5MB) DMphys | 0x0108b000-0x01100000 ( 468KB, 0MB) DMphys | 0x0114e000-0x01220000 ( 840KB, 1MB) DMphys | 0x01258000-0x01300000 ( 672KB, 1MB) DMphys | 0x01353000-0x01400000 ( 692KB, 1MB) DMphys | 0x01416000-0x01500000 ( 936KB, 1MB) DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) DMphys | 0x0154e000-0x066b2000 ( 83344KB, 81MB) DMphys | 0x0755b000-0x1b854000 (330724KB, 323MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x0013a000 ( 232KB, 0MB) DMphys | 0x001d2000-0x002d0000 ( 1016KB, 1MB) DMphys | 0x002e4000-0x00400000 ( 1136KB, 1MB) DMphys | 0x0043c000-0x009e8000 ( 5808KB, 6MB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/fiasco_L4/vmlinuz26" (14354kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/libloader.s.so" (654kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec11ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec120000-ec13ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec160000-ec1600ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec161000-ec1617ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec162000-ec1620ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d01f : Intel Corp. 82544GC Gigabit Ethernet Controller (Copper io : ) io | d400-d4ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d800-d87f : VIA Technologies, Inc. IEEE 1394 Host Controller io | dc00-dc1f : VIA Technologies, Inc. USB io | e000-e01f : VIA Technologies, Inc. USB (#2) io | e400-e41f : VIA Technologies, Inc. USB (#3) io | e800-e80f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | ec00-ecff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler loader | "vmlinuz26" is a valid binary image exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 882922 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 26225 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00006340 => 00016340 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#f: Starting at l4loader_init (00016bd0) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 00400000 => 00400000 exec | vmlinuz26: Packed 719273 bytes of symbols exec | vmlinuz26: Packed 1770776 bytes of lines loader | vmlinuz26,#f: Continue at l4env_init (00016be0, libloader.s.so) l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (root@slackware) (gcc version 3.3.6) #2 Mon J l4lx : ul 3 08:57:36 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (0 args): l4lx | Image: 00400000 - 006f0000 [3008 KiB]. l4lx | Areas: Text: 00400000 - 00615000 [2132kB] (a bit longer) l4lx | Data: 00615000 - 0065c50c [285kB] l4lx | Initdata: 00660000 - 00690000 [192kB] l4lx | BSS: 00690000 - 006eee50 [379kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 0065e000 size = 598016 l4lx | sec-w-init: virt: 0x0065e000 to 0x006effff [584 KiB] l4lx | sec-w-init: Number of physical regions: 1, 598016 Bytes l4lx | sec-w-init: 1: Phys: 0x01416000 to 0x014a8000, Size: 598016 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | PF: F.04: pfaddr = 0065e002 pc = 00666c5b (rw) l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 32MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043c000 to 0x0063c000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x02bfffff [32768 KiB] l4lx | Main memory: Number of physical regions: 1, 33554432 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x03800000, Size: 33554432 l4lx | Filling lower ptabs... l4lx | Done (1643 entries). l4lx | PF: F.04: pfaddr = 006852c7 pc = 0066cf84 (rw, T) l4lx | PF: F.04: pfaddr = 006844af pc = 00668b73 (rw, T) l4lx | PF: F.04: pfaddr = b01fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b01ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) l4lx | PF: F.04: pfaddr = b02fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b02ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.06 (IRQ12) l4lx | PF: F.04: pfaddr = b03fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b03ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.07 (Idler) l4lx | PF: F.04: pfaddr = b04fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b04ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.08 (IRQ17) l4lx | PF: F.04: pfaddr = b05fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b05ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.09 (IRQ16) l4lx | PF: F.04: pfaddr = b06fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b06ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ15) l4lx | PF: F.04: pfaddr = b07fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b07ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ14) l4lx | PF: F.04: pfaddr = b08fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b08ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ13) l4lx | PF: F.04: pfaddr = b09fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b09ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ11) l4lx | PF: F.04: pfaddr = b0afe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0aff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ10) l4lx | PF: F.04: pfaddr = b0bfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0bff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0f (IRQ9) l4lx | PF: F.04: pfaddr = b0cfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0cff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.10 (IRQ7) l4lx | PF: F.04: pfaddr = b0dfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0dff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.11 (IRQ6) l4lx | PF: F.04: pfaddr = b0efe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0eff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.12 (IRQ5) l4lx | PF: F.04: pfaddr = b0ffe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0fff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) l4lx | panic: going to sleep forever, bye ---------------------------------------------------------IP: f0013b04 --IRQ ENTRY (0.00) jdb: q (0.00) jdb: w (0.00) jdb: b(0.00) jdb: bt [a]ddr/[t]hread thread=4 backtrace (thread 4.00, fp=001b3734, pc=0013d51a): #1 0013d51a : pager + 0x1aa /home/chenggh/test/l4/pkg/roottask/server/src/pager.c:688 #2 0013a128 : rmgr_main + 0x78 /home/chenggh/test/l4/pkg/roottask/server/src/rmgr.c:101 #3 001268d5 : init + 0x95 /home/chenggh/test/l4/pkg/roottask/server/src/init.c:1737 --kernel-bt-follows-- #0 f0007120 #1 f00069d8 #2 f000f50f #3 f000debf #4 f002c2b3 (0.00) jdb: b(0.00) jdb: bt [a]ddr/[t]hread backtrace (thread 0.00, fp=00000000, pc=00000000): --kernel-bt-follows-- #2 f001ba7c #3 f001db2a #4 f00182a1 #5 f0018848 #6 f000af7a #7 f000947a #8 f002b4f4 #9 f0013b04 #10 f002b7cb (0.00) jdb: bt [a]ddr/[t]hread thread=f.4 backtrace (thread f.04, fp=01081f58, pc=0040152d): #1 0040152d : l4x_blink + 0x2d /home/chenggh/test/l4linux-2.6/arch/l4/kernel/main.c:666 #2 00660b4f : mount_block_root + 0x8f /home/chenggh/test/l4linux-2.6/init/do_mounts.c:312 #3 00660d87 : mount_root + 0x87 /home/chenggh/test/l4linux-2.6/init/do_mounts.c:386 #4 00660ddc : prepare_namespace + 0x4c /home/chenggh/test/l4linux-2.6/init/do_mounts.c:421 #5 0040018f : init + 0x12f /home/chenggh/test/l4linux-2.6/init/main.c:699 #6 004063a9 : kernel_thread_start + 0x29 /home/chenggh/test/l4linux-2.6/arch/l4/kernel/arch-i386/process.c:199 #7 0040637e : ret_kernel_thread_start + 0x6 /home/chenggh/test/l4linux-2.6/arch/l4/kernel/arch-i386/process.c:174 #8 00400021 : rest_init + 0x21 /home/chenggh/test/l4linux-2.6/init/main.c:403 #9 00660726 : start_kernel + 0x176 /home/chenggh/test/l4linux-2.6/init/main.c:546 #10 00666d5f : l4env_linux_startup + 0xbf /home/chenggh/test/l4linux-2.6/arch/l4/kernel/main.c:695 #11 00018733 : l4th_thread_start + 0x73 /home/chenggh/test/l4/pkg/thread/lib/src/create.c:72 #12 0001ba06 : l4th_thread_entry + 0x16 /home/chenggh/test/l4/pkg/thread/lib/src/l4.c:93 #13 001e0801 --kernel-bt-follows-- #0 f0007120 #1 f00069d8 #2 f000f50f #3 f000debf #4 f002b838 (0.00) jdb: q (0.00) jdb: u f0013b04 <enter_kdebug ("IRQ ENTRY") f0013b0f mov 0x8(%ebx),%edx f0013b12 lea 0xffffffff(%edx),%ecx f0013b15 cmp $0x7,%ecx f0013b18 ja 0xf0013b30 f0013b1a in $0x21,%al f0013b1c mov $0xfffffffe,%esi f0013b21 mov %eax,%edx f0013b23 rol %cl,%esi f0013b25 and %esi,%edx f0013b27 mov %edx,%eax f0013b29 out %al,$0x21 f0013b2b jmp 0xf00139b0 f0013b30 in $0xa1,%al f0013b32 mov $0xfffffffe,%ebx f0013b37 lea 0xfffffff7(%edx),%ecx f0013b3a rol %cl,%ebx f0013b3c and %ebx,%eax f0013b3e out %al,$0xa1 f0013b40 jmp 0xf00139b0 f0013b45 mov 0x14(%ecx),%edx f0013b48 lea 0xffffffff(%edx),%ecx f0013b4b cmp $0x7,%ecx f0013b4e ja 0xf0013b5f <Space>=lines modedis: <f0013b04> task 0 [Headers] [AT&T] f0013b04 <enter_kdebug ("IRQ ENTRY") f0013b0f mov 0x8(%ebx),%edx f0013b12 lea 0xffffffff(%edx),%ecx f0013b15 cmp $0x7,%ecx f0013b18 ja 0xf0013b30 f0013b1a in $0x21,%al f0013b1c mov $0xfffffffe,%esi f0013b21 mov %eax,%edx f0013b23 rol %cl,%esi f0013b25 and %esi,%edx f0013b27 mov %edx,%eax f0013b29 out %al,$0x21 f0013b2b jmp 0xf00139b0 f0013b30 in $0xa1,%al f0013b32 mov $0xfffffffe,%ebx f0013b37 lea 0xfffffff7(%edx),%ecx f0013b3a rol %cl,%ebx f0013b3c and %ebx,%eax f0013b3e out %al,$0xa1 f0013b40 jmp 0xf00139b0 f0013b45 mov 0x14(%ecx),%edx f0013b48 lea 0xffffffff(%edx),%ecx f0013b4b cmp $0x7,%ecx f0013b4e ja 0xf0013b5f <Space>=lines modedis: <f0013b04> task 0 [Headers] [AT&T] f0013b04 <enter_kdebug ("IRQ ENTRY") f0013b0f mov 0x8(%ebx),%edx f0013b12 lea 0xffffffff(%edx),%ecx f0013b15 cmp $0x7,%ecx f0013b18 ja 0xf0013b30 f0013b1a in $0x21,%al f0013b1c mov $0xfffffffe,%esi f0013b21 mov %eax,%edx f0013b23 rol %cl,%esi f0013b25 and %esi,%edx f0013b27 mov %edx,%eax f0013b29 out %al,$0x21 f0013b2b jmp 0xf00139b0 f0013b30 in $0xa1,%al f0013b32 mov $0xfffffffe,%ebx f0013b37 lea 0xfffffff7(%edx),%ecx f0013b3a rol %cl,%ebx f0013b3c and %ebx,%eax f0013b3e out %al,$0xa1 f0013b40 jmp 0xf00139b0 f0013b45 mov 0x14(%ecx),%edx f0013b48 lea 0xffffffff(%edx),%ecx f0013b4b cmp $0x7,%ecx f0013b4e ja 0xf0013b5f <Space>=lines modedis: <f0013b04> task 0 [Headers] [AT&T] (0.00) jdb: s (0.00) jdb: 悙 �Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 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: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427896kB ( 418MB) received RAM from Sigma0 23272kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:2 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 12 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys --isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing exec | libloader.s.so: Loading exec | libloader.s.so: Saved 26225 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00006340 => 00016340 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#f: Starting at l4loader_init (00016bd0) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 00400000 => 00400000 exec | vmlinuz26: Packed 719273 bytes of symbols exec | vmlinuz26: Packed 1770776 bytes of lines loader | vmlinuz26,#f: Continue at l4env_init (00016be0, libloader.s.so) l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (root@slackware) (gcc version 3.3.6) #2 Mon J l4lx : ul 3 08:57:36 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (0 args): l4lx | Image: 00400000 - 006f0000 [3008 KiB]. l4lx | Areas: Text: 00400000 - 00615000 [2132kB] (a bit longer) l4lx | Data: 00615000 - 0065c50c [285kB] l4lx | Initdata: 00660000 - 00690000 [192kB] l4lx | BSS: 00690000 - 006eee50 [379kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 0065e000 size = 598016 l4lx | sec-w-init: virt: 0x0065e000 to 0x006effff [584 KiB] l4lx | sec-w-init: Number of physical regions: 1, 598016 Bytes l4lx | sec-w-init: 1: Phys: 0x01416000 to 0x014a8000, Size: 598016 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | PF: F.04: pfaddr = 0065e002 pc = 00666c5b (rw) l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 32MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043c000 to 0x0063c000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x02bfffff [32768 KiB] l4lx | Main memory: Number of physical regions: 1, 33554432 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x03800000, Size: 33554432 l4lx | Filling lower ptabs... l4lx | Done (1643 entries). l4lx | PF: F.04: pfaddr = 006852c7 pc = 0066cf84 (rw, T) l4lx | PF: F.04: pfaddr = 006844af pc = 00668b73 (rw, T) l4lx | PF: F.04: pfaddr = b01fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b01ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) l4lx | PF: F.04: pfaddr = b02fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b02ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.06 (IRQ12) l4lx | PF: F.04: pfaddr = b03fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b03ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.07 (Idler) l4lx | PF: F.04: pfaddr = b04fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b04ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.08 (IRQ17) l4lx | PF: F.04: pfaddr = b05fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b05ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.09 (IRQ16) l4lx | PF: F.04: pfaddr = b06fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b06ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ15) l4lx | PF: F.04: pfaddr = b07fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b07ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ14) l4lx | PF: F.04: pfaddr = b08fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b08ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ13) l4lx | PF: F.04: pfaddr = b09fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b09ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ11) l4lx | PF: F.04: pfaddr = b0afe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0aff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ10) l4lx | PF: F.04: pfaddr = b0bfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0bff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0f (IRQ9) l4lx | PF: F.04: pfaddr = b0cfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0cff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.10 (IRQ7) l4lx | PF: F.04: pfaddr = b0dfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0dff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.11 (IRQ6) l4lx | PF: F.04: pfaddr = b0efe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0eff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.12 (IRQ5) l4lx | PF: F.04: pfaddr = b0ffe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0fff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) l4lx | panic: going to sleep forever, bye ---------------------------------------------------------IP: f0013b04 --IRQ ENTRY (0.00) jdb: w (0.00) jdb: br bpn=(0.00) jdb: bt [a]ddr/[t]hread thread=f.4 backtrace (thread f.04, fp=01081f58, pc=0040152d): #1 0040152d : l4x_blink + 0x2d /home/chenggh/test/l4linux-2.6/arch/l4/kernel/main.c:666 #2 00660b4f : mount_block_root + 0x8f /home/chenggh/test/l4linux-2.6/init/do_mounts.c:312 #3 00660d87 : mount_root + 0x87 /home/chenggh/test/l4linux-2.6/init/do_mounts.c:386 #4 00660ddc : prepare_namespace + 0x4c /home/chenggh/test/l4linux-2.6/init/do_mounts.c:421 #5 0040018f : init + 0x12f /home/chenggh/test/l4linux-2.6/init/main.c:699 #6 004063a9 : kernel_thread_start + 0x29 /home/chenggh/test/l4linux-2.6/arch/l4/kernel/arch-i386/process.c:199 #7 0040637e : ret_kernel_thread_start + 0x6 /home/chenggh/test/l4linux-2.6/arch/l4/kernel/arch-i386/process.c:174 #8 00400021 : rest_init + 0x21 /home/chenggh/test/l4linux-2.6/init/main.c:403 #9 00660726 : start_kernel + 0x176 /home/chenggh/test/l4linux-2.6/init/main.c:546 #10 00666d5f : l4env_linux_startup + 0xbf /home/chenggh/test/l4linux-2.6/arch/l4/kernel/main.c:695 #11 00018733 : l4th_thread_start + 0x73 /home/chenggh/test/l4/pkg/thread/lib/src/create.c:72 #12 0001ba06 : l4th_thread_entry + 0x16 /home/chenggh/test/l4/pkg/thread/lib/src/l4.c:93 #13 001e0801 --kernel-bt-follows-- #0 f0007120 #1 f00069d8 #2 f000f50f #3 f000debf #4 f002b838 (0.00) jdb: � (0.00) jdb: � (0.00) jdb: � (0.00) jdb: � (0.00) jdb: � (0.00) jdb: � (0.00) jdb: Thank you chenggh

1 0

Re: panic in L4Linux booting process
by Adam Lackorzynski 03 Jul '06

03 Jul '06

On Mon Jul 03, 2006 at 10:32:25 +0800, chenggh wrote: > l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) > l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) > l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) > l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) > l4lx | panic: going to sleep forever, bye Then go into the kernel debugger and issue bttf.4 to get a backtrace of thread f.4. Please show me this backtrace. If there are no line information in the backtrace please look the addresses up in an objdump of vmlinux. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: panic in L4Linux booting process
by chenggh 03 Jul '06

03 Jul '06

On Monday 03 July 2006 02:45, Adam Lackorzynski wrote: > On Fri Jun 30, 2006 at 20:13:34 +0800, chenggh wrote: > > names | Starting thread listening for `exit' events > > simplets| Configured for 300 tasks. > > DMphys | [8.0] dm_phys/server/src/main.c:115:__get_num(): > > DMphys | Error: DMphys: invalid number: 'sa=0x00800000'! > > DMphys | [8.0] dm_phys/server/src/main.c:153:__pool_config(): > > DMphys | Error: DMphys: invalid size for pool 7: sa=0x00800000! > > > > > > module (hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events > > Write --isa=0x00800000 to get the above error fixed (two '_'). > > > Please enable 'Show page faults and exceptions of Linux server' under > L4Linux configuration -> Debugging options in the L4Linux conifguration > menu. When you try again, there should be a line starting with 'EX: ' > just before the panic. On this line, there will be 'pc = 0x12345678', > look up this address with a disassemble of your vmlinux binary. Then > show us where this is in the source. I enable "Show page faults and exceptions of Linux server". But there is not a line starting with "EX:". The following is my log. Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 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: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427896kB ( 418MB) received RAM from Sigma0 23272kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:2 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 12 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys --isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074b66ce ] passing module (hd0,1)/boot/fiasco_L4/libloader.s.so [ 074b7000-0755a661 ] entry at 000690ec via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) #0e: loading "(hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26" from [0755b000-0763f6f5] to [01300000-0132792a][01328000-01353000] entry at 0006a090 via trampoline page code symbols at [1b86e000-1b875000] (28kB), lines at [1b854000-1b86e000] (104kB) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:03.07.2006 Time:10:20:10 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x0013a000 7 12 MAPPED DMphys | 0x0013a000-0x001d2000 -- -- DENIED DMphys | 0x001d2000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e4000 -- -- DENIED DMphys | 0x002e4000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043c000 -- -- DENIED DMphys | 0x0043c000-0x009e8000 7 12 MAPPED DMphys | 0x009e8000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bf1000 -- -- DENIED DMphys | 0x00bf1000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108b000 -- -- DENIED DMphys | 0x0108b000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114e000 -- -- DENIED DMphys | 0x0114e000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01258000 -- -- DENIED DMphys | 0x01258000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01353000 -- -- DENIED DMphys | 0x01353000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01416000 -- -- DENIED DMphys | 0x01416000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154e000 -- -- DENIED DMphys | 0x0154e000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x066b2000 0 12 MAPPED DMphys | 0x066b2000-0x0755b000 -- -- DENIED DMphys | 0x0755b000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b854000 0 12 MAPPED DMphys | 0x1b854000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 424116KB total, 424116KB free, 32KB reserved DMphys | 0x009e8000-0x00b80000 ( 1632KB, 2MB) DMphys | 0x00bf1000-0x01080000 ( 4668KB, 5MB) DMphys | 0x0108b000-0x01100000 ( 468KB, 0MB) DMphys | 0x0114e000-0x01220000 ( 840KB, 1MB) DMphys | 0x01258000-0x01300000 ( 672KB, 1MB) DMphys | 0x01353000-0x01400000 ( 692KB, 1MB) DMphys | 0x01416000-0x01500000 ( 936KB, 1MB) DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) DMphys | 0x0154e000-0x066b2000 ( 83344KB, 81MB) DMphys | 0x0755b000-0x1b854000 (330724KB, 323MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x0013a000 ( 232KB, 0MB) DMphys | 0x001d2000-0x002d0000 ( 1016KB, 1MB) DMphys | 0x002e4000-0x00400000 ( 1136KB, 1MB) DMphys | 0x0043c000-0x009e8000 ( 5808KB, 6MB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/fiasco_L4/vmlinuz26" (14354kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/libloader.s.so" (654kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec11ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec120000-ec13ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec160000-ec1600ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec161000-ec1617ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec162000-ec1620ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d01f : Intel Corp. 82544GC Gigabit Ethernet Controller (Copper io : ) io | d400-d4ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d800-d87f : VIA Technologies, Inc. IEEE 1394 Host Controller io | dc00-dc1f : VIA Technologies, Inc. USB io | e000-e01f : VIA Technologies, Inc. USB (#2) io | e400-e41f : VIA Technologies, Inc. USB (#3) io | e800-e80f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | ec00-ecff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler loader | "vmlinuz26" is a valid binary image exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 882922 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 26225 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00006340 => 00016340 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#f: Starting at l4loader_init (00016bd0) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 00400000 => 00400000 exec | vmlinuz26: Packed 719273 bytes of symbols exec | vmlinuz26: Packed 1770776 bytes of lines loader | vmlinuz26,#f: Continue at l4env_init (00016be0, libloader.s.so) l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (root@slackware) (gcc version 3.3.6) #2 Mon J l4lx : ul 3 08:57:36 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (0 args): l4lx | Image: 00400000 - 006f0000 [3008 KiB]. l4lx | Areas: Text: 00400000 - 00615000 [2132kB] (a bit longer) l4lx | Data: 00615000 - 0065c50c [285kB] l4lx | Initdata: 00660000 - 00690000 [192kB] l4lx | BSS: 00690000 - 006eee50 [379kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 0065e000 size = 598016 l4lx | sec-w-init: virt: 0x0065e000 to 0x006effff [584 KiB] l4lx | sec-w-init: Number of physical regions: 1, 598016 Bytes l4lx | sec-w-init: 1: Phys: 0x01416000 to 0x014a8000, Size: 598016 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | PF: F.04: pfaddr = 0065e002 pc = 00666c5b (rw) l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 32MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043c000 to 0x0063c000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x02bfffff [32768 KiB] l4lx | Main memory: Number of physical regions: 1, 33554432 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x03800000, Size: 33554432 l4lx | Filling lower ptabs... l4lx | Done (1643 entries). l4lx | PF: F.04: pfaddr = 006852c7 pc = 0066cf84 (rw, T) l4lx | PF: F.04: pfaddr = 006844af pc = 00668b73 (rw, T) l4lx | PF: F.04: pfaddr = b01fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b01ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) l4lx | PF: F.04: pfaddr = b02fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b02ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.06 (IRQ12) l4lx | PF: F.04: pfaddr = b03fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b03ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.07 (Idler) l4lx | PF: F.04: pfaddr = b04fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b04ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.08 (IRQ17) l4lx | PF: F.04: pfaddr = b05fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b05ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.09 (IRQ16) l4lx | PF: F.04: pfaddr = b06fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b06ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ15) l4lx | PF: F.04: pfaddr = b07fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b07ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ14) l4lx | PF: F.04: pfaddr = b08fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b08ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ13) l4lx | PF: F.04: pfaddr = b09fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b09ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ11) l4lx | PF: F.04: pfaddr = b0afe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0aff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ10) l4lx | PF: F.04: pfaddr = b0bfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0bff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.0f (IRQ9) l4lx | PF: F.04: pfaddr = b0cfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0cff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.10 (IRQ7) l4lx | PF: F.04: pfaddr = b0dfe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0dff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.11 (IRQ6) l4lx | PF: F.04: pfaddr = b0efe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0eff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.12 (IRQ5) l4lx | PF: F.04: pfaddr = b0ffe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b0fff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) l4lx | PF: F.04: pfaddr = b10fe002 pc = 00016db6 (rw) l4lx | PF: F.04: pfaddr = b10ff002 pc = 00016db6 (rw) l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) l4lx | panic: going to sleep forever, bye Cheng

1 0

Re: panic in L4Linux booting process
by Adam Lackorzynski 02 Jul '06

02 Jul '06

On Fri Jun 30, 2006 at 20:13:34 +0800, chenggh wrote: > names | Starting thread listening for `exit' events > simplets| Configured for 300 tasks. > DMphys | [8.0] dm_phys/server/src/main.c:115:__get_num(): > DMphys | Error: DMphys: invalid number: 'sa=0x00800000'! > DMphys | [8.0] dm_phys/server/src/main.c:153:__pool_config(): > DMphys | Error: DMphys: invalid size for pool 7: sa=0x00800000! > module (hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events Write --isa=0x00800000 to get the above error fixed (two '_'). Please enable 'Show page faults and exceptions of Linux server' under L4Linux configuration -> Debugging options in the L4Linux conifguration menu. When you try again, there should be a line starting with 'EX: ' just before the panic. On this line, there will be 'pc = 0x12345678', look up this address with a disassemble of your vmlinux binary. Then show us where this is in the source. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

panic in L4Linux booting process
by chenggh 30 Jun '06

30 Jun '06

Hi, everyone: In the L4Linux booting process it is panic. The log is following: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 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: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427936kB ( 418MB) received RAM from Sigma0 23232kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:2 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 12 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074ac99d ] passing module (hd0,1)/boot/fiasco_L4/libloader.s.so [ 074ad000-07550661 ] entry at 000690ec via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) #0e: loading "(hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26" from [07551000-076356f5] to [01300000-0132792a][01328000-01353000] entry at 0006a090 via trampoline page code symbols at [1b86e000-1b875000] (28kB), lines at [1b854000-1b86e000] (104kB) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. DMphys | [8.0] dm_phys/server/src/main.c:115:__get_num(): DMphys | Error: DMphys: invalid number: 'sa=0x00800000'! DMphys | [8.0] dm_phys/server/src/main.c:153:__pool_config(): DMphys | Error: DMphys: invalid size for pool 7: sa=0x00800000! rtc | Date:15.06.2006 Time:09:43:32 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x0013a000 0 12 MAPPED DMphys | 0x0013a000-0x001d2000 -- -- DENIED DMphys | 0x001d2000-0x002d0000 0 12 MAPPED DMphys | 0x002d0000-0x002e4000 -- -- DENIED DMphys | 0x002e4000-0x00400000 0 12 MAPPED DMphys | 0x00400000-0x0043c000 -- -- DENIED DMphys | 0x0043c000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bf1000 -- -- DENIED DMphys | 0x00bf1000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108b000 -- -- DENIED DMphys | 0x0108b000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114e000 -- -- DENIED DMphys | 0x0114e000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01258000 -- -- DENIED DMphys | 0x01258000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01353000 -- -- DENIED DMphys | 0x01353000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01416000 -- -- DENIED DMphys | 0x01416000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154e000 -- -- DENIED DMphys | 0x0154e000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x066b2000 0 12 MAPPED DMphys | 0x066b2000-0x07551000 -- -- DENIED DMphys | 0x07551000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b854000 0 12 MAPPED DMphys | 0x1b854000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 432348KB total, 432348KB free, 32KB reserved DMphys | 0x00100000-0x0013a000 ( 232KB, 0MB) DMphys | 0x001d2000-0x002d0000 ( 1016KB, 1MB) DMphys | 0x002e4000-0x00400000 ( 1136KB, 1MB) DMphys | 0x0043c000-0x00b80000 ( 7440KB, 7MB) DMphys | 0x00bf1000-0x01080000 ( 4668KB, 5MB) DMphys | 0x0108b000-0x01100000 ( 468KB, 0MB) DMphys | 0x0114e000-0x01220000 ( 840KB, 1MB) DMphys | 0x01258000-0x01300000 ( 672KB, 1MB) DMphys | 0x01353000-0x01400000 ( 692KB, 1MB) DMphys | 0x01416000-0x01500000 ( 936KB, 1MB) DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) DMphys | 0x0154e000-0x066b2000 ( 83344KB, 81MB) DMphys | 0x07551000-0x1b854000 (330764KB, 323MB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/fiasco_L4/vmlinuz26" (14315kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/libloader.s.so" (654kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec11ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec120000-ec13ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec160000-ec1600ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec161000-ec1617ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec162000-ec1620ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d01f : Intel Corp. 82544GC Gigabit Ethernet Controller (Copper io : ) io | d400-d4ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d800-d87f : VIA Technologies, Inc. IEEE 1394 Host Controller io | dc00-dc1f : VIA Technologies, Inc. USB io | e000-e01f : VIA Technologies, Inc. USB (#2) io | e400-e41f : VIA Technologies, Inc. USB (#3) io | e800-e80f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | ec00-ecff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler loader | "vmlinuz26" is a valid binary image exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 881541 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 26225 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00006340 => 00016340 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#f: Starting at l4loader_init (00016bd0) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 00400000 => 00400000 exec | vmlinuz26: Packed 718178 bytes of symbols exec | vmlinuz26: Packed 1762501 bytes of lines loader | vmlinuz26,#f: Continue at l4env_init (00016be0, libloader.s.so) l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (root@slackware) (gcc version 3.3.6) #1 Thu J l4lx : un 8 21:09:48 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (0 args): l4lx | Image: 00400000 - 006ee000 [3000 KiB]. l4lx | Areas: Text: 00400000 - 00613000 [2124kB] (a bit longer) l4lx | Data: 00613000 - 0065a50c [285kB] l4lx | Initdata: 0065e000 - 0068e000 [192kB] l4lx | BSS: 0068e000 - 006ece50 [379kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 0065c000 size = 598016 l4lx | sec-w-init: virt: 0x0065c000 to 0x006edfff [584 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 598016 Bytes l4lx | sec-w-init: 1: Phys: 0x01416000 to 0x0146b000, Size: 348160 l4lx | sec-w-init: 2: Phys: 0x011e3000 to 0x01220000, Size: 249856 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 32MB l4lx | Main memory: virt: 0x00800000 to 0x027fffff [32768 KiB] l4lx | Main memory: Number of physical regions: 1, 33554432 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x03800000, Size: 33554432 l4lx | Filling lower ptabs... l4lx | Done (1133 entries). l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 0f.06 (IRQ12) l4lx | l4lx_thread_create: Created thread 0f.07 (Idler) l4lx | l4lx_thread_create: Created thread 0f.08 (IRQ17) l4lx | l4lx_thread_create: Created thread 0f.09 (IRQ16) l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ15) l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ14) l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ13) l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ11) l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ10) l4lx | l4lx_thread_create: Created thread 0f.0f (IRQ9) l4lx | l4lx_thread_create: Created thread 0f.10 (IRQ7) l4lx | l4lx_thread_create: Created thread 0f.11 (IRQ6) l4lx | l4lx_thread_create: Created thread 0f.12 (IRQ5) l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ1) l4lx | panic: going to sleep forever, bye The grub configuration is following: title fiasco_L4Linux-2.6 kernel (hd0,1)/boot/fiasco_L4/bootstrap modaddr 0x06000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" attached 2 modules module (hd0,1)/boot/fiasco_L4/events module (hd0,1)/boot/fiasco_L4/names -events module (hd0,1)/boot/fiasco_L4/log module (hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events module (hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events module (hd0,1)/boot/fiasco_L4/rtc --events module (hd0,1)/boot/fiasco_L4/l4io -noirq --events module (hd0,1)/boot/fiasco_L4/l4exec --events module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/libloader.s.so module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26 Please help me! Thank you! cheng

1 0

Userland (UX) Runtime
by Michael J. Emswiler 28 Jun '06

28 Jun '06

Good evening all, I have just gotten the most recent L4 tree from CVS and did a complete UX rebuild starting from scratch. However, after building L4 and Fiasco-UX, i cannot seem to get past this one point: < Begin Paste ----------------------------------------> Fiasco-UX on Linux 2.6.16.13-4-default (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096924 [sigma0-ux] Loading Module 0x00120000-0x002bc9c4 [roottask] Copying Module 0x039be000-0x039e0c99 [hello] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Mon Jun 26 22:50:26 2006 compiled with gcc 3.4.6 for AMD Athlon CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 1463 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) < End Paste ----------------------------------------> I never see any output from Sigma0, RootTask, much less the Hello sample (as i see in other screenshots.) Is there a log that can provide me some hints? Do I need to enable debug logging specifically to see Sigma0 and RootTask outputs to the screen on startup? Further I have to kill -9 it to get unload. -- Thanks, MikeE

3 8

Re: Userland (UX) Runtime
by Michael J. Emswiler 27 Jun '06

27 Jun '06

When comparing differences between your output and the output of my K7-GCC4 binary, I notice the following differences: 1. Your kernel is 2.6.13.2, while mine is the default 10.1 kernel of 2.6.16.13-4 2. After the "Loading Module..." messages and before "Bootstrapping...", mine shows : Copying Module 0x039be000-0x039e0c99 [hello] 3. Your running a Pentium-M (I'm running a K-7), so my TLBs and Caches are different. 4. My init code/data freed is 7 pages. 5. I don't get a SIGSEGV after MIKEE: Exiting Thread::initialize(), it appears to go into a tight loop that ignores CTRL+C. Not sure what all that means but thought I'd point it out in case someone has an "Aha!" they might offer up. Thanks, MikeE On Tuesday 27 June 2006 05:28, you wrote: > Hi, > > I get the following... > > > ch12@krishna:/tmp/fiasco-ux> ./fiasco > > > Fiasco-UX on Linux 2.6.13.2-krishna (i686) > Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 > > Loading Module 0x00090000-0x00096924 [sigma0-ux] > Loading Module 0x00120000-0x002bc9c4 [roottask] > > Bootstrapping... > > Welcome to Fiasco(ux)! > DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden > Rev: Mon Jun 26 22:50:26 2006 compiled with gcc 3.4.6 for Intel Pentium > > CPU: GenuineIntel (6:9:5:16) Model: Pentium-M (Banias) at 598 MHz > > 128 Entry I TLB (4K pages) 2 Entry I TLB (4M pages) > 128 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) > 32 KB L1 I Cache (8-way associative, 64 bytes per line) > 32 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) > > MIKEE: Initializing Architecture... > MIKEE: Starting System... > MIKEE: Creating Kernel Thread... > MIKEE: Bootstrapping Kernel Thread... > MIKEE: Activating Helping Lock... > MIKEE: Initializing System Clock... > MIKEE: Initializing Scheduler... > MIKEE: Enabling Timers... > MIKEE: Bootstrapping Architecture... > MIKEE: Initialization Delay Loop... > MIKEE: Running Kernel Thread... > MIKEE: Freeing InitCall Section... > MIKEE: Initializing Idle Thread... > MIKEE: Initializing Workload... > MIKEE: Creating Sigma0 Task... > MIKEE: Creating Sigma0 Thread... > MIKEE: Initializng Sigma0 Workload... > MIKEE: Initializng Sigma0 Thread... > MIKEE: Entering Thread::initialize()... > MIKEE: Initializing Entry Frame... > MIKEE: Check for Dead Thread... > MIKEE: Resurrect Thread... > MIKEE: Check for Exception... > MIKEE: Examine Instruction Pointer... > MIKEE: Initializing Instruction Pointer... > MIKEE: Changing State... > MIKEE: Initializing Stack Pointer... > MIKEE: Check for Preempter... > MIKEE: Exiting Thread::initialize()... > Segmentation fault > > > So Fiasco-UX stops on SIGSEGV. Maybe you should also send me your > globalconfig.out from your Fiasco build directory. > > Up to now I have no glue what the problem could be... -- Thanks, MikeE

2 1

L4Env / DOPE Question
by Michael J. Emswiler 25 Jun '06

25 Jun '06

Is this the correct mailing list for raising L4Env and/or DOPE questions and comments? If not, please let me know where this should be posted. I am interested in possibly porting over OpenBinder to the L4Env / Dope environment. Was wondering if anyone has looked at this or had any thoughts or any interest? This will be my first port of something to the L4Env (perhaps I should start with something smaller), so any tips on porting (or links thereto) would be greatly appreciated. -- Thanks, MikeE

3 2

Binary Compatibility of compiled programs in different DROPS versions?
by Arthur Mielimonka 25 Jun '06

25 Jun '06

Hi, can you tell me if programs compiled for a specific DROPS version are runable on other DROPS versions as well? Or is it necessary to compile the program on each target machine? I do not talk about programs like dm_phys or rmgr but about user applications which use some DROPS RT-functions. Thanks, Arthur

2 1

Compiling DROPS with GCC 4
by Oskar Senft 23 Jun '06

23 Jun '06

Hi! Is it possible to compile DROPS with GCC 4 now? I still get the following error: make[2]: Entering directory `/home/osk/tmp/dropsupdate-060619-163030/drops-060619/l4/pkg/l4io' Makefile:8: *** Wrong gcc major version "" - use 3.x for l4io. Stop. make[2]: Leaving directory `/home/osk/tmp/dropsupdate-060619-163030/drops-060619/l4/pkg/l4io' Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 500 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

4 6

Build problems with make 3.81rc2
by Oskar Senft 21 Jun '06

21 Jun '06

Hi people! With "GNU Make 3.81rc2" and "GNU sed version 4.1.4" from Debian testing, I get an error with the following entries in l4/tool/gcc-wrap/Makefile: $(SYSTOOLS): %.$(SYSTEM): %.in .general.d @$(GEN_MESSAGE) $(VERBOSE)sed '\ s,@system@,$(SYSTEM),g;\ s,@ar@,$(AR),g;\ s,@nm@,$(NM),g;\ s,@ranlib@,$(RANLIB),g;\ s,@cc@,$(CC_$(DEFAULT_ARCH)),g;\ s,@cxx@,$(CXX_$(DEFAULT_ARCH)),g;\ s,@l4dir@,$(absfilename $(L4DIR)),g;\ s,@dropsdir@,$(DROPS_STDDIR),g;\ s,@compilerincdir@,$(GCCDIR_$(DEFAULT_ARCH))/include,g;\ s,@libgcc@,$(GCCLIB_$(DEFAULT_ARCH)),g;\ s,@libgcc_eh@,$(GCCLIB_EH_$(DEFAULT_ARCH)),g;\ s,@default_system@,$(DEFAULT_SYSTEM),g;\ s,@default_arch@,$(DEFAULT_ARCH),g;\ s,@default_cpu@,$(call PROCESS_SYSTEM, 's/[^-_]*_$[^-]*$.*/\1/p'),g;\ s,@default_l4api@,$(call PROCESS_SYSTEM, 's/.*-$.*$/\1/p'),g;\ ' $< > $@.new $(VERBOSE)chmod 755 $@.new $(VERBOSE)mv $@.new $@ For some reason (probably "make" or "sed" is broken?), the multi-line sed command is not recognized properly. I get the following error: ... Generating drops-ar.Linux sed '\ s,@system@,Linux,g;\ s,@ar@,ar,g;\ s,@nm@,nm,g;\ s,@ranlib@,ranlib,g;\ s,@cc@,,g;\ s,@cxx@,,g;\ s,@l4dir@,,g;\ s,@dropsdir@,/home/osk/tmp/dropsupdate-060619-163030/drops-060619/build,g;\ s,@compilerincdir@,/include,g;\ s,@libgcc@,,g;\ s,@libgcc_eh@,,g;\ s,@default_system@,x86_586,g;\ s,@default_arch@,x86,g;\ s,@default_cpu@,586,g;\ s,@default_l4api@,,g;\ ' drops-ar.in > drops-ar.Linux.new sed: -e expression #1, char 359: unterminated address regex make: *** [drops-ar.Linux] Error 1 When I try it "by hand", I get the same error. Nevertheless it works, when I put all the sed command into a single line. Probably you already have a better solution to that? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 500 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 3

Build problems with dice
by Tonnerre Lombard 21 Jun '06

21 Jun '06

Salut, Trying to build dice, I get the following errors: g++ -Wunused -Wunused-parameter -g -O2 -o dice -export-dynamic main.o Compiler.o CParser.o File.o Object.o version.o CCParser.o CCXXParser.o CDCEParser.o CCORBAParser.o CPreProcess.o IncludeStatement.o Exception.o -L../src/be/l4/v2 -lv2 -L../src/be/l4/v2/amd64 -lv2amd64 -L../src/be/l4/v2/ia32 -lv2ia32 -L../src/be/l4/x0 -lx0 -L../src/be/l4/v4 -lv4 -L../src/be/l4/v4/ia32 -lv4ia32 -L../src/be/l4 -ll4 -L../src/be/sock -lsock -L../src/be/cdr -lcdr -L../src/be -lbe -L../src/parser/dce -ldce -L../src/parser/corba -lcorba -L../src/parser/inc -linc -L../src/parser/gcc-c -lgcc_c -L../src/parser/gcc-cxx -lgcc_cxx -L../src/fe -lfe -lstdc++ -ldl CCParser.o: In function `CCParser::Parse(void*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, bool, bool)': /root/l4/tool/dice/src/CCParser.cpp:258: undefined reference to `gcc_c_flex_debug' /root/l4/tool/dice/src/CCParser.cpp:268: undefined reference to `gcc_cin' /root/l4/tool/dice/src/CCParser.cpp:269: undefined reference to `StartBufferGccC(_IO_FILE*)' /root/l4/tool/dice/src/CCParser.cpp:263: undefined reference to `gcc_c_flex_debug' /root/l4/tool/dice/src/CCParser.cpp:272: undefined reference to `RestoreBufferGccC(void*, bool)' /root/l4/tool/dice/src/CCParser.cpp:284: undefined reference to `GetCurrentBufferGccC()' CCParser.o: In function `CCParser::Import(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /root/l4/tool/dice/src/CCParser.cpp:105: undefined reference to `GetCurrentBufferGccC()' /root/l4/tool/dice/src/CCParser.cpp:155: undefined reference to `RestoreBufferGccC(void*, bool)' CCXXParser.o: In function `CCXXParser::Parse(void*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, bool, bool)': /root/l4/tool/dice/src/CCXXParser.cpp:239: undefined reference to `gcc_cxx_flex_debug' /root/l4/tool/dice/src/CCXXParser.cpp:253: undefined reference to `RestoreBufferGccCxx(void*, bool)' /root/l4/tool/dice/src/CCXXParser.cpp:244: undefined reference to `gcc_cxx_flex_debug' /root/l4/tool/dice/src/CCXXParser.cpp:249: undefined reference to `gcc_cxxin' /root/l4/tool/dice/src/CCXXParser.cpp:250: undefined reference to `StartBufferGccCxx(_IO_FILE*)' /root/l4/tool/dice/src/CCXXParser.cpp:265: undefined reference to `GetCurrentBufferGccCxx()' CCXXParser.o: In function `CCXXParser::Import(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /root/l4/tool/dice/src/CCXXParser.cpp:93: undefined reference to `GetCurrentBufferGccCxx()' /root/l4/tool/dice/src/CCXXParser.cpp:145: undefined reference to `RestoreBufferGccCxx(void*, bool)' CDCEParser.o: In function `CDCEParser::Parse(void*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, bool, bool)': /root/l4/tool/dice/src/CDCEParser.cpp:249: undefined reference to `dce_flex_debug' /root/l4/tool/dice/src/CDCEParser.cpp:259: undefined reference to `dcein' /root/l4/tool/dice/src/CDCEParser.cpp:260: undefined reference to `StartBufferDce(_IO_FILE*)' /root/l4/tool/dice/src/CDCEParser.cpp:254: undefined reference to `dce_flex_debug' /root/l4/tool/dice/src/CDCEParser.cpp:263: undefined reference to `RestoreBufferDce(void*, bool)' /root/l4/tool/dice/src/CDCEParser.cpp:275: undefined reference to `GetCurrentBufferDce()' CDCEParser.o: In function `CDCEParser::Import(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /root/l4/tool/dice/src/CDCEParser.cpp:95: undefined reference to `GetCurrentBufferDce()' /root/l4/tool/dice/src/CDCEParser.cpp:150: undefined reference to `RestoreBufferDce(void*, bool)' CCORBAParser.o: In function `CCORBAParser::Import(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /root/l4/tool/dice/src/CCORBAParser.cpp:93: undefined reference to `GetCurrentBufferCorba()' /root/l4/tool/dice/src/CCORBAParser.cpp:145: undefined reference to `RestoreBufferCorba(void*, bool)' CCORBAParser.o: In function `CCORBAParser::Parse(void*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, bool, bool)': /root/l4/tool/dice/src/CCORBAParser.cpp:222: undefined reference to `corba_flex_debug' /root/l4/tool/dice/src/CCORBAParser.cpp:232: undefined reference to `corbain' /root/l4/tool/dice/src/CCORBAParser.cpp:233: undefined reference to `StartBufferCorba(_IO_FILE*)' /root/l4/tool/dice/src/CCORBAParser.cpp:227: undefined reference to `corba_flex_debug' /root/l4/tool/dice/src/CCORBAParser.cpp:236: undefined reference to `RestoreBufferCorba(void*, bool)' /root/l4/tool/dice/src/CCORBAParser.cpp:248: undefined reference to `GetCurrentBufferCorba()' CPreProcess.o: In function `CPreProcess::PreProcess(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, bool)': /root/l4/tool/dice/src/CPreProcess.cpp:346: undefined reference to `incin' /root/l4/tool/dice/src/CPreProcess.cpp:347: undefined reference to `incout' /root/l4/tool/dice/src/CPreProcess.cpp:351: undefined reference to `inclex()' ../src/parser/dce/libdce.a(parser.o): In function `dceparse()': /root/l4/tool/dice/src/parser/dce/y.tab.c:2677: undefined reference to `dcelex(YYSTYPE*)' ../src/parser/dce/libdce.a(parser.o): In function `dceparse()': /root/l4/tool/dice/src/parser/dce/parser.yy:3584: undefined reference to `dcelex(YYSTYPE*)' ../src/parser/corba/libcorba.a(parser.o): In function `corbaparse()': /root/l4/tool/dice/src/parser/corba/y.tab.c:1868: undefined reference to `corbalex(YYSTYPE*)' ../src/parser/gcc-c/libgcc_c.a(parser.o): In function `gcc_cparse()': /root/l4/tool/dice/src/parser/gcc-c/y.tab.c:2637: undefined reference to `gcc_clex(YYSTYPE*)' ../src/parser/gcc-cxx/libgcc_cxx.a(parser.o): In function `gcc_cxxparse()': /root/l4/tool/dice/src/parser/gcc-cxx/y.tab.c:5457: undefined reference to `gcc_cxxlex(YYSTYPE*)' collect2: ld returned 1 exit status It seems that your #define magic doesn't work overly well... Any ideas on how to fix it? Or is it an error using the makefiles? BTW, the documentation is also inaccurate: it states that one should just type make config and make, but you have to add O=/where/ever to the mess. Tonnerre -- SyGroup GmbH Tonnerre Lombard Loesungen mit System Tel:+41 61 333 80 33 Roeschenzerstrasse 9 Fax:+41 61 383 14 67 4153 Reinach Web:www.sygroup.ch tonnerre.lombard(a)sygroup.ch

2 3

MIKES 2006 workshop update
by Ihor Kuz 21 Jun '06

21 Jun '06

Hi, Several months ago we sent you an invitation to the MIKES 2006 (microkernels for embedded systems) workshop being held in Sydney this August. Unfortunately there have been too few submissions to create a quality workshop program worthy of interest. The organisers have decided to postpone the workshop until January 2007, and will work hard on advertising the workshop more widely. We encourage you to resubmit your work to MIKES later this year for the workshop in January. Regards Ihor Kuz on behalf of the MIKES workshop organising committee: Gernot Heiser Stefan Petters Ihor Kuz http://www.ertos.nicta.com.au/events/06/0815-mikes.pml

1 0

2025

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