<div dir="ltr">Hello Dengguangxing,<div style><br></div><div style>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)?</div>
<div style><br></div><div style>Gerd</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 24, 2013 at 5:17 AM, Dengguangxing <span dir="ltr"><<a href="mailto:dengguangxing@huawei.com" target="_blank">dengguangxing@huawei.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
We're working on running barrelfish on an armv7 board(not pandaboard).<br>
<br>
Now, we have gone through kernel boot-up, and reach user_space. We load modules like pandaboard do,<br>
include cpu, init, mem_server, monitor, ramfsd, spawnd, startd, skb and memtest.<br>
<br>
The problem is that we stuck with print-message "skb.0: waiting for: all spawnds_up" and "skb.0: waiting for: skb".<br>
<br>
Trace the code we find module spawnd stops at main()->bsp_bootup()->skb_client_connect()->nameservice_blocking_lookup("skb", &iref);<br>
module startd stops at main()->nsb_wait()->nameservice_blocking_lookup("all_spawnds_up", NULL).<br>
<br>
Looking forward to get the reason of this problem, we'll be grateful for helping resolve this.<br>
<br>
sincerely<br>
Deng Guangxing<br>
<br>
<br>
_______________________________________________<br>
Barrelfish-users mailing list<br>
<a href="mailto:Barrelfish-users@lists.inf.ethz.ch">Barrelfish-users@lists.inf.ethz.ch</a><br>
<a href="https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users" target="_blank">https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users</a><br>
</blockquote></div><br></div></div>