From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: ??? <pnk003@naver.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
Date: Thu, 15 Oct 2015 08:02:17 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8353FE@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <9d3f39f1cd6d917e5e74c12b73f90dd@cweb24.nm.nhnsystem.com>
Hi,
From: 최익성 [mailto:pnk003@naver.com]
Sent: Thursday, October 15, 2015 2:02 AM
To: De Lara Guarch, Pablo; dev@dpdk.org
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
Dear De Lara Guarch, Pablo.
I checked what you mentioned.
* Fedora Linux kernel version is as follows.
$ uname -r (print kernel name)
3.17.7-200.fc20.x86_64
$ uname -a
Linux sdnlab-k01 3.17.7-200.fc20.x86_64 #1 SMP Wed Dec 17 03:35:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version
Linux version 3.17.7-200.fc20.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org<mailto:mockbuild@bkernel01.phx2.fedoraproject.org>) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) ) #1 SMP Wed Dec 17 03:35:33 UTC 2014
$ rpm -q kernel
kernel-3.11.10-301.fc20.x86_64
kernel-3.17.7-200.fc20.x86_64
kernel-3.15.6-200.fc20.x86_64
$ cat /etc/redhat-release
Fedora release 20 (Heisenbug)
* Vt-d seems to be enabled. I heard that the result values of 3 or 5 mean the virtualization activated.
$ sudo rdmsr 0x3A
5
If VT-d is enabled, and you are running on the host, you need to use “intel_iommu=on iommu=pt” in the kernel parameters.
Anyway, there is a known issue with kernels between 3.15 and 3.17, with VT-d: take a look at the bug 6.25 here:
http://dpdk.readthedocs.org/en/v2.1.0/rel_notes/known_issues.html
I suggest you to disable VT-d and see if you problem goes away, and if so,
update your kernel and include the line above if you need VT-d enabled for any reason.
And I have strange error during the yum update.
$ sudo yum update
--> Finished Dependency Resolution
--> Running transaction check
---> Package aspell-en.x86_64 50:7.1-6.fc20 will be installed
---> Package kernel-devel.x86_64 0:3.11.10-301.fc20 will be erased
---> Package kernel-modules-extra.x86_64 0:3.11.10-301.fc20 will be erased
---> Package kernel-modules-extra.x86_64 0:3.19.8-100.fc20 will be installed
--> Processing Dependency: kernel-uname-r = 3.19.8-100.fc20.x86_64 for package: kernel-modules-extra-3.19.8-100.fc20.x86_64
--> Finished Dependency Resolution
Error: Package: kernel-modules-extra-3.19.8-100.fc20.x86_64 (updates)
Requires: kernel-uname-r = 3.19.8-100.fc20.x86_64
Installed: kernel-3.11.10-301.fc20.x86_64 (@anaconda)
kernel-uname-r = 3.11.10-301.fc20.x86_64
Installed: kernel-3.15.6-200.fc20.x86_64 (installed)
kernel-uname-r = 3.15.6-200.fc20.x86_64
Installed: kernel-3.17.7-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.17.7-200.fc20.x86_64
Available: kernel-debug-3.11.10-301.fc20.x86_64 (fedora)
kernel-uname-r = 3.11.10-301.fc20.x86_64+debug
Available: kernel-debug-3.19.8-100.fc20.x86_64 (updates)
kernel-uname-r = 3.19.8-100.fc20.x86_64+debug
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
* There are virtual bridge and virtual nic in the Fedora server.
$ ifconfig or $ ifconfig -a
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet ?.?.?.? netmask 255.255.255.0 broadcast ?.?.?.?
ether 52:54:00:f2:70:98 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:f2:70:98 txqueuelen 500 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Thank you very much.
Sincerely Yours,
Ick-Sung Choi.
-----Original Message-----
From: "De Lara Guarch, Pablo"<pablo.de.lara.guarch@intel.com<mailto:pablo.de.lara.guarch@intel.com>>
To: "???"<pnk003@naver.com<mailto:pnk003@naver.com>>; "dev@dpdk.org<mailto:dev@dpdk.org>"<dev@dpdk.org<mailto:dev@dpdk.org>>;
Cc:
Sent: 2015-10-14 (수) 22:19:02
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
Hi Ick-Sung,
> * Fedora OS version : Fedora release 20 (Heisenbug)
>
> * gcc version : gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7).
>
> * Intel(R) Xeon(R) CPU E5-2680 10 cores, 64G bytes system memory.
> * 2 2-port NIC cards, Intel® 82599ES 10 Gigabit Ethernet 2 port Controller.
> SFI/SFP+. optical link. Hence there are 4 10 GbE ports.
>
> * I attached DPDK setup script in my environment.
What is your kernel version? And also, can you check if you have VT-d enabled?
Thanks,
Pablo
>
>
> Thank you very much.
>
> Sincerely Yours,
>
> Ick-Sung Choi.
[http://mail.naver.com/readReceipt/notify/?img=b9nqKAIOWNgqpoFvaxmsa6MwMrtrpAvwFrE9pxbdMquZMobqpovmpz3gMX%2B0MoUd74lR74lcWNFlbX30WLloWrdQaXICM4wT743074wCb4u5pXkCb4Fctz05%2Bzkn74FTWt%3D%3D.gif]
next prev parent reply other threads:[~2015-10-15 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 1:29 최익성
2015-10-14 1:38 ` Xu, Qian Q
2015-10-14 1:49 ` 최익성
2015-10-14 13:19 ` De Lara Guarch, Pablo
2015-10-15 1:01 ` 최익성
2015-10-15 8:02 ` De Lara Guarch, Pablo [this message]
2015-10-15 8:10 ` Mcnamara, John
2015-10-15 23:46 ` 최익성
2015-10-19 14:48 ` 최익성
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=E115CCD9D858EF4F90C690B0DCB4D8973C8353FE@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=pnk003@naver.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).