DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Srinivas Reddi <srinivas.reddi@aricent.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] MENNIC1.2 host-sim crashed for me
Date: Tue, 15 Jul 2014 00:01:14 +0000	[thread overview]
Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD01150C89@BPXM14GP.gisp.nec.co.jp> (raw)
In-Reply-To: <97f38ab32ebb49759fb699b4bc23e623@GURMBXV02.AD.ARICENT.COM>

Hi,

> Subject: [dpdk-dev] MENNIC1.2 host-sim crashed for me
> 
> Hi,
> I want to run MEMNIC 1.2 application .
> 
> 1.       I compiled DPDK1.6
> 
> 2.       I compiled memnic.12
> 
> 3.       And while running memnic-hostsim app    got strucked
> 
> 4.
> 
> 5.       [root@localhost host-sim]# ./memnic-host-sim /dev/shm/ivshm
> 
> Bus error (core dumped)
> 
> 
> 
> Core was generated by `./memnic-host-sim  /dev/shm/ivshm'.
> 
> Program terminated with signal SIGBUS, Bus error.
> 
> #0  0x0000003a82e894e4 in memset () from /lib64/libc.so.6
> 
> Missing separate debuginfos, use: debuginfo-install glibc-2.18-11.fc20.x86_64
> 
> (gdb) bt
> 
> #0  0x0000003a82e894e4 in memset () from /lib64/libc.so.6
> 
> #1  0x00000000004008a3 in init_memnic (nic=0x7ffff6fe2000) at host-sim.c:55
> 
> #2  0x0000000000400a8a in main (argc=2, argv=0x7fffffffe4a8) at host-sim.c:106
> 
> (gdb)
> 
> 
> 
> 
> 
> Got error at line 55 .. saying nic is read only..


I have never tried host-sim yet though.
I guess it's the cause that host-sim doesn't increase the shared memory size.
Could you try booting qemu first with -device ivshmem,size=16,shm=/ivshm then run host-sim?

thanks,
Hiroshi

> 
> 
> 
> 53 static void init_memnic(struct memnic_area *nic)
> 
> 54 {
> 
> 55     memset(nic, 0, sizeof(*nic));
> 
> 56     nic->hdr.magic = MEMNIC_MAGIC;
> 
> 57     nic->hdr.version = MEMNIC_VERSION;
> 
> 58     /* 00:09:c0:00:13:37 */
> 
> 59     nic->hdr.mac_addr[0] = 0x00;
> 
> 60     nic->hdr.mac_addr[1] = 0x09;
> 
> 61     nic->hdr.mac_addr[2] = 0xc0;
> 
> 62     nic->hdr.mac_addr[3] = 0x00;
> 
> 63     nic->hdr.mac_addr[4] = 0x13;
> 
> 64     nic->hdr.mac_addr[5] = 0x37;
> 
> 65 }
> 
> 
> 
> Thanks,
> 
> Srinivas.
> 
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is
> addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose
> other than for what it is intended. If you have received this message in error, please notify the originator immediately.
> If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering,
> or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use
> of the information transmitted by this email including damage from virus."

  reply	other threads:[~2014-07-15  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 10:17 Srinivas Reddi
2014-07-15  0:01 ` Hiroshi Shimamoto [this message]
2014-07-15 12:37 [dpdk-dev] FW: " Srinivas Reddi
2014-07-15 12:53 ` [dpdk-dev] " Hiroshi Shimamoto
2014-07-15 14:40   ` Srinivas Reddi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7F861DC0615E0C47A872E6F3C5FCDDBD01150C89@BPXM14GP.gisp.nec.co.jp \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=dev@dpdk.org \
    --cc=srinivas.reddi@aricent.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).