Hi,everyone:
When I boot the hello example in the L4/Fiasco. there is a "region
overlap" in the booting information. I don't why it could be like this. The
grub configuration and the error information is following:
Grub:
title fiasco_hello_new
kernel (hd0,1)/boot/fiasco_hello_new/bootstrap -comport 1 -serial
module (hd0,1)/boot/fiasco_hello_new/main -nokdb
module (hd0,1)/boot/fiasco_hello_new/sigma0
module (hd0,1)/boot/fiasco_hello_new/roottask
module (hd0,1)/boot/…
[View More]fiasco_hello_new/hello
minicom_log:
L4 Bootstrapper
Loading (hd0,1)/boot/fiasco_hello_new/main
Kernel at 00002000-0038f408
Detected new-style DD-L4(v2)/Fiasco x86
Loading (hd0,1)/boot/fiasco_hello_new/sigma0
Loading (hd0,1)/boot/fiasco_hello_new/roottask
loaded module section: [0028d000-00324e13) .Roottask syms/lines (copy)
overlaps with: [00300000-0038f408)
(hd0,1)/boot/fiasco_hello_new/main
[00002000-0005ae70) (hd0,1)/boot/fiasco_hello_new/main
[0005b000-0005fcfd) (hd0,1)/boot/fiasco_hello_new/main
[00090000-0009432d) (hd0,1)/boot/fiasco_hello_new/sigma0
[00095340-00096824) (hd0,1)/boot/fiasco_hello_new/sigma0
[0009f000-00100000) BIOS area
[00100000-0010dc04) bootstrap
[0013f000-0028ccb0) Modules Memory
[00300000-0038f408) (hd0,1)/boot/fiasco_hello_new/main
[1dff0000-ffffffff) Deep Space
region overlap
Thanks!
Cheng
[View Less]
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-…
[View More]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.
[View Less]
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 ###
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 …
[View More]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
[View Less]
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 […
[View More]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
[View Less]
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
&…
[View More]gt;
> 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/
[View Less]
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/…
[View More]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/
[View Less]