netdev - Re: error message: VF is not privileged to issue opcode 89-1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Dec 2013 08:35:21 -0800
From:	Greg Rose <gregory.v.rose@...el.com>
To:	vaughan <vaughan.cao@...cle.com>
CC:	<netdev@...r.kernel.org>
Subject: Re: error message: VF is not privileged to issue opcode 89-1

On Fri, 20 Dec 2013 17:44:51 +0800
vaughan <vaughan.cao@...cle.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@...lex.com>
M:      Subbu Seetharaman <subbu.seetharaman@...lex.com>
M:      Ajit Khaparde <ajit.khaparde@...lex.com>
L:      netdev@...r.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html