name_server problem

Christian Helmuth ch12 at os.inf.tu-dresden.de
Tue Sep 7 10:05:25 CEST 2004


Hello,

On Tue, Sep 07, 2004 at 08:17:32AM +0200, Leon wrote:
> Hi all,
> 
> I am having a problem with the new name_server from the l4vfs package.
> 
> I load it the name_server module with grub:
> 
> 	kernel (nd)/fiasco/rmgr -sigma0 task modname "L4Linux task"
> 	modaddr 0x02000000
> 	module (nd)/fiasco/fiasco -nowait -nokdb -nofancy -serial -comspeed  
> 115200 -comport 1
> 	module (nd)/fiasco/sigma0
> 	module (nd)/fiasco/names
> 	module (nd)/fiasco/log
> 	module (nd)/fiasco/dm_phys
> 	module (nd)/fiasco/l4io --noirq
> 	module (nd)/fiasco/tftp -i -s 192.168.1.4
> 	module (nd)/fiasco/simple_ts
> 	module (nd)/fiasco/l4exec
> 	module (nd)/fiasco/l4dope --l4io
>  	module (nd)/fiasco/name_server
>   	module (nd)/fiasco/loader (nd)/fiasco/dope-l4linux.cfg
> 	vbeset 0x117
> 
> and it produces the following debug output:
> 
> 	name_ser| main(): 2 ...
> 	 (0)/
> 	    file1 (56.1)
> 	    test3 (5)/
> 	        c (8)/
> 	        b (7)/
> 	        a (6)/
> 	    test2 (4)/
> 	    test1 (3)/
> 	    server (2)/
> 	    linux (1)/
> 	name_ser| main(): 3 ...

That looks okay for me.

> Q1: Where did the name_server get these names?

It is the default debugging configuration. Never mind the names.

> I wanted to test the name_server module so I ran "name_server_test" which  
> always crashes with output:
> 
> tftp    | Loading (nd)/fiasco/name_server_test [549kB]
> loader  | "(nd)/fiasco/name_server_test" is a valid binary image
> loader  | Setting libpath to (nd)/fiasco/
> exec    | name_server_test: Loading
> exec    | name_server_test: Has no dynamic info
> exec    | name_server_test: Saved 20647 bytes of symbols
> exec    | name_server_test: library "libloader.s.so" not found
> loader  | name_server_test: Starting sigma0-style application
> exec    | name_server_test: Packed 14374 bytes of symbols
> exec    | name_server_test: Packed 69740 bytes of lines
> loader  | name_server_test,#14: Entry at 00009c74 => 00980000
> loader  | name_server_test,#14: Started
> run     | .
> n_s_test| main(): Results follow below (should be as predicted (123) ==  
> '123').
> n_s_test| main(): Volume stuff: *******************
> n_s_test| main(): Name server thread id (8.2) 'D.02'
> name_ser| l4vfs_basic_name_server_thread_for_volume_component(): Before:  
> l4vfs_
> name_ser: basic_name_server_thread_for_volume_component()
> name_ser| l4vfs_basic_name_server_thread_for_volume_component(): After:  
> l4vfs_b
> name_ser: asic_name_server_thread_for_volume_component()
> n_s_test| main(): Volume server for NS volume (8.2) 'D.02'
> name_ser| l4vfs_basic_name_server_thread_for_volume_component(): Before:  
> l4vfs_
> name_ser: basic_name_server_thread_for_volume_component()
> name_ser| l4vfs_basic_name_server_thread_for_volume_component(): After:  
> l4vfs_b
> name_ser: asic_name_server_thread_for_volume_component()
> n_s_test| main(): Volume server for other volume (0.0) '7FF.7F'
> name_ser| l4vfs_name_space_provider_register_volume_component():  
> register_volum
> name_ser: e: 5.0
> name_ser| L4RM: [PF] read at 0x012ffd14, eip 012003f9, src D.02
> name_ser| [D.0] l4rm/lib/src/pagefault.c:75:__unknown_pf():
> name_ser|  unhandled page fault
> 
> I seem to get a lot of Double PF when loading my own or test programs.

That's strange. My CVS version runs without any problems. Which version
are you working with? L4Env release? Remote CVS (date)?

Regards
-- 
Christian Helmuth
## Dept. of CS, TU Dresden,  Germany ##
## http://os.inf.tu-dresden.de/~ch12 ##




More information about the l4-hackers mailing list