From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Brandon Lo <blo@iol.unh.edu>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>
Subject: Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
Date: Fri, 9 Oct 2020 09:58:10 +0000 [thread overview]
Message-ID: <0f6f66089f234037b599334ba6ec36c1@pantheon.tech> (raw)
In-Reply-To: <CAOeXdvbVh8RjYrQNE26LAPS9YtgkV49Jyo8tAo_ivW3TGg=uaw@mail.gmail.com>
It's possible that vfio-pci is not loaded, /sys/bus/pci/drivers//unbind is missing vfio-pci in the path.
Try to modprobe vfio-pci and see whether it shows under /sys/bus/pci/drivers/.
If this is the case, then you may want to add vfio-pci to /etc/modules so that it gets loaded automatically on boot.
Juraj
> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of Brandon Lo
> Sent: Thursday, October 8, 2020 8:30 PM
> To: Ferruh Yigit <ferruh.yigit@intel.com>
> Cc: ci@dpdk.org; Chen, Zhaoyan <zhaoyan.chen@intel.com>; Tu, Lijuan
> <lijuan.tu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>
> Subject: Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
>
> I may have sent that thanks email too early.
>
> Vt-d is enabled now for both machines, but the same error -22 is still occurring in
> dmesg.
>
> `/sys/kernel/iommu_groups/` is empty.
> Perhaps the kernel parameters are not being set properly?
>
> Thanks,
> Brandon
>
> On Thu, Oct 8, 2020 at 2:19 PM Brandon Lo <blo@iol.unh.edu> wrote:
> >
> > Thanks, I was not aware that the system had Vt-d disabled.
> >
> > On Thu, Oct 8, 2020 at 1:46 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > >
> > > On 10/8/2020 5:51 PM, Brandon Lo wrote:
> > > > Hi everyone,
> > > >
> > > > I am having issues trying to bind both Intel Niantic and Fortville
> > > > NICs over to VFIO-PCI.
> > > > The machines are running Ubuntu 18.04 with kernel 4.15.0-55.
> > > > The dpdk-devbind.py tool outputs "Cannot bind to driver vfio-pci"
> > > > and "Cannot open /sys/bus/pci/drivers//unbind".
> > > >
> > > > The dmesg output contains "vfio-pci: probe of [PCI Address] failed
> > > > with error -22" whenever I try to bind it.
> > > > Both machines have "intel_iommu=on iommu=pt" in their kernel
> parameters.
> > > >
> > >
> > > Is 'Vt-d' enabled in the bios?
> > >
> > > What do you see under '/sys/kernel/iommu_groups/' folder?
> >
> >
> >
> > --
> >
> > Brandon Lo
> >
> > UNH InterOperability Laboratory
> >
> > 21 Madbury Rd, Suite 100, Durham, NH 03824
> >
> > blo@iol.unh.edu
> >
> > www.iol.unh.edu
>
>
>
> --
>
> Brandon Lo
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> blo@iol.unh.edu
>
> www.iol.unh.edu
next prev parent reply other threads:[~2020-10-09 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:51 Brandon Lo
2020-10-08 17:46 ` Ferruh Yigit
2020-10-08 18:19 ` Brandon Lo
2020-10-08 18:30 ` Brandon Lo
2020-10-09 9:58 ` Juraj Linkeš [this message]
2020-10-09 11:14 ` Ferruh Yigit
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=0f6f66089f234037b599334ba6ec36c1@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=zhaoyan.chen@intel.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).