Problems with l4linux
Valery V. Sedletski
_valerius at mail.ru
Wed Oct 22 12:14:26 CEST 2008
On Wed, 22 Oct 2008 18:00:04 +1300 (MSD), Valery V. Sedletski wrote:
>
>I unmommented the fragment and recompiled, but an error appeared:
>
>loader | vmlinuz26: Starting application using libld-l4.s.so
>loader | [36mvmlinuz26,#f: Loading binary[m
>loader | vmlinuz26,#f: Loading ldso
>loader | vmlinuz26,#f: Starting libld-l4.s.so at 000138e0 via 0000cbe8
>l4lx | [34;1m======> L4Linux 2.6 starting... <========[0m
>l4lx | Linux version 2.6.26-l4-svn119-dirty2 (root at localhost) (gcc version 4
>l4lx : .2.2 20071128 (prerelease) (4.2.2-3mdv2008.0)) #5 Wed Oct 22 15:59:47
>l4lx : PETST 2008
>l4lx | Binary name: vmlinuz26
>l4lx | Linux kernel command line (8 args): mem=100M video=l4fb:refreshsleep:
>l4lx : 200 l4fb.nograb=1 load_ramdisk=1 ramdisk_size=40960 root=/dev/ram l4e
>l4lx : nv_rd=(nd)/tftpboot/drops/ramdisk/drops-fp.rd panicblink=0
>l4lx | Image: 00400000 - 00854000 [4432 KiB].
>l4lx | Areas: Text: 00400000 - 0075d000 [3444kB] (a bit longer)
>l4lx | Data: 0075d000 - 00782978 [150kB]
>l4lx | Initdata: 00786000 - 007bb000 [212kB]
>l4lx | BSS: 007bc000 - 0085393c [606kB]
>l4lx | l4lx_thread_create: Created thread 0f.03 (tamer0)
>l4lx | Tamer0 is 0f.03
>l4lx | Using tamed mode.
>ROOT: Sending all ports (for cli/sti) to task #0d
>l4lx | Got 65536 out of 65536 I/O ports
>l4lx | L4RM: unknown exception src=F.02 exc=-5 ip=00405afd data=0,0
>con | vc_loop(): vc[1] running as C.07
>con | vc[1] 800x600 at 16, bpl:1600, gmode:0x25, evprt:E.03 save:0
>run | contxt_init(): 800x582, cols:100, lines:41, sb_lines:1041
>
Here is a disassembly around the place of exception:
/home/valerius/src/tudos/l4linux-2.6/arch/l4/kernel/arch-i386/ioport.c:475
405ae1: c7 44 24 08 00 00 01 movl $0x10000,0x8(%esp)
405ae8: 00
405ae9: c7 44 24 04 00 00 01 movl $0x10000,0x4(%esp)
405af0: 00
405af1: c7 04 24 e9 4f 70 00 movl $0x704fe9,(%esp)
405af8: e8 18 fe 29 00 call 6a5915 <LOG_printf>
/home/valerius/src/tudos/l4linux-2.6/arch/l4/kernel/arch-i386/ioport.c:480
405afd: fa cli
405afe: fb sti
405aff: eb 9e jmp 405a9f <l4x_iodb_init+0x8f>
405b01: eb 0d jmp 405b10 <sys_ioperm>
405b03: 90 nop
405b04: 90 nop
405b05: 90 nop
405b06: 90 nop
So, 00405afd is the address of cli instruction in the same fragment I uncommented
More information about the l4-hackers
mailing list