[Barrelfish-users] Fwd: Re: Problem of booting barrelfish on arm board

[Dengguangxing]

Hi Gerd,

Arguments we passing to these binaries are:
kernel /armv7/sbin/cpu loglevel=4
module  /armv7/sbin/init

module  /armv7/sbin/mem_serv
module  /armv7/sbin/monitor

module  /armv7/sbin/ramfsd boot
module  /armv7/sbin/skb boot
modulenounzip /skb_ramfs.cpio.gz nospawn
module  /armv7/sbin/spawnd boot
module  /armv7/sbin/startd boot

On 2013/6/24 14:34, Gerd Zellweger wrote:
> Hello Dengguangxing,
> 
> Can you show us the menu.lst file you use for booting (or in case you don't parse a menu.lst file for your arm boot-up: which binaries do you load and what are the arguments your passing to the binaries)?
> 
> Gerd
> 
> 
> On Mon, Jun 24, 2013 at 5:17 AM, Dengguangxing <dengguangxing at huawei.com <mailto:dengguangxing at huawei.com>> wrote:
> 
>     Hi all,
> 
>     We're working on running barrelfish on an armv7 board(not pandaboard).
> 
>     Now, we have gone through kernel boot-up, and reach user_space. We load modules like pandaboard do,
>     include cpu, init, mem_server, monitor, ramfsd, spawnd, startd, skb and memtest.
> 
>     The problem is that we stuck with print-message "skb.0: waiting for: all spawnds_up" and "skb.0: waiting for: skb".
> 
>     Trace the code we find module spawnd stops at main()->bsp_bootup()->skb_client_connect()->nameservice_blocking_lookup("skb", &iref);
>     module startd stops at main()->nsb_wait()->nameservice_blocking_lookup("all_spawnds_up", NULL).
> 
>     Looking forward to get the reason of this problem, we'll be grateful for helping resolve this.
> 
>     sincerely
>     Deng Guangxing
> 
> 
>     _______________________________________________
>     Barrelfish-users mailing list
>     Barrelfish-users at lists.inf.ethz.ch <mailto:Barrelfish-users at lists.inf.ethz.ch>
>     https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users
> 
>