DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hyun Yoo <easetheworld@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Crash when 'ifconfig vEth0 X.X.X.X'
Date: Mon, 10 Aug 2015 06:50:31 +0900	[thread overview]
Message-ID: <CAJzQz-HVRdXUdH4fu57fJyWTJzi8exSj29RNLa-Fju3YOyWtkg@mail.gmail.com> (raw)

After kni, I want to wake vEth0 up automatically.
so, I executed 'ifconfig vEth0 X.X.X.X' programatically with various ways.

A) put system('ifconfig...)' right after check_all_ports_link_status() in
main()  examples/kni/main.c
B) put system('ifconfig...)' in callback using
rte_eth_dev_callback_register().
C) in shell script,
    examples/kni/build/kni &
    for loop
          ifconfig ...

In either ways, linux crashes sometimes.
No keyboard, mouse works. I have to reboot.
There was usually no error message but once time I saw something about irq
balance...
It seems ifconfig shouldn't be run right after(or before) link is up, maybe.

Has anyone experienced the same?

I'm using DPDK 2.0.0 on RHEL 6.5 (kernel 2.6.32).

                 reply	other threads:[~2015-08-09 21:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAJzQz-HVRdXUdH4fu57fJyWTJzi8exSj29RNLa-Fju3YOyWtkg@mail.gmail.com \
    --to=easetheworld@gmail.com \
    --cc=dev@dpdk.org \
    /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).