l4-hackers September 2007

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

19 participants
45 discussions

problem compiling l4linux - arm
by Dennis Gessner 06 Nov '07

06 Nov '07

Hi, I have some difficulties, compiling l4linux for arm. (I use the toolchain from http://www.ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.bz2.) Using the version from SVN (# svn co -N http://svn.tudos.org/repos/tudos/trunk tudos), I don't have any problems compiling fiasco or the l4env, but if I try to compile l4linux (... "repomgr co fiasco dice l4linux-2.6-env" ... and after disabling the VGA-Console) - I get the following error-message: --- l4linux-2.6 # make L4ARCH=arm … [View More]

4 5

about the L4Linux scheduler
by Lin 17 Oct '07

17 Oct '07

Hello. I have some questions about the scheduler system on DROPS L4Linux. I would like your help or some hints. The version of my source is ... DROPS SVN revision : 205 L4Linux SVN revision : 61 Fiasco version : 1.2 L4Linux version : 2.6.22 In L4Linux system (on L4Env), there are two schedulers (in Fiasco and in Linux server), you know. Some papers say any Linux user process consists of L4 task and the L4 shceduler schedules all L4 thread. It is ok, but I can't … [View More]understand the work of the Linux scheduler. In fact, a new thread is created in L4 when a process (has one thread) is created in Linux, and the active thread is changed when the context switch occurs in Linux server (made sure by using Fiasco JDB). I want to make this relation clear. In other words, what does the Linux scheduler do at these time. 1. Task creating ~~~~~~~~~~~~~~~~ When "fork()" (or such functions) is called, the function: l4x_setup_next_exec (in "arch/l4/kernel/arch-i386/dispatch.c") may be called. This function seems push the argument function "ret_from_fork" to the stack of the new "task_struct" instance to execute it first when the task is scheduled. Then, when "fork()" ends (when "do_fork()" returns), the new "task_struct" instance is created in Linux system. At this time, is the L4 thread (task ?) corresponds to that "task_struct" is not created yet ? (I assume it is created after the "task_struct" is scheduled.) 2. Linux server's scheduling ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In L4Linux task, there are 7 threads and IRQ threads: (1)l4lx.rm (2)l4lx.sem (3)l4lx.main (4)l4lx.tamer (5)l4lx.cpu0 (6)l4lx.timer.i0 (7)l4lx.idler ... "l4lx.main" creates "l4lx.cpu0" (Linux server) and waits this end. "l4lx.cpu0" does many initialization in the function "start_kernel()", and then it reaches at the function: l4x_idle (in "arch/l4/kernel/dispatch.c"). In this function, the Linux server creates the thread "l4lx.idler" and then enters the scheduling and IPC waiting loop. What does this function do ?? (My expectation about it is written in 4.) And more, What is the thread "l4lx.idler" used for ?? 3. Scheduled new Linux task ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The function "switch_to()" (depends on L4 arch) in Linux kernel only saves and restores the registers ESI, ..., ESP, and EIP. So, when all new created "task_struct"s are scheduled by the Linux server, they runs from "ret_from_fork" as the Linux server thread. (Is it right ?) ^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ "ret_from_fork" reaches at the function: l4x_user_dispatcher (in "arch/l4/kernel/dispatch.c"). It calls "l4x_spawn_cpu_thread()" before its loop. I assume it creates the new L4 thread corresponds to the now scheduled "task_struct" in Linux server. And, the loop in "l4x_user_dispatcher" seems to reply or wait page fault, exception and system call IPCs from any L4 thread runs as a Linux user task. What does this loop do in fact ?? When the context switch occurs in Linux server for some reasons, the active L4 thread is also switched almost at the same time. (I see it by using "ps" on Linux and the thread list of JDB on L4.) I want to know the mechanism of this synchronization. 4. Summary ~~~~~~~~~~ My main quiestions is ... (1) What is "l4lx.idler" created for ? (in 2) (2) What does the function "l4x_idle" do ? (in 2) (3) Do all Linux user tasks ("task_struct" instance) only execute "l4x_user_dispatcher" (from "ret_from_fork") as the Linux server ? (in 1 and 3) (4) What does the function "l4x_user_dispatcher" do ? How to switch contexts in Linux and in L4 almost at the same time ? (in 3) My expectation about Linux scheduling system is the following: - When there is no need to reschedule Linux user processes, Linux server is in IPC sleep and waiting the wakeup IPC in "l4x_idle". - If Linux server gets IPC for some reasons, it wakes up and check the IPC sender. Then, if the sender is a thread corresponds to certain Linux task, Linux server wakes up this Linux task and reschedules by calling "schedule()". - The waked up task will be active as Linux server. This context may execute only "l4x_user_dispatcher" which replies and wait IPCs and handles page faults and exceptions based on information of the received IPC. - When the L4 thread of the Linux task exits, that Linux task in Linux (task_struct instance) also is freed. If there is no schedulable task in Linux at that time, the original context (executes "l4x_idle") is re-scheduled. If you find my incorrect understanding, please tell me. Sorry for my poor English and lengthy question. I'm glad if you give me some hints or corrections. Regards, Lin (a college student in Japan) [View Less]

2 5

Re: the problems of l4linux
by Adam Lackorzynski 08 Oct '07

08 Oct '07

On Wed Sep 19, 2007 at 09:01:38 +0000, chenggh wrote: > > Looks the same as the other mail. Enter helps? Actually, what do you > > expect to see? :) > Thanks. > I also read another mail with the same situation. I use Slackware 12.0 not > Ubuntu because in Ubuntu there is a glibc bug which has been existed at least > for more than half year - "undefined reference to __stack_chk_fail". This bug > has been reported many times and has committed to the Ubuntu Bug List.… [View More] But > bug is as before. That's no bug, it's a stack protection feature they use. I didn't really care because I do not use Ubuntu myself but I think we have to work around this. > The first question: > the l4 boot log is like this: > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > l4lx | acquire_irq: Error attaching to IRQ 2 > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > l4lx | acquire_irq: Error attaching to IRQ 1 > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some errors > like "acquire_irq: Error attaching to IRQ x". But later attaching IRQ is ok. > What is the matter? IRQ1 and IRQ12 are related with keyboard and monse, IRQ2 > is related with cascade, IRQ9 is about acpi. I have removed these drivers > from linux. why is it also like this? Think about who is supposed to have these IRQs. Keyboard and Mouse are already taken by the windowing/console system, so Linux can obviously not get them. So it is really ok that attaching those IRQs fail, it's supposed to be like this. > The second problem is: > The Linux booting stops at /ect/random-seed to initialize /dev/urandom and > there is no login interface. I have checked the normal linux booting and > after the using /ect/random-seed to initialize /dev/urandom the linux will > finish booting kernel, enter the linux user space "INIT: Entering init X". > So I think it is still the problem of l4linux kernel not the special linux > distribution. Is it right? Same question: Is your Slackware starting a login on tty1? What happens with normal Linux? You may want to disable your X for the test and check your /etc/inittab. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ [View Less]

2 1

Re: the problems of l4linux
by chenggh 01 Oct '07

01 Oct '07

> When using ttyLv0 as a console you also need to start a getty there, > similar to an ttyS0 entry. Otherwise no login prompt will appear there. > My inittab looks a bit different but I don't see some obvious reasons > why yours isn't popping up a login-prompt on tty1, at least on the first > glance. > Just booting to single user mode works? Not yet. This time without dope in ttyLv0 the booting log is: proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) Starting udevd:… [View More]

2 1

The ultimate HOW-TO
by ComputerScienceStudent 01 Oct '07

01 Oct '07

<?xml version="1.0" encoding="UTF-8"?> @page { size: 20.999cm 29.699cm; margin-top: 2cm; margin-bottom: 2cm; margin-left: 2cm; margin-right: 2cm } table { border-collapse:collapse; border-spacing:0; empty-cells:show } td, th { vertical-align:top; } h1, h2, h3, h4, h5, h6 { clear:both } ol, ul { padding:0; } * { margin:0; } *.Caption { font-family:'Thorndale AMT'; font-size:12pt; margin-top:0.212cm; margin-bottom:0.212cm; font-style:italic; } *.Heading { font-family:'Albany AMT'; … [View More]

3 46

error report
by chenggh 26 Sep '07

26 Sep '07

Hi: When compiling dde_linux26 there are some errors like this: In file included from /home/L4/tudos/l4/build/include/x86/l4/linux-26-headers/asm/thread_info.h:16, from /home/L4/tudos/l4/build/include/l4/linux-26-headers/linux/thread_info.h:21, from /home/L4/tudos/l4/build/include/l4/dde_linux26/linux/spinlock.h:12, from /home/L4/tudos/l4/build/include/l4/linux-26-headers/linux/mmzone.h:8, from /home/L4/tudos/l4/build/… [View More]

4 3

Re: the problems of l4linux
by Adam Lackorzynski 22 Sep '07

22 Sep '07

On Thu Sep 20, 2007 at 17:59:41 +0000, chenggh wrote: > > > __stack_chk_fail". This bug has been reported many times and has > > > committed to the Ubuntu Bug List. But bug is as before. > > > > That's no bug, it's a stack protection feature they use. I didn't really > > care because I do not use Ubuntu myself but I think we have to work > > around this. > Yes, basically it is not a bug but I should have used fno-stack-protector to > fix the … [View More]problem. But later I found although I use fno-stack-protector the > problem is still. I google the key word __stack_chk_fail and there are lots > of people with same problem as me. So I think it is a bug of glic problem. If google finds many pages with something this doesn't mean all those pages show the truth just because they are so many. Using -fno-stack-protector is fine as long as _all_ code is compiled with this option. When linking against code that is built _with_ the stack-protection feature enabled that compile time option won't help you. This happens e.g. when linking against libraries supplied by gcc. On Ubuntu those libraries are built with the stack protection feature enabled. To fix this you either rebuild gcc-libs with stack protection or provide those symbols. The latter seems far more convenient. > > > The first question: > > > the l4 boot log is like this: > > > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > > > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > > > l4lx | acquire_irq: Error attaching to IRQ 2 > > > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > > l4lx | acquire_irq: Error attaching to IRQ 1 > > > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some > > > errors like "acquire_irq: Error attaching to IRQ x". But later attaching > > > IRQ is ok. What is the matter? IRQ1 and IRQ12 are related with keyboard > > > and monse, IRQ2 is related with cascade, IRQ9 is about acpi. I have > > > removed these drivers from linux. why is it also like this? > > Think about who is supposed to have these IRQs. Keyboard and Mouse are > > already taken by the windowing/console system, so Linux can obviously > > not get them. So it is really ok that attaching those IRQs fail, it's > > supposed to be like this. > Thanks. I think I should read the l4linux code and later if I encouter the > similar question I could understand. :) > > > The second problem is: > > > The Linux booting stops at /ect/random-seed to initialize /dev/urandom > > > and there is no login interface. I have checked the normal linux booting > > > and after the using /ect/random-seed to initialize /dev/urandom the linux > > > will finish booting kernel, enter the linux user space "INIT: Entering > > > init X". So I think it is still the problem of l4linux kernel not the > > > special linux distribution. Is it right? > > > > Same question: Is your Slackware starting a login on tty1? What happens > > with normal Linux? You may want to disable your X for the test and check > > your /etc/inittab. > Not ,the problem is also. I disable X and try to boot l4linux on ttyLv0. The > Linux also stops here "/ect/random-seed to initialize /dev/urandom". There is > an attachment which is my inittab. When using ttyLv0 as a console you also need to start a getty there, similar to an ttyS0 entry. Otherwise no login prompt will appear there. My inittab looks a bit different but I don't see some obvious reasons why yours isn't popping up a login-prompt on tty1, at least on the first glance. Just booting to single user mode works? > # > # inittab This file describes how the INIT process should set up > # the system in a certain run-level. > # > # Version: @(#)inittab 2.04 17/05/93 MvS > # 2.10 02/10/95 PV > # 3.00 02/06/1999 PV > # 4.00 04/10/2002 PV > # > # Author: Miquel van Smoorenburg, <miquels(a)drinkel.nl.mugnet.org> > # Modified by: Patrick J. Volkerding, <volkerdi(a)slackware.com> > # > > # These are the default runlevels in Slackware: > # 0 = halt > # 1 = single user mode > # 2 = unused (but configured the same as runlevel 3) > # 3 = multiuser mode (default Slackware runlevel) > # 4 = X11 with KDM/GDM/XDM (session managers) > # 5 = unused (but configured the same as runlevel 3) > # 6 = reboot > > # Default runlevel. (Do not set to 0 or 6) > id:3:initdefault: > > # System initialization (runs when system boots). > si:S:sysinit:/etc/rc.d/rc.S > > # Script to run when going single user (runlevel 1). > su:1S:wait:/etc/rc.d/rc.K > > # Script to run when going multi user. > rc:2345:wait:/etc/rc.d/rc.M > > # What to do at the "Three Finger Salute". > ca::ctrlaltdel:/sbin/shutdown -t5 -r now > > # Runlevel 0 halts the system. > l0:0:wait:/etc/rc.d/rc.0 > > # Runlevel 6 reboots the system. > l6:6:wait:/etc/rc.d/rc.6 > > # What to do when power fails. > pf::powerfail:/sbin/genpowerfail start > > # If power is back, cancel the running shutdown. > pg::powerokwait:/sbin/genpowerfail stop > > # These are the standard console login getties in multiuser mode: > c1:1235:respawn:/sbin/agetty 38400 tty1 linux > c2:1235:respawn:/sbin/agetty 38400 tty2 linux > c3:1235:respawn:/sbin/agetty 38400 tty3 linux > c4:1235:respawn:/sbin/agetty 38400 tty4 linux > c5:1235:respawn:/sbin/agetty 38400 tty5 linux > c6:12345:respawn:/sbin/agetty 38400 tty6 linux > > # Local serial lines: > #s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100 > #s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100 > > # Dialup lines: > #d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100 > #d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100 > > # Runlevel 4 used to be for an X window only system, until we discovered > # that it throws init into a loop that keeps your load avg at least 1 all > # the time. Thus, there is now one getty opened on tty6. Hopefully no one > # will notice. ;^) > # It might not be bad to have one text console anyway, in case something > # happens to X. > x1:4:respawn:/etc/rc.d/rc.4 > > # End of /etc/inittab > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ [View Less]

1 0

O.S. question
by huang 22 Sep '07

22 Sep '07

dear Adam: Could you tell me the debain version that you are using now! And are there any other things about compilation environment I should pay attentation to? I want to use the same compilation environment as yours! :) thanks a lot! Best wishes! huang

2 1

Re: the problems of l4linux
by chenggh 20 Sep '07

20 Sep '07

> > __stack_chk_fail". This bug has been reported many times and has > > committed to the Ubuntu Bug List. But bug is as before. > > That's no bug, it's a stack protection feature they use. I didn't really > care because I do not use Ubuntu myself but I think we have to work > around this. Yes, basically it is not a bug but I should have used fno-stack-protector to fix the problem. But later I found although I use fno-stack-protector the problem is still. I google … [View More]the key word __stack_chk_fail and there are lots of people with same problem as me. So I think it is a bug of glic problem. > > The first question: > > the l4 boot log is like this: > > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > > l4lx | acquire_irq: Error attaching to IRQ 2 > > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > l4lx | acquire_irq: Error attaching to IRQ 1 > > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some > > errors like "acquire_irq: Error attaching to IRQ x". But later attaching > > IRQ is ok. What is the matter? IRQ1 and IRQ12 are related with keyboard > > and monse, IRQ2 is related with cascade, IRQ9 is about acpi. I have > > removed these drivers from linux. why is it also like this? > Think about who is supposed to have these IRQs. Keyboard and Mouse are > already taken by the windowing/console system, so Linux can obviously > not get them. So it is really ok that attaching those IRQs fail, it's > supposed to be like this. Thanks. I think I should read the l4linux code and later if I encouter the similar question I could understand. :) > > The second problem is: > > The Linux booting stops at /ect/random-seed to initialize /dev/urandom > > and there is no login interface. I have checked the normal linux booting > > and after the using /ect/random-seed to initialize /dev/urandom the linux > > will finish booting kernel, enter the linux user space "INIT: Entering > > init X". So I think it is still the problem of l4linux kernel not the > > special linux distribution. Is it right? > > Same question: Is your Slackware starting a login on tty1? What happens > with normal Linux? You may want to disable your X for the test and check > your /etc/inittab. Not ,the problem is also. I disable X and try to boot l4linux on ttyLv0. The Linux also stops here "/ect/random-seed to initialize /dev/urandom". There is an attachment which is my inittab. Thanks. Cheng Guanghui [View Less]

1 0

Re: l4-hackers Digest, Vol 53, Issue 22
by 丁莹 20 Sep '07

20 Sep '07

2007/9/19, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de>: > > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person … [View More]managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: The ultimate HOW-TO (Adam Lackorzynski) > 2. Re: l4linux starting problem (Adam Lackorzynski) > 3. Re: the problems of l4linux (Adam Lackorzynski) > 4. Re: the problems of l4linux (chenggh) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 19 Sep 2007 00:11:06 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: The ultimate HOW-TO > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070918221106.GD19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Tue Sep 18, 2007 at 08:05:18 -0700, ComputerScienceStudent wrote: > > > > Maybe this is the longest email you'll receive, but I would give you all > the > > possible informations. > > There are three sections: > > - THE MAKE ERRORS > > - L4LINUX CONFIGURATION > > - HARDWARE INFO. > > Ok, looks like you took your Linux configuration from your host (or the > configuration system did so). Please use the default configuration > coming with L4Linux by starting with 'make x86-native_defconfig'. And > then those errors won't occur. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 2 > Date: Wed, 19 Sep 2007 00:17:25 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: l4linux starting problem > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070918221725.GE19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Tue Sep 18, 2007 at 17:34:07 +0800, ???? wrote: > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. > > l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ14) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. > > l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ15) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. > > l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ11) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12. > > l4lx | acquire_irq: Error attaching to IRQ 12 > > l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ12) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > l4lx | acquire_irq: Error attaching to IRQ 1 > > l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ1) > > > > And the dope when starting after following message then dead. > > > > Checking non-root filesystems: > > fsck 1.39 (29-May-2006) > > /dev/hda10:clean, 135991/667808 files,510175/1333387 blocks > > Mounting non-root local filesystems: > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on hda10, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > /dev/hda10 on /home type ext3(rw) > > Using /etc/random-seed to initialize /dev/urandom. > > > > How can I solve this problem?Anybody who knows please help me,Thanks! > > Well, userland starts, can't be too bad. Is that Ubuntu? Does a login > prompt appear when you press Enter a bit? > I wonder how the bootup looks like on native Linux (with X disabled). > > No,I use the slackware 12.0,the l4linux system dead when output above > message,so when press enter there is no response,the native Linux when > bootup after this will indicate message: INIT:enter runlevel 3. Best Regards! Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 3 > Date: Wed, 19 Sep 2007 00:19:29 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: the problems of l4linux > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070918221929.GF19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Tue Sep 18, 2007 at 22:02:16 +0000, chenggh wrote: > > Hi: > > I boot l4dope with l4linux. The dope seems ok but l4linux doesn't > start > > completely. I am not sure whether it is l4 problem or linux problem. > Please > > help me. > > > > The l4 boot log > > 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.22-l4 (root@darkstar) (gcc version 4.1.2) #1 > Tue > > Se > > l4lx : p 18 16:36:23 CST 2007 > > l4lx | Binary name: vmlinuz > > l4lx | Kernel command line (5 args): earlyprintk=yes video=l4fb > init=1 > > mem=6 > > l4lx : 4M root=/dev/hda2 > > l4lx | Image: 00400000 - 007a3000 [3724 KiB]. > > l4lx | Areas: Text: 00400000 - 006ad000 > [2740k | Initdata: > > 006cc000 - 00700000 [208kB] > > l4lx | BSS: 00702000 - 007a0f00 [635kB] > > l4lx | l4lx_thread_create: Created thread 10.03 (tamer0) > > l4lx | Tamer0 is 10.03 > > l4lx | Using tamed mode. > > l4lx | Connecting to l4io server. > > l4lx | l4env_linux_startup thread 4. > > l4lx | l4lx_thread_create: Created thread 10.04 (cpu0) > > l4lx | main thread will be 10.04 > > l4lx | l4env_register_pointer_section: addr = 00400000 size = 3149824 > > l4lx | sec-w-init: virt: 0x00400000 to 0x00700fff [3076 KiB] > > l4lx | Noncontiguous region for sec-w-init > > l4lx | sec-w-init: Number of physical regions: 3, 3149824 Bytes > > l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x01218000, > Size: 1630208 > > l4lx | sec-w-init: 2: Phys: 0x01419000 to 0x01500000, Size: > 946176 > > l4lx | sec-w-ini startup message. > > l4lx | Main thread running, waiting... > > 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: 0x0043a000 to 0x0063a000, > 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: 0x08c00000 to 0x0cc00000, Size: > 67108864 > > l4lx | Filling lower ptabs... > > l4lx | Done (1594 entries). > > l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) > > l4lx | Jumpinl4lx | idler0d_create: Created threadl4lx | > Startil4dope > > | SharedMem(allo0 > > l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) > > l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) > > l4lx | l4lx_iRQ 17. > > l4lx |startup_hw: Starting IRQ16) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. > > l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. > > l4lx tup_hw: Starting IRQ thread for IRQ 13. > > l4lx | l4lx_ting IRQ thread for IRQ 12. > > l4lx | acquire_irq: Error attaching to IRQ 12 > > l4lx | l4lx_thread_create: Created thread 10.0f (IRQ12) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. > > l4lx | l4lx_thread_create: Created thread 10.10 (IRQ11) > > l4lx | l4lx_irq_dev_startp_hw: Starting IRQ thread | > > l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 9. > > l4lx | l4lx_thread_create: Created thread 10.12 (IRQ9) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 8. > > l4lx | l4lx_thread_create: Created thread 10.13 (IRQ8) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 7. > > l4lx | l4lx_thread_create: Created thread 10.14 (IRQ7) > > l4lx | l4lx_irq_dev_startup_hw: Starting thread for IRQ 6. > > l4lx | l4lx_thread_create: Created thread 10.15 (IRQ6) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 5. > > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > > l4lx | acquire_irq: Error attaching to IRQ 2 > > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > l4lx | acquire_irq: Error attaching to IRQ 1 > > > > I don't know what these information stands for. Are all the > necessary > > interrupt threads ok? Or some of them is not ok. > > Seems ok. Some IRQ probing, 1, 2 and 12 are not allowed which is > perfectly ok. > > > the linux boot log > > ?????? > > EXTS FS on hda3, internal journal > > EXT-fs: mounted filesystem with orderred data mode > > /dev/hda3 on /home type ext3 (rw) > > using /ect/random-seed to initialize /dev/urandom > > > > The linux could stop here even I wait lot of time. It doesn't go > on. > > Looks the same as the other mail. Enter helps? Actually, what do you > expect to see? :) > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 4 > Date: Wed, 19 Sep 2007 09:01:38 +0000 > From: chenggh <chenggh04(a)st.lzu.edu.cn> > Subject: Re: the problems of l4linux > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <390158225.18632(a)st.lzu.edu.cn> > Content-Type: text/plain; charset="iso-8859-1" > > > Looks the same as the other mail. Enter helps? Actually, what do you > > expect to see? :) > Thanks. > I also read another mail with the same situation. I use Slackware > 12.0 not > Ubuntu because in Ubuntu there is a glibc bug which has been existed at > least > for more than half year - "undefined reference to __stack_chk_fail". This > bug > has been reported many times and has committed to the Ubuntu Bug > List. But > bug is as before. > The first question: > the l4 boot log is like this: > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > l4lx | acquire_irq: Error attaching to IRQ 2 > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > l4lx | acquire_irq: Error attaching to IRQ 1 > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are > some errors > like "acquire_irq: Error attaching to IRQ x". But later attaching IRQ is > ok. > What is the matter? IRQ1 and IRQ12 are related with keyboard and monse, > IRQ2 > is related with cascade, IRQ9 is about acpi. I have removed these drivers > from linux. why is it also like this? > > > The second problem is: > The Linux booting stops at /ect/random-seed to initialize > /dev/urandom and > there is no login interface. I have checked the normal linux booting and > after the using /ect/random-seed to initialize /dev/urandom the linux will > finish booting kernel, enter the linux user space "INIT: Entering init X". > So I think it is still the problem of l4linux kernel not the > special linux > distribution. Is it right? > Thank you very much. > Cheng > Guanghui > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 53, Issue 22 > ****************************************** > [View Less]

2 1

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 September 2007