Michael, Thanks for responding,
-----Original Message-----
From: Michael Hohmuth <hohmuth(a)innocent.com>
To: Paul Phillips <pphillips(a)ivue.com>
Cc: l4-hackers(a)os.inf.tu-dresden.de <l4-hackers(a)os.inf.tu-dresden.de>
Date: Tuesday, January 26, 1999 11:21 AM
Subject: Re: multiple servers
>Paul,
>
>thanks for trying Fiasco and L4Linux!
>
>"Paul Phillips" <pphillips(a)ivue.com> writes:
>
>> Right now I'm trying to run two servers concurrently. This is just a
>> "proof of concept" for now. I am trying to run the "hello" server
>> (relocated to 0x2400000) along with the L4-Linux server. I load the
>> "hello"server first and then L4-Linux. L4-linux gets to the
>> "Calibrating delay loop.." and hangs. I am obviously forgetting
>> something here. Is the printf used by the hello server causing a
>> problem?
>
>No, I don't think so.
>
>I take it that without `hello', L4Linux works correctly. My guess
>would be that hello has trouble running at the memory location you
>linked it at. Did you see `hello's output ("hello: My thread-id
>is...") at least once?
>
Yes, both 'hello' and L4Linux run correctly (some bugs in L4, but that's OK
for now)
when running as a single server.
I do see the 'hello' output one time only:
"hello: My id is 80000" , in the middle of the Linux bootup messages.
I tried 'hello' at the default 0x200000 as well as 0x2400000. Both perform
the same.
>Did you get `hello' to work without L4Linux?
>
Yes, no problem!
>Why did you relocate it to 0x2400000? It should be able to run (even
>concurrently with L4Linux) at the memory location it is linked to
>using the distributed version of l4/server/hello/Makefile, 0x200000.
>
I thought perhaps GRUB was trying to load both 'hello' and L4Linux at the
same physical address and that was the reasoning behind my relocating it. It
makes no difference.
I have GDB running, but because the system hangs I can't generate a
backtrace. Any ideas?
Thanks
Paul Phillips
