* error message: VF is not privileged to issue opcode 89-1
@ 2013-12-20 9:44 vaughan
2013-12-20 16:35 ` Greg Rose
2013-12-20 16:42 ` Ajit Khaparde
0 siblings, 2 replies; 4+ messages in thread
From: vaughan @ 2013-12-20 9:44 UTC (permalink / raw)
To: netdev; +Cc: vaughan
Hi experts,
I encounter the following error when creating SR-IOV VF for Emulex 10GB
nic on 3.8.13 kernel.
# modprobe be2net num_vfs=4
be2net 0000:30:00.0: irq 214 for MSI/MSI-X
be2net 0000:30:00.0: enabled 1 MSI-x vector(s)
be2net 0000:30:00.0: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:00.0: created 1 TX queue(s)
pci 0000:30:04.0: [19a2:0710] type 00 class 0x020000
pci 0000:30:04.1: [19a2:0710] type 00 class 0x020000
pci 0000:30:04.2: [19a2:0710] type 00 class 0x020000
pci 0000:30:04.3: [19a2:0710] type 00 class 0x020000
be2net 0000:30:00.0: Emulex OneConnect(be3): PF port 0
be2net 0000:30:00.1: irq 215 for MSI/MSI-X
be2net 0000:30:00.1: enabled 1 MSI-x vector(s)
be2net 0000:30:00.1: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:00.1: created 1 TX queue(s)
pci 0000:30:06.0: [19a2:0710] type 00 class 0x020000
pci 0000:30:06.1: [19a2:0710] type 00 class 0x020000
pci 0000:30:06.2: [19a2:0710] type 00 class 0x020000
pci 0000:30:06.3: [19a2:0710] type 00 class 0x020000
be2net 0000:30:00.1: Emulex OneConnect(be3): PF port 1
be2net 0000:30:04.0: enabling device (0140 -> 0142)
be2net 0000:30:04.0: Could not use PCIe error reporting
be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
be2net 0000:30:04.0: VF is not privileged to issue opcode 125-1
be2net 0000:30:04.0: irq 216 for MSI/MSI-X
be2net 0000:30:04.0: enabled 1 MSI-x vector(s)
be2net 0000:30:04.0: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:04.0: created 1 TX queue(s)
be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.0: Exhausted multicast HW filters.
be2net 0000:30:04.0: Disabling HW multicast filtering.
be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.0: Emulex OneConnect(be3): VF port 0
...
But the module gets loaded and VFs are created.
Also when the module is unloaded, below errors are seen in syslog:
be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
I checked the code, this error occurs in be_probe() and the error opcode
89 is OPCODE_COMMON_SET_INTERRUPT_ENABLE, which is essential for an
initializing process IMO. And I also found this thread
https://lkml.org/lkml/2013/5/14/690, which shows there is a bug that VFs
will be probed before PFs. According to this thread, I guess I may
encountered the same error.
Anyone can confirm if this is a real error like I guess? Thanks.
--
Regards,
Vaughan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: error message: VF is not privileged to issue opcode 89-1
2013-12-20 9:44 error message: VF is not privileged to issue opcode 89-1 vaughan
@ 2013-12-20 16:35 ` Greg Rose
2013-12-20 16:42 ` Ajit Khaparde
1 sibling, 0 replies; 4+ messages in thread
From: Greg Rose @ 2013-12-20 16:35 UTC (permalink / raw)
To: vaughan; +Cc: netdev
On Fri, 20 Dec 2013 17:44:51 +0800
vaughan <vaughan.cao@oracle.com> wrote:
> Hi experts,
>
> I encounter the following error when creating SR-IOV VF for Emulex
> 10GB nic on 3.8.13 kernel.
>
> # modprobe be2net num_vfs=4
> be2net 0000:30:00.0: irq 214 for MSI/MSI-X
> be2net 0000:30:00.0: enabled 1 MSI-x vector(s)
> be2net 0000:30:00.0: created 0 RSS queue(s) and 1 default RX queue
> be2net 0000:30:00.0: created 1 TX queue(s)
> pci 0000:30:04.0: [19a2:0710] type 00 class 0x020000
> pci 0000:30:04.1: [19a2:0710] type 00 class 0x020000
> pci 0000:30:04.2: [19a2:0710] type 00 class 0x020000
> pci 0000:30:04.3: [19a2:0710] type 00 class 0x020000
> be2net 0000:30:00.0: Emulex OneConnect(be3): PF port 0
> be2net 0000:30:00.1: irq 215 for MSI/MSI-X
> be2net 0000:30:00.1: enabled 1 MSI-x vector(s)
> be2net 0000:30:00.1: created 0 RSS queue(s) and 1 default RX queue
> be2net 0000:30:00.1: created 1 TX queue(s)
> pci 0000:30:06.0: [19a2:0710] type 00 class 0x020000
> pci 0000:30:06.1: [19a2:0710] type 00 class 0x020000
> pci 0000:30:06.2: [19a2:0710] type 00 class 0x020000
> pci 0000:30:06.3: [19a2:0710] type 00 class 0x020000
> be2net 0000:30:00.1: Emulex OneConnect(be3): PF port 1
> be2net 0000:30:04.0: enabling device (0140 -> 0142)
> be2net 0000:30:04.0: Could not use PCIe error reporting
> be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
> be2net 0000:30:04.0: VF is not privileged to issue opcode 125-1
> be2net 0000:30:04.0: irq 216 for MSI/MSI-X
> be2net 0000:30:04.0: enabled 1 MSI-x vector(s)
> be2net 0000:30:04.0: created 0 RSS queue(s) and 1 default RX queue
> be2net 0000:30:04.0: created 1 TX queue(s)
> be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
> be2net 0000:30:04.0: Exhausted multicast HW filters.
> be2net 0000:30:04.0: Disabling HW multicast filtering.
> be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
> be2net 0000:30:04.0: Emulex OneConnect(be3): VF port 0
> ...
>
> But the module gets loaded and VFs are created.
> Also when the module is unloaded, below errors are seen in syslog:
> be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
>
> I checked the code, this error occurs in be_probe() and the error
> opcode 89 is OPCODE_COMMON_SET_INTERRUPT_ENABLE, which is essential
> for an initializing process IMO. And I also found this thread
> https://lkml.org/lkml/2013/5/14/690, which shows there is a bug that
> VFs will be probed before PFs. According to this thread, I guess I may
> encountered the same error.
> Anyone can confirm if this is a real error like I guess? Thanks.
>
>
You might want to check the MAINTAINERS file and copy some of the folks
from emulex on this mail
SERVER ENGINES 10Gbps NIC - BladeEngine 2 DRIVER
M: Sathya Perla <sathya.perla@emulex.com>
M: Subbu Seetharaman <subbu.seetharaman@emulex.com>
M: Ajit Khaparde <ajit.khaparde@emulex.com>
L: netdev@vger.kernel.org
W: http://www.emulex.com
S: Supported
F: drivers/net/ethernet/emulex/benet/
Just a suggestion.
In answer to your question - yes, it is possible for a VF to be probed
before the PF. The drivers should handle that.
- Greg
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: error message: VF is not privileged to issue opcode 89-1
2013-12-20 9:44 error message: VF is not privileged to issue opcode 89-1 vaughan
2013-12-20 16:35 ` Greg Rose
@ 2013-12-20 16:42 ` Ajit Khaparde
2013-12-21 2:28 ` Vaughan Cao
1 sibling, 1 reply; 4+ messages in thread
From: Ajit Khaparde @ 2013-12-20 16:42 UTC (permalink / raw)
To: vaughan, netdev@vger.kernel.org
> be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
> be2net 0000:30:04.0: Emulex OneConnect(be3): VF port 0
> ...
>
> But the module gets loaded and VFs are created.
> Also when the module is unloaded, below errors are seen in syslog:
> be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
>
> I checked the code, this error occurs in be_probe() and the error opcode
> 89 is OPCODE_COMMON_SET_INTERRUPT_ENABLE, which is essential for an
> initializing process IMO. And I also found this thread
> https://lkml.org/lkml/2013/5/14/690, which shows there is a bug that VFs
> will be probed before PFs. According to this thread, I guess I may
> encountered the same error.
> Anyone can confirm if this is a real error like I guess? Thanks.
The VFs on Emulex devices are assigned limited privileges unlike PFs.
Due to this certain commands sent to the firmware end up a response as seen in the logs.
In most of the cases the log message is informational and does not really impact normal I/O operations.
But for this particular message pertaining to opcode 89, I will have to check with the firmware team as well.
We will get back to you on that.
Could you send the output of ethtool -i?
I am interested in the firmware version on the card.
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: error message: VF is not privileged to issue opcode 89-1
2013-12-20 16:42 ` Ajit Khaparde
@ 2013-12-21 2:28 ` Vaughan Cao
0 siblings, 0 replies; 4+ messages in thread
From: Vaughan Cao @ 2013-12-21 2:28 UTC (permalink / raw)
To: Ajit Khaparde, netdev@vger.kernel.org
On 2013年12月21日 00:42, Ajit Khaparde wrote:
>
>> be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
>> be2net 0000:30:04.0: Emulex OneConnect(be3): VF port 0
>> ...
>>
>> But the module gets loaded and VFs are created.
>> Also when the module is unloaded, below errors are seen in syslog:
>> be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
>>
>> I checked the code, this error occurs in be_probe() and the error opcode
>> 89 is OPCODE_COMMON_SET_INTERRUPT_ENABLE, which is essential for an
>> initializing process IMO. And I also found this thread
>> https://lkml.org/lkml/2013/5/14/690, which shows there is a bug that VFs
>> will be probed before PFs. According to this thread, I guess I may
>> encountered the same error.
>> Anyone can confirm if this is a real error like I guess? Thanks.
> The VFs on Emulex devices are assigned limited privileges unlike PFs.
> Due to this certain commands sent to the firmware end up a response as seen in the logs.
> In most of the cases the log message is informational and does not really impact normal I/O operations.
>
> But for this particular message pertaining to opcode 89, I will have to check with the firmware team as well.
> We will get back to you on that.
>
> Could you send the output of ethtool -i?
> I am interested in the firmware version on the card.
>
> Thanks
Hi Ajit,
Thanks for your explanation. What you requested is below:
# ethtool -i eth4
driver: be2net
version: 4.6.63.0u
firmware-version: 4.1.402.18
bus-info: 0000:30:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: no
# cat /sys/class/net/eth4/device/sriov_numvfs
4
# cat /sys/class/net/eth4/device/sriov_totalvfs
16
And Emulex card detail :
30:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3)
(rev 01)
30:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3)
(rev 01)
The whole message when creating SR-IOV VF is here, all VFs report
messages like that.
be2net 0000:30:00.0: irq 214 for MSI/MSI-X
be2net 0000:30:00.0: enabled 1 MSI-x vector(s)
be2net 0000:30:00.0: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:00.0: created 1 TX queue(s)
pci 0000:30:04.0: [19a2:0710] type 00 class 0x020000
pci 0000:30:04.1: [19a2:0710] type 00 class 0x020000
pci 0000:30:04.2: [19a2:0710] type 00 class 0x020000
pci 0000:30:04.3: [19a2:0710] type 00 class 0x020000
be2net 0000:30:00.0: Emulex OneConnect(be3): PF port 0
be2net 0000:30:00.1: irq 215 for MSI/MSI-X
be2net 0000:30:00.1: enabled 1 MSI-x vector(s)
be2net 0000:30:00.1: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:00.1: created 1 TX queue(s)
pci 0000:30:06.0: [19a2:0710] type 00 class 0x020000
pci 0000:30:06.1: [19a2:0710] type 00 class 0x020000
pci 0000:30:06.2: [19a2:0710] type 00 class 0x020000
pci 0000:30:06.3: [19a2:0710] type 00 class 0x020000
be2net 0000:30:00.1: Emulex OneConnect(be3): PF port 1
be2net 0000:30:04.0: enabling device (0140 -> 0142)
be2net 0000:30:04.0: Could not use PCIe error reporting
be2net 0000:30:04.0: VF is not privileged to issue opcode 89-1
be2net 0000:30:04.0: VF is not privileged to issue opcode 125-1
be2net 0000:30:04.0: irq 216 for MSI/MSI-X
be2net 0000:30:04.0: enabled 1 MSI-x vector(s)
be2net 0000:30:04.0: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:04.0: created 1 TX queue(s)
be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.0: Exhausted multicast HW filters.
be2net 0000:30:04.0: Disabling HW multicast filtering.
be2net 0000:30:04.0: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.0: Emulex OneConnect(be3): VF port 0
be2net 0000:30:04.1: enabling device (0140 -> 0142)
be2net 0000:30:04.1: Could not use PCIe error reporting
be2net 0000:30:04.1: VF is not privileged to issue opcode 89-1
be2net 0000:30:04.1: VF is not privileged to issue opcode 125-1
be2net 0000:30:04.1: irq 217 for MSI/MSI-X
be2net 0000:30:04.1: enabled 1 MSI-x vector(s)
be2net 0000:30:04.1: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:04.1: created 1 TX queue(s)
be2net 0000:30:04.1: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.1: Exhausted multicast HW filters.
be2net 0000:30:04.1: Disabling HW multicast filtering.
be2net 0000:30:04.1: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.1: Emulex OneConnect(be3): VF port 0
be2net 0000:30:04.2: enabling device (0140 -> 0142)
be2net 0000:30:04.2: Could not use PCIe error reporting
be2net 0000:30:04.2: VF is not privileged to issue opcode 89-1
be2net 0000:30:04.2: VF is not privileged to issue opcode 125-1
be2net 0000:30:04.2: irq 218 for MSI/MSI-X
be2net 0000:30:04.2: enabled 1 MSI-x vector(s)
be2net 0000:30:04.2: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:04.2: created 1 TX queue(s)
be2net 0000:30:04.2: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.2: Exhausted multicast HW filters.
be2net 0000:30:04.2: Disabling HW multicast filtering.
be2net 0000:30:04.2: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.2: Emulex OneConnect(be3): VF port 0
be2net 0000:30:04.3: enabling device (0140 -> 0142)
be2net 0000:30:04.3: Could not use PCIe error reporting
be2net 0000:30:04.3: VF is not privileged to issue opcode 89-1
be2net 0000:30:04.3: VF is not privileged to issue opcode 125-1
be2net 0000:30:04.3: irq 219 for MSI/MSI-X
be2net 0000:30:04.3: enabled 1 MSI-x vector(s)
be2net 0000:30:04.3: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:04.3: created 1 TX queue(s)
be2net 0000:30:04.3: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.3: Exhausted multicast HW filters.
be2net 0000:30:04.3: Disabling HW multicast filtering.
be2net 0000:30:04.3: VF is not privileged to issue opcode 34-1
be2net 0000:30:04.3: Emulex OneConnect(be3): VF port 0
be2net 0000:30:06.0: enabling device (0140 -> 0142)
be2net 0000:30:06.0: Could not use PCIe error reporting
be2net 0000:30:06.0: VF is not privileged to issue opcode 89-1
be2net 0000:30:06.0: VF is not privileged to issue opcode 125-1
be2net 0000:30:06.0: irq 220 for MSI/MSI-X
be2net 0000:30:06.0: enabled 1 MSI-x vector(s)
be2net 0000:30:06.0: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:06.0: created 1 TX queue(s)
be2net 0000:30:06.0: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.0: Exhausted multicast HW filters.
be2net 0000:30:06.0: Disabling HW multicast filtering.
be2net 0000:30:06.0: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.0: Emulex OneConnect(be3): VF port 1
be2net 0000:30:06.1: enabling device (0140 -> 0142)
be2net 0000:30:06.1: Could not use PCIe error reporting
be2net 0000:30:06.1: VF is not privileged to issue opcode 89-1
be2net 0000:30:06.1: VF is not privileged to issue opcode 125-1
be2net 0000:30:06.1: irq 221 for MSI/MSI-X
be2net 0000:30:06.1: enabled 1 MSI-x vector(s)
be2net 0000:30:06.1: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:06.1: created 1 TX queue(s)
be2net 0000:30:06.1: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.1: Exhausted multicast HW filters.
be2net 0000:30:06.1: Disabling HW multicast filtering.
be2net 0000:30:06.1: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.1: Emulex OneConnect(be3): VF port 1
be2net 0000:30:06.2: enabling device (0140 -> 0142)
be2net 0000:30:06.2: Could not use PCIe error reporting
be2net 0000:30:06.2: VF is not privileged to issue opcode 89-1
be2net 0000:30:06.2: VF is not privileged to issue opcode 125-1
be2net 0000:30:06.2: irq 222 for MSI/MSI-X
be2net 0000:30:06.2: enabled 1 MSI-x vector(s)
be2net 0000:30:06.2: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:06.2: created 1 TX queue(s)
be2net 0000:30:06.2: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.2: Exhausted multicast HW filters.
be2net 0000:30:06.2: Disabling HW multicast filtering.
be2net 0000:30:06.2: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.2: Emulex OneConnect(be3): VF port 1
be2net 0000:30:06.3: enabling device (0140 -> 0142)
be2net 0000:30:06.3: Could not use PCIe error reporting
be2net 0000:30:06.3: VF is not privileged to issue opcode 89-1
be2net 0000:30:06.3: VF is not privileged to issue opcode 125-1
be2net 0000:30:06.3: irq 223 for MSI/MSI-X
be2net 0000:30:06.3: enabled 1 MSI-x vector(s)
be2net 0000:30:06.3: created 0 RSS queue(s) and 1 default RX queue
be2net 0000:30:06.3: created 1 TX queue(s)
be2net 0000:30:06.3: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.3: Exhausted multicast HW filters.
be2net 0000:30:06.3: Disabling HW multicast filtering.
be2net 0000:30:06.3: VF is not privileged to issue opcode 34-1
be2net 0000:30:06.3: Emulex OneConnect(be3): VF port 1
Vaughan
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-12-21 2:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-20 9:44 error message: VF is not privileged to issue opcode 89-1 vaughan
2013-12-20 16:35 ` Greg Rose
2013-12-20 16:42 ` Ajit Khaparde
2013-12-21 2:28 ` Vaughan Cao
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).