Playing with ORe

Hi everybody, I did some experiments with ORe. I played with arping and I modified it to reply to ICMP from windows. I also added one option to ORe to prevent promiscuous mode when not necessary. cf attachment Best Regards ore.070622.patch Description: Binary data

Trouble with semaphore library

Hello, I encounter strange problems with semaphore library from l4env. I use a vanillia revision 230 on an intel PIII architecture. After some debugging and tracing, I get the following scenarion : 1. thread 03 of my process calls a semaphore down timed which then calls BLOCKTIMED IPC to

Re: Trouble with semaphore library

from Bjoern Doebel : Are you just having a problem understanding the observed values or is there a real problem that you are running into? If the latter, could you provide a small example program so that we can reproduce it here? That's a real problem. I use several producer (08 and others)

Re: Trouble with semaphore library

Alexander Boettcher [EMAIL PROTECTED]: Marc CHALAND wrote: 2. thread 08 calls semaphore_up inline assembler code. Before IPC call, the semaphore structure is as follow : counter = 0 pending = 0 queue = 03 2.1 Now, Thread 02 (the semaphore thread) have to run, because

Re: Trouble with semaphore library

Alexander Boettcher [EMAIL PROTECTED]: There is one tricky situation if the wakeup message for a semaphore is received before the block message. This might happen if the thread waiting on that semaphore is preemted by the thread releasing the semaphore before it can send the message to the

Re: Mad Mouse

2007/11/5, Christian Helmuth [EMAIL PROTECTED]: Hi Marc, Hi Did you start L4Linux too? I don't start L4Linux. I think a complete Fiasco bootlog and L4Linux configuration file may help to expose the culprit. I joined bootlog as attachment. BTW: Does our demo CD from

Hide linux console into DOpE

Hi, I added into l4linux a feature that seems to me interesting. With the following patch, it is possible to hide linux console window with the following linux command: echo N /sys/module/l4fb/parameters/console_visible The console can be shown with the following command : echo Y

Re: Mad Mouse

Marc CHALAND [EMAIL PROTECTED]: - one PS/2 which looses sync without usbhid task, but works perfectly when usbhid task is started Sorry, this info is not right. After some testing, sync is also lost but very less often than without usbhid task. Regards Marc

Re: Mad Mouse

2007/11/7, Christian Helmuth [EMAIL PROTECTED]: On Wed, Nov 07, 2007 at 03:09:24PM +0100, Marc CHALAND wrote: I've found a mouse which perfectly works ;). So, you use a working PS/2 mouse now? Yes, I've got 3 mice : - one PS/2 which works - one PS/2 which looses sync without usbhid task

Re: Mad Mouse

Hi Christian Helmuth [EMAIL PROTECTED]: Hm, sounds strange... maybe your BIOS's USB legacy support interferes with the PS/2 mouse - just a guess. Even with USB legacy disabled, this happens. But now, I am not blocked. I think usbhid should be used as most of recent hardware use USB keyboard

Re: l4x_hybrid_return for ovlscreen driver

2007/11/7, Adam Lackorzynski [EMAIL PROTECTED]: I've just tried to reproduce something like this but I had no 'luck'. I also do not understand how the code path can be taken with the given values. I suppose your sources are up to date? Is this reliably reproducible? Yes, I have latest svn

Re: l4x_hybrid_return for ovlscreen driver

Hi The problem is solved : I upgraded gcc 4.2 and binutils 2.18. I also had to completely purge build directory of fiasco. ovlscreen_drv works as no assembler ipc shortcut. Thank you Adam for your help. Regards Marc ___ l4-hackers mailing list

Little fix about ORe

Hi, I've found that when an ORe client finishes, ORe doesn't stop associated worker thread. Context is correctly freed but not thread. This may lead a lack of thread when several clients finishes and restart several times. Here is a little patch to fix this. Regards Marc ore.r238.071206.patch

Re : Little fix about ORe

Hello, Sorry for my last patch. I did some more testing after sending it (I know, it's bad) and I've found some problems in some cases : - error when the device is not found - normal close (thread is killed twice) So I propose the following patch which is applicable to r250. I tested it this

sigma0 and tbuf

Hi, I tried to use fiasco without jdb. It works fine, but, at boot time, sigma0 issues an int 3. After some analysis, int 3 is generated by init_memory in init_mem_v2.cc. It calls fiasco_get_status_phys(). If I comment this, everything is then fine. Why this call is for ? Regards Marc

Re: Trouble with l4rm_region_cache slab

Adam Lackorzynski [EMAIL PROTECTED]: By any chance, can you provide a small test case which triggers this? This is quite difficult to produce. I guessed that this was due to memory leek and I've found some. So it would be easy to make a sample by allocating memory in a same manner. Tomorow, I

Question about semaphores and threads

Hi, Sometimes, I get the following message : semaphore/lib/src/semaphore.c:167:__enqueue_thread(): Error : l4semahore: failed to get priority of thread 17.08: invalid argument (-3) Into sources, the comment says that thread has not been created by l4thread or is dead. But all threads are

Re: Question about semaphores and threads

2008/1/22, Adam Lackorzynski [EMAIL PROTECTED]: The thread should exist, looking at the code path in the semaphore lib. The thread_id used for the prio-get is coming fron an ipc-wait so the thread should be there (in the sense there's a thread at all). The thread-lib might have some other

Re: Question about semaphores and threads

Here is some more info about this log : Each time this log appears, the state of the thread into jdb is, for example : 17.0d (deleted)a0 17.01 rcv,ipc_progr Backtrace of each thread is mainly : l4rm_detach l4th_pages_free __do_cleanup_and_block We observed one thread with the

Re: Trouble with l4rm_region_cache slab

2008/1/22, Adam Lackorzynski [EMAIL PROTECTED]: You're right that the slab objects themselves were not locked. The fix was not as easy as proposed but I think I have fixed this (update l4env and l4rm packages). I hope this fixes your issue. Thank you for this patch. We will test it this

Re: Question about semaphores and threads

2008/1/24, Adam Lackorzynski [EMAIL PROTECTED]: No, the thread is still alive, the '(deleted)' just means that it has already been unregistered at the name service. Name service data is stored into fiasco data to be shown into jdb ? Could you verify the theory that the threadlib has some

Re: Trouble with l4rm_region_cache slab

Hi, The patch fixes the crash. Test ran all night without any problem. Thank you Adam. I will try to get testing machine to get more info about semaphore log. Regards Marc ___ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de

Linux 2.6.24 L4FB and VGA_CONSOLE

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

Re: Linux 2.6.24 L4FB and VGA_CONSOLE

Sorry Adam, I think I have trouble with my ISP. I didn't get your mail. From Adam Lackorzynski I think it has nothing to do with CONFIG_EMBEDDED. Thank you for this info. So you confirm, to build l4linux with L4con, EMBEDDED should be set on version 2.6.24 ? With 'sometimes', do you mean it's

Re: Linux 2.6.24 L4FB and VGA_CONSOLE

From Ronald Aigner: The address of the UTCB is taken in the stub from the environment variable. This environment variable (_dice_corba_env-utcb) is set per default with l4sys_utcb_get which in turn does 'asm( %gs:0 )'. The problem with Linux applications (running on L4Linux) is that they are

Re: Linux 2.6.24 L4FB and VGA_CONSOLE

From Ronald Aigner: I build a test for the IDL you sent, but could not find any error. If the task using the IPC is really a pure L4Env task, then this IDL should work. Do you still see the error if you leave L4Linux out of the boot menu? I still have a problem on that API with current

Re: Back to UTCB IPC

From Ronald Aigner : Strange. How exactly do you set up the worker? Can you send that peace of code? Do you initialize (using dice_server_default_environment) the CORBA_Server_Environment for the worker after the worker thread is started? That's it. In fact, server environment was not inited

Error handling for reply in dice

Hi, I implemented an IDL with a allow_reply_only method : start. When client calls this, it is blocked until server decides to send reply. This works fine in general. But when client thread disapears after call, I cannot get error code from reply function on server side. I tried to use

Re: Error handling for reply in dice

From Ronald Aigner: Before calling the reply function you could set the partner member of the CORBA_Server_Environment parameter. This environment is passed to the error function. In the error function you could then check the partner member. Is it a good idea to use

Fiasco compilation with ubuntu

Hi, I get problem with our version of ubuntu to compile fiasco. date doesn't work exactly in a same manner as gentoo and debian. It adds (+02.00) at the end of output which disturbs make process. Here is the patch that we use. It works on debian and gentoo also. Regards Marc

Re: Fiasco compilation with ubuntu

2008/4/16, Adam Lackorzynski [EMAIL PROTECTED]: Hi Marc, Hi Adam, Ok, the -R is probably a good thing to add but anyway I'd like to know where this happens but cannot see this behaviour in any Ubuntu version I tried. Which Ubuntu and maybe any 'strange' locale set? Our version of ubuntu

Question about ipcmon and assembler IPC shortcut

Hi, I've made a little test with ipcmon. This test is a simple application launched by loader which makes an IPC to names (05) and to log server (06). With assembler IPC shortcut, I don't need to set an accept rule to names. ipcmon doesn't handle requests to names. If I activate jdb IPC

Little fixup around pthreads

Hi guys, Symptoms are: sem_timedwait behaves quite like sem_wait after 0x8000 usec system has been started. Regards Marc diff --git a/src/l4/pkg/uclibc/lib/libpthread/src/restart.h b/src/l4/pkg/uclibc/lib/libpthread/src/restart index 26ae5ea..92b71d3 100644 ---

fiasco.oc i.MX7d port

Hi, I'm trying to port fiasco.oc to i.MX7d. It works, but I cannot start second core. I set trampoline addr into corresponding GPR and enables CORE1. But nothing happens. I saw that trampoline assembler code enables SCU through external registers. But with cortex a7, SCU hasn't got external

Re: fiasco.oc i.MX7d port

11:17:36 +0200, Marc CHALAND wrote: > > Le mercredi 12 octobre 2016, Adam Lackorzynski < > a...@os.inf.tu-dresden.de <javascript:;> > > <javascript:_e(%7B%7D,'cvml','a...@os.inf.tu-dresden.de <javascript:;>');>> > a écrit : > > > > >

fiasco.oc i.MX7d port

Le mercredi 12 octobre 2016, Adam Lackorzynski > a écrit : > > I do not see anything obviously wrong right away. I assume it passes the > while loop? > Yes, the while loop exits. In fact, I think uboot powers up

fiasco.oc i.MX7d port

t; a écrit : > Hi, > > On Wed Oct 05, 2016 at 19:50:45 +0200, Marc CHALAND wrote: > > > So, I ifdefed it but CPU0 still doesn't startup. Can somebody help me ? > > You mean CPU1? Did you also add different setting for SCR? It seems to > be different for imx7. > Yes, I mean

Re: Questions about Fiasco.OC scheduler and L4Linux

Le mer. 22 mars 2017 à 00:59, Adam Lackorzynski <a...@os.inf.tu-dresden.de> a écrit : On Tue Mar 21, 2017 at 08:31:06 +0100, Marc CHALAND wrote: > I'm doing a study to port old software on top of Fiasco.OC. This soft uses > routines which blocks thread scheduling between

Re: Questions about Fiasco.OC scheduler and L4Linux

Le lun. 27 mars 2017 à 15:59, Christian Ludwig <christian_lud...@genua.de> a écrit : Hi, On Monday, 27. March 2017, 15:24:59 Matthias Lange wrote: > On 03/27/2017 03:12 PM, Marc CHALAND wrote: > > <a...@os.inf.tu-dresden.de <mailto:a...@os.inf.tu-dresden.de>> a écrit

Re: Questions about Fiasco.OC scheduler and L4Linux

Le lun. 27 mars 2017 à 15:59, Christian Ludwig a écrit : I guess the question was more about running umodified Linux in a VM on top of Fiasco. In this scenario, Fiasco acts as the hypervisor only. There is the 'uvmm' package that implements a virtual machine monitor,

Re: Questions about Fiasco.OC scheduler and L4Linux

Hi Le mer. 22 mars 2017 à 00:59, Adam Lackorzynski a écrit : > > With a i.MX7d you have hardware support for virtualization, so what > about using that, i.e. running normal Linux in a VM? Getting an L4Linux > for an older version is of course possible but a bit of

Re: Questions about Fiasco.OC scheduler and L4Linux

Le jeu. 30 mars 2017 à 23:54, Adam Lackorzynski a écrit : > > > a7 hangs exactly at that > > point. Any idea to fix this ? > > Multiple. You need to make sure that u-boot boots you non-secure > (there's no hyp-mode on the secure side). u-boot needs to be enabled for >

Questions about Fiasco.OC scheduler and L4Linux

Hi, I'm doing a study to port old software on top of Fiasco.OC. This soft uses routines which blocks thread scheduling between EnterRegion and LeaveRegion call. Is there any equivalent on TUDOS ? Did somebody already get this challenge ? I would like to know if L4Linux uses Fiasco.OC scheduler or