- l4-hackers - example.com Site

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