The "region overlap" problem in the L4/Fiasco hello example
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/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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 chenggh wrote on 13.06.2006 09:15 this:
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 modaddr 0x06000000 ? 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/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
HTH, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEjqCdvCdOf9l7ipgRAr2dAJ46W6pOKxOkUKks55qqw3NtA+OoggCgjKEC 618NZaQb/8aHZpJC9tFpom0= =2IBh -----END PGP SIGNATURE-----
Ronald Aigner wrote on 06/13/06 13:25:
chenggh wrote on 13.06.2006 09:15 this:
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:
I've the same problem with the hello example. But when I change the modaddr the problem resides. The "Module Memory" is alway beginning at 0x0013a000 and thus overlaps with other ones. Anyone has an idea why? -- title hello world kernel /bootstrap modaddr 0x02000000 module /fiasco -nowait -nokdb module /sigma0 module /roottask module /hello
On Fri Aug 11, 2006 at 18:06:31 +0200, Emanuel Thomas wrote:
Ronald Aigner wrote on 06/13/06 13:25:
chenggh wrote on 13.06.2006 09:15 this:
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:
I've the same problem with the hello example. But when I change the modaddr the problem resides. The "Module Memory" is alway beginning at 0x0013a000 and thus overlaps with other ones. Anyone has an idea why?
Do you use a GRUB that understands modaddr? Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
participants (4)
-
Adam Lackorzynski -
chenggh -
Emanuel Thomas -
Ronald Aigner