netdev - RE: ixgbe and SRIOV failure in driver?

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:	Mon, 24 May 2010 09:49:27 +0000
From:	"Fischer, Anna" <anna.fischer@...com>
To:	"Rose, Gregory V" <gregory.v.rose@...el.com>
CC:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: ixgbe and SRIOV failure in driver?

> Subject: RE: ixgbe and SRIOV failure in driver?
> 
> >-----Original Message-----
> >From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> >On Behalf Of Fischer, Anna
> >Sent: Friday, May 21, 2010 9:33 AM
> >To: e1000-devel@...ts.sourceforge.net; netdev@...r.kernel.org
> >Subject: ixgbe and SRIOV failure in driver?
> >
> >I am running a system with 3 Intel NICs. Two of them are 82598 devices,
> >and one is a SRIOV capable 82599.
> >
> >All devices use the ixgbe driver. What happens (I believe) now is that
> >when the driver loads at first, it sees the 82598 first (because of its
> >position in the PCI tree) and then it says "Device not IOV capable -
> >switching off IOV."
> >
> >So then it switches into non-IOV mode, and I can never enable SRIOV on
> >my 82599, because the driver does not enable it any more for further
> >devices.
> >
> >So to get around this issue, I tried to use pciback.hide to hide the
> >82598 devices from the OS. That way I was hoping that the driver would
> >switch on SRIOV on my 82599. However, then I got a kernel panic on boot
> >(see below).
> >
> >I am running Xen 4 and the Dom0 kernel is a 2.6.31 kernel.
> 
> The ixgbe driver included with the 2.6.31 kernel does not support SR-IOV.
> Where did you get the driver that does?  Please run ethtool -i <ethx>
> and
> post the results.

I have installed the driver separately on my pv-ops kernel.

[root@...052610-f-cpu ~]# ethtool -i eth
driver: ixgbe
version: 2.0.75.7-NAPI
firmware-version: 0.9-3
bus-info: 0000:05:00.0

I have attached a log on when the drivers loads. There is a bit more debugging information enabled. You can see that the driver loads at first on devices 0000:02:00.0 and 0000:02:00.1 which are 82598 devices and don't support SRIOV. So the driver switches off SRIOV. When it loads it on the 82599 which sits on 0000:05:00.0, it does not even have the SRIOV parameter enabled anymore, even though I load the driver with 'modprobe ixgbe max_vfs=4'.

Thanks,
Anna


Download attachment "ixgbe-error.log" of type "application/octet-stream" (4755 bytes)