- l4-hackers - example.com Site

stop thread running in fiasco/L4
by hazwan 06 Mar '08

06 Mar '08

Hello Im curious to know, how can i stop a thread from running? Is there an API call to do this process? As far as i know, there is an API call for OK/L4 to stop a thread. How about fiasco? Thanks -- View this message in context: http://www.nabble.com/stop-thread-running-in-fiasco-L4-tp15864227p15864227.… Sent from the L4 mailing list archive at Nabble.com.

2 1

need some help in okl4
by Gabi Voiculescu 04 Mar '08

04 Mar '08

Hello l4-hackers community, Does anyone have experience with okl4's distribution? I have some questions on how to make gta01 platform simulate in Skyeye starting from okl4_release_1.5.2 with lcd support. I changed machines.py in platform/s3c2410/tools to contain: lcd: state=on, type=s3c2410x, mod=gtk I know Skyeye can simulate the LCD (verified it in arm's testsuite). Gabi --------------------------------- Never miss a thing. Make Yahoo your homepage.

1 0

does l4 linux now support smp?
by Yang Xu 04 Mar '08

04 Mar '08

Hello everyone, does anybody know that whether l4 linux now already support smp or not please? As far as I know, linux 2.6.x already supports smp. So I am wondering the the l4-linux 2.6 supports smp or not. if yes, it is the linux kernel distributes the threads across the cores or the ukernel does this? Any comment is welcome :-) best regards, Yang

2 5

mysterious double fault
by Alexander Arlt 04 Mar '08

04 Mar '08

hi all, i have a mysterious double fault error while booting fiasco in qemu. the problem is that the same configuration works on a native 586 fiasco and in fiasco-ux without any problems. only with qemu a double fault is detected. i tested it with qemu 0.9.0 and qemu 0.9.1. with version 0.9.0 the boot process hangs, without any error messages. with qemu 0.9.1 fiasco says that a double fault was detected. in my configuration i boot two instances of l4linux. while the intialization of the l4linux kernel, fiasco produces the following output: DOUBLE FAULT! EAX=c02407d0 ESI=c0240000 DS=0023 EBX=c0401000 EDI=00000000 ES=0023 ECX=3fe19000 EBP=c02406b4 GS=0043 EDX=00000000 ESP=c04017cc SS=0010 ESP0=c0240800 EFL=00200087 EIP=f002ef06 CS=0008 this happens always after the "l4lx | Got 0 out of 65536 I/O ports" message. but the really confusing thing is, that sometimes also qemu can boot without any double fault. any ideas whats going wrong here? thanks alex

2 1

Linux 2.6.24 L4FB and VGA_CONSOLE
by Marc CHALAND 27 Feb '08

27 Feb '08

Hi, I made a svn up into l4linux-2.6, made an oldconfig and encountered some problems with lxevent and... cron (???). Problem with lxevent, was into rmgr_init_ping_call: _dice_msg_buffer was NULL. So I decided to purge all build directories (fiasco, build dir, install dir and l4linux). I edited a new configuration for l4linux but I encountered a problem : I cannot disable VGA_CONSOLE if I don't use EMBEDDED. So I decided to set it. But, now, I've got some stability problems : I get the following message : --------------------------------------------------------------------------------------------------------------------------------- KERNEL: set_tls: non-existing thread 003401e1 KERNEL: set_ldt: non-existing task 0. Trap: 13: 0000 [#1] Modules linked in: Pid: 1070, comm: consolechars Not tainted (2.6.24-l4 #14) EIP: ff7c:[<00405055>] EFLAGS: 00010246 CPU: 0 EIP is at l4x_switch_to+0xd0/0xd3 EAX: 1003cc60 EBX: 00000018 ECX: 00000000 EDX: 00000000 ESI: 003401e1 EDI: 1003ca80 EBP: 1081013c ESP: 108139a0 DS: 0000 ES: 4280 FS: 0023 GS: 0043 SS: 0023 Process consolechars (pid: 1070, ti=10812000 task=1003ca80 task.ti=108d0000) Stack: 108139a8 00000000 1003ca80 10810000 00000400 0054da88 005f0fbc 10810000 00000400 1003ca80 10812000 108139e8 ffff950d 00000400 0000000b 0054dd5b 108139e8 ffff950d 005f67b0 005f67b0 ffff950d 0041923c 10810000 005f5f00 Call Trace: [<0054da88>] schedule+0x171/0x1bb [<0054dd5b>] schedule_timeout+0x7b/0x99 [<0041923c>] process_timeout+0x0/0x9 [<0045672f>] do_select+0x397/0x3ee [<00456d5f>] __pollwait+0x0/0xaf [<0040eeff>] default_wake_function+0x0/0x14 [<0049f877>] __make_request+0x472/0x4a8 [<0040e891>] update_curr+0x52/0xc8 [<0040eb9b>] dequeue_entity+0xb/0x2a [<0040fbbf>] dequeue_task_fair+0x1b/0x2f [<0040f644>] finish_task_switch+0x1f/0x50 [<0054dab4>] schedule+0x19d/0x1bb [<0054dcca>] io_schedule+0xb/0x12 [<00467424>] sync_buffer+0x3b/0x40 [<0054debd>] __wait_on_bit+0x53/0x5c [<004673e9>] sync_buffer+0x0/0x40 [<004673e9>] sync_buffer+0x0/0x40 [<0054df28>] out_of_line_wait_on_bit+0x62/0x6a [<00421d9c>] wake_bit_function+0x0/0x34 [<004820b3>] __ext3_get_inode_loc+0x29e/0x2f6 [<00448a95>] kmem_cache_alloc+0x66/0x9e [<0045a1da>] __d_lookup+0x97/0xd5 [<0045a1da>] __d_lookup+0x97/0xd5 [<00451dd2>] do_lookup+0x59/0x16b [<00453837>] __link_path_walk+0x930/0xa72 [<0045a6a3>] dput+0x2a/0xe5 [<00453837>] __link_path_walk+0x930/0xa72 [<0045d5ea>] mntput_no_expire+0x1c/0x5c [<0045697e>] core_sys_select+0x1f8/0x2ae [<00454514>] __user_walk_fd+0x43/0x4c [<00449151>] kmem_cache_free+0x40/0x93 [<00452d6f>] getname+0x68/0xa2 [<0044e26d>] cp_new_stat64+0xff/0x111 [<00456eb3>] sys_select+0xa5/0x173 [<0040401b>] l4x_user_dispatcher+0x8e2/0x184c [<0040c030>] _upage_start+0x30/0x890 [<00456e0e>] sys_select+0x0/0x173 [<0044fd40>] do_execve+0x172/0x17b [<0044fd40>] do_execve+0x172/0x17b [<005c4372>] kernel_init+0x0/0x254 [<004079a3>] l4_kernelinternal_execve+0xc2/0xc9 [<00400915>] in_kernel_int80_helper+0x9/0x17 [<005c4372>] kernel_init+0x0/0x254 [<004094a3>] kernel_execve+0x17/0x1a [<00400198>] run_init_process+0x20/0x24 [<00400242>] init_post+0xa6/0xd0 [<005c45bc>] kernel_init+0x24a/0x254 [<0040f644>] finish_task_switch+0x1f/0x50 [<005c4372>] kernel_init+0x0/0x254 [<005c4372>] kernel_init+0x0/0x254 [<004072cb>] kernel_thread_start+0x28/0x2d [<00406ed2>] sys_enosys+0x0/0x6 ======================= Code: 00 00 89 04 d5 04 e0 5a 00 89 0c d5 00 e0 5a 00 8b b7 00 02 00 00 8d 87 e0 01 00 00 bb 18 00 00 00 31 c9 89 ca 0f 00 d0 5b 5e 5f <c3> 90 90 57 56 83 ec 04 8b 74 24 10 8b 7c 24 14 f6 46 0d 20 74 EIP: [<00405055>] l4x_switch_to+0xd0/0xd3 SS:ESP 0023:108139a0 ---[ end trace 10d172b22dcd8354 ]--- Fixing recursive fault but reboot is needed! ------------------------------------------------------------------------------------------------------------------------ I thought I forgot to set an option into kernel. But this happens sometimes on egrep, which, etc.. Any idea on the problem ? Regards Marc

3 10

Problem with dice when fpage are used with derivation
by Marc CHALAND 27 Feb '08

27 Feb '08

Hi, I don't have time to do more checking on L4Linux. Today, I use dice r238 of public repository of TUDOS. All my tasks are pure L4env ones. I try to process an idl which is quite long. Here is a sample : library myapp { [uuid(2)] interface connection { int syn([out] unsigned long *page_in_base); int ack([in] fpage page_in, [in] unsigned long page_out_base, [out] fpage *page_out); int rst(void); }; }; I create one interface which derives from myapp::connection : library myapp_server { interface server : myapp::configuration, myapp::connection, myapp::key { }; }; Dice generates files. One of them is very strange. On server side, file corresponding to myapp_server contains following code : inline long myapp_server_reply_and_wait (CORBA_Object _dice_corba_obj, l4_msgtag_t *_dice_tag, myapp_server_msg_buffer_t *_dice_msg_buffer, CORBA_Server_Environment *_dice_corba_env) { long _dice_opcode = 0; l4_msgtag_t tagdummy __attribute__ ((unused)) = l4_msgtag(0,0,0,0); l4_msgdope_t _dice_result = { msgdope: 0 }; if ((_dice_msg_buffer->_word._dice_send_dope.md.dwords <= 2) && (_dice_msg_buffer->_word._dice_send_dope.md.strings == 0)) [ZAP] /* clear exception if set*/ if (DICE_EXPECT_FALSE(DICE_HAS_EXCEPTION(_dice_corba_env))) CORBA_server_exception_set(_dice_corba_env, CORBA_NO_EXCEPTION, CORBA_DICE_EXCEPTION_NONE, 0); /* test for IPC errors */ if (DICE_EXPECT_FALSE(L4_IPC_IS_ERROR(_dice_result))) { _dice_opcode = 0; _dice_msg_buffer->_word._word[0] = 0; if (DICE_IS_NO_EXCEPTION(_dice_corba_env)) CORBA_server_exception_set(_dice_corba_env, CORBA_SYSTEM_EXCEPTION, CORBA_DICE_INTERNAL_IPC_ERROR, 0); return _dice_opcode; } if (l4_ipc_fpage_received(_dice_result)) _dice_opcode = _dice_msg_buffer->_word._word[2]; else _dice_opcode = _dice_msg_buffer->_word._word[0]; return _dice_opcode; } By adding some logging, I realized that when fpage is received, opcode is not into _word[2] but _word[4]. Regards Marc

2 1

how can a l4 task load l4linux?
by Alexander Arlt 27 Feb '08

27 Feb '08

hi all, i try to write a l4 task which can dynamically load / boot a l4linux. at the moment i using fiasco ux which parses a loader configuration file to boot l4linux. the question is, how can i do this at runtime, without such a configuration file. it seems so, that this can be done by using some internal l4 loader stuff. i looked at the l4 loader reference manual, but its a bit hard to reason how this can be realized. maybe a small example would be really nice :) can anyone help me? thanks, alex

2 1

February 75% OFF
by l4-hackers＠os.inf.tu-dresden.de 13 Feb '08

13 Feb '08

1 0

Runux script to run Fiasco-UX
by Lucyantie Mazalan 30 Jan '08

30 Jan '08

Hi, | | | It should be "./fiasco -l hello". | | | | When I try (to run existing module), I get this: | | | | ---------------------------------------------------------------------- | | -- | | ---- | | root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# ./fiasco -l | | hiworld | | | | | | Fiasco-UX on Linux 2.6.20-15-generic (i686) Mapped 64 MB Memory + 0 KB | | Framebuffer + 0 MB Input Area on FD 3 | | | | Loading Module 0x00100000-0x00109364 [sigma0] Loading Module | | 0x00110000-0x002af000 [roottask] Failed to open file: hiworld | | root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# | That's how it should look like. The error tells you that the hiworld binary is missing or has inappropriate rights. (Btw.: You're still building as | root...) Thanks I have copied my binaries and it runs well. | You might want to have a look at the scripts in l4/tool/runux - there is also a config file template which you can adapt for your system. Then you don't | always need to copy around your binaries. I am now trying to find the mentioned script but could not find it in my l4/tool/runux. Here is what I have: ----------------------------------------------------------------- lucy@lucy-ubuntu:/home/fiasco/l4/tool$ ls bin config gendep Makefile lucy@lucy-ubuntu:/home/fiasco/l4/tool$ slocate runux /home/fiasco/build/doc/bid-tut/hi-runux.tex /home/fiasco/l4/mk/.svn/prop-base/runux.mk.svn-base /home/fiasco/l4/mk/.svn/text-base/runux.mk.svn-base /home/fiasco/l4/mk/runux.mk /home/fiasco/l4/doc/bid-tut/.svn/prop-base/hi-runux.tex.svn-base /home/fiasco/l4/doc/bid-tut/.svn/text-base/hi-runux.tex.svn-base /home/fiasco/l4/doc/bid-tut/hi-runux.tex ----------------------------------------------------------------- Is there anything I should do beforehand? According to http://os.inf.tu-dresden.de/l4env/doc/html/bid-tut/tut.pdf, I have to edit the hello file in l4/tool/runux to start Fiasco-UX which will also start my server & client binaries. I have found the same script but it is named as 'hi-runux.tex' and it is in different path - /home/fiasco/build/doc/bid-tut/-. Any help? Anyone? Thanks in advance, Lucille. ------------------------------------------------------------------ - - - DISCLAIMER: This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any dealing, review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or MIMOS Berhad immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of MIMOS Berhad and/or its subsidiaries shall be understood as neither given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS Berhad nor its subsidiaries accepts responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mails is excluded to the fullest extent permitted by law.

2 1

Re: error in writing code for IPC servers & problem with Fiasco-UX
by Björn Döbel 29 Jan '08

29 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lucyantie Mazalan wrote: | Hi again, thanks for replying. | | | Did you build your package's include directory before building the | | client dir? | | Yes definitely, I built my include dir first before building the client | dir. anything else should be wrong? I don't get your error here. The only thing that's wrong in your tgz is that you link the client against libaes256.a, but your lib is called libaes.a | | It should be "./fiasco -l hello". | | When I try (to run existing module), I get this: | | ------------------------------------------------------------------------ | ---- | root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# ./fiasco -l | hiworld | | | Fiasco-UX on Linux 2.6.20-15-generic (i686) | Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 | | Loading Module 0x00100000-0x00109364 [sigma0] | Loading Module 0x00110000-0x002af000 [roottask] | Failed to open file: hiworld | root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# That's how it should look like. The error tells you that the hiworld binary is missing or has inappropriate rights. (Btw.: You're still building as root...) You might want to have a look at the scripts in l4/tool/runux - there is also a config file template which you can adapt for your system. Then you don't always need to copy around your binaries. Bjoern - -- Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHntLhP5ijxgQLUNkRAh8QAKCW6T76ZJzwb5P71WsDZ0DQqw4MtQCffLHv UIamVw1+qjr9ak7UUAAGCzk= =KlYv -----END PGP SIGNATURE-----

2 1