From: Bruce Richardson <bruce.richardson@intel.com>
To: Nagendra Prabhu A T <nagendraprabhu.a.t@gmail.com>
Cc: <anatoly.burakov@intel.com>, <dev@dpdk.org>
Subject: Re: unable to bind to vfio-pci
Date: Tue, 21 Feb 2023 16:06:19 +0000 [thread overview]
Message-ID: <Y/Tr+0ChDLS3hT3R@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CACG-zq9EWCTfv=OW4nU=Y6qyec+OQKTUR-oMZhNfHfSbTKg7Eg@mail.gmail.com>
On Tue, Feb 21, 2023 at 09:30:15PM +0530, Nagendra Prabhu A T wrote:
> HI Bruce,
> Thanks for your reply.
> I have removed the binding of all other ports. So , i can confirm that
> #2 is taken care of.
> I tried using a different driver "uio_pci_generic". I still see the
> same issue for that driver as well.
> The problem seems to be because the write operation is not happening in
> "bind" file.
> Infact tried doing the following step manually. That also failed
> echo sh -c 0000:51:00.0 > /sys/bus/pci/drivers/uio_pci_generic/bind
> bash: echo: write error: No such device
The "sh -c" doesn't look right in that command. It should just echo the
device id to the bind file. However, it's generally recommended just to use
the devbind script, as more writes to sysfs may be necessary first, e.g. to
register the device ids first.
> I have required permission for the file.
> I tried doing with "sudo"
> I dont have selinux running
> So not sure whats blocking me. Infact , even
> "cat /sys/bus/pci/drivers/uio_pci_generic/bind" is failing
> Can you please help.
To track down issues other than the obvious, I think we need more
information. For example, what NIC card is this? Are there any useful error
messages in dmesg?
/Bruce
next prev parent reply other threads:[~2023-02-21 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:35 Nagendra Prabhu A T
2023-02-21 14:45 ` Bruce Richardson
2023-02-21 16:00 ` Nagendra Prabhu A T
2023-02-21 16:06 ` Bruce Richardson [this message]
2023-02-21 16:16 ` Nagendra Prabhu A T
2023-02-21 16:27 ` Bruce Richardson
2023-02-21 17:03 ` Stephen Hemminger
2023-02-21 17:27 ` Nagendra Prabhu A T
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=Y/Tr+0ChDLS3hT3R@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=nagendraprabhu.a.t@gmail.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).