[Barrelfish-users] 回复:AW: Failed to run barrelfish inside qemu withnetworking enabled
kdf5000
kdf5000 at 163.com
Mon Jul 18 05:51:20 CEST 2016
Hi,
Thank you for your prompt reply! I checkout the latest released version(release2016-06-29) and build again, it shows a different error:
routing GSI 0 - 2 - INTI 2 - APIC 1 (coreid 1) vector 32
kernel 1: unhandled IRQ 0
e1000n.1.0: Reset done..
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
#######
For service [e1000] MAC= 52:54:00:12:34:56
using 8192 slots for internal buffer
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
########### Driver with interrupts
e1000: Media type: copper, Link speed: 1 Gb in Full duplex.
service [e1000_0] exported at iref 261
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
kernel 1: e1000n: IRQ message buffer overflow on IRQ 0
################################
For service [e1000_0_FILT] MAC= 52:54:00:12:34:56
idc_c_port_mng_srv: success [e1000_PORTS_MNG]
LWIP: lwip_init: done with connection setup
LWIP: done with connection setup
NGKDM: done with most of things for device[e1000]
netd.0 in alloc_mem() ..//lib/i
Allocating memory region frame failed!
Aborted
It seems that the configuration of memory is improper. Should I change the configuration in file (include/barrelfish/net_constants.h)? Here is mymenu.lst.x86_64:
title Barrelfish
root (nd)
kernel /x86_64/sbin/elver loglevel=4
module /x86_64/sbin/cpu loglevel=4
module /x86_64/sbin/init
# Domains spawned by init
module /x86_64/sbin/mem_serv
module /x86_64/sbin/monitor
# Special boot time domains spawned by monitor
module /x86_64/sbin/ramfsd boot
module /x86_64/sbin/skb boot
modulenounzip /eclipseclp_ramfs.cpio.gz nospawn
modulenounzip /skb_ramfs.cpio.gz nospawn
module /x86_64/sbin/kaluga boot
module /x86_64/sbin/acpi boot
module /x86_64/sbin/spawnd boot
#bootapic-x86_64=1-15
module /x86_64/sbin/startd boot
module /x86_64/sbin/routing_setup boot
# Drivers
module /x86_64/sbin/pci auto
module /x86_64/sbin/corectrl auto
module /x86_64/sbin/ahcid auto
## For networking
#module /x86_64/sbin/rtl8029
module /x86_64/sbin/e1000n core=1
## Other services needed for networking
module /x86_64/sbin/NGD_mng cardname=e1000
module /x86_64/sbin/netd cardname=e1000
# General user domains
module /x86_64/sbin/serial
module /x86_64/sbin/fish nospawn
module /x86_64/sbin/angler serial0.terminal xterm
原始邮件
发件人:Häcki Ronironi.haecki at inf.ethz.ch
收件人:孔德飞kdf5000 at 163.com; barrelfish-users at lists.inf.ethz.chbarrelfish-users@lists.inf.ethz.ch
发送时间:2016年7月17日(周日) 22:59
主题:AW: [Barrelfish-users] Failed to run barrelfish inside qemu withnetworking enabled
Hi, It seems like you are starting the e1000n driver and other network related services seem to assume there is an e1000n card. Can you show us the contents of your menu.lst file (in your build directory platforms/x86/menu.lst.x86_64)? The default menu.lst file that is generated most likely uses the e1000n driver and you have to change the lines as described in the wiki (Changes in the menu.lst). --Roni ________________________________________ Von: Barrelfish-users [barrelfish-users-bounces at lists.inf.ethz.ch]quot; im Auftrag von quot;孔德飞 [kdf5000 at 163.com] Gesendet: Sonntag, 17. Juli 2016 14:32 An: barrelfish-users at lists.inf.ethz.ch Betreff: [Barrelfish-users] Failed to run barrelfish inside qemu with networking enabled Hello, I have successfully compiled and run barrelfish in qemu. I read the wiki and try to run barrelfish with networking enabled following the instructions in the wiki page(http://wiki.barrelfish.org/qemu_networking ), the only difference is that I replace the rtl8029 adapter with e1000n which is default in new release version. When booting the barrelfish in qemu(make emu_x86_64), it gives the following errors: kernel 1: e1000n: IRQ message buffer overflow on IRQ 0 kernel 1: e1000n: IRQ message buffer overflow on IRQ 0 kernel 1: e1000n: IRQ message buffer overflow on IRQ 0 kernel 1: e1000n: IRQ message buffer overflow on IRQ 0 kernel 1: e1000n: IRQ message buffer overflow on IRQ 0 kernel 1: e1000n: IRQ message buffer overflow on IRQ 0 net_queue_manager: Use raw interface Connected to driver [e1000] remaining_lwip_init: allocating pbuf memory #### Networking with small amount of memory ##### #### [0:4:netd] [for_qemu] [1] MEM_SIZE[62914560], PBUF_POOL_SIZE[16384], MEMP_MAX[14], RECEIVE_BUFFERS[2444] qid[0]#### Assertion failed on core 0 in netd: rem_len = 0, function pbuf_alloc_tagged, file ..//lib/lwip/src/core/pbuf.c, line 454. Aborted
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/barrelfish-users/attachments/20160718/73b61bf3/attachment-0001.html>
More information about the Barrelfish-users
mailing list