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:	Wed, 1 Feb 2012 00:43:07 +0000
From:	"Rose, Gregory V" <gregory.v.rose@...el.com>
To:	David Ahern <daahern@...co.com>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: RE: VFs go missing with latest kernel

> -----Original Message-----
> From: David Ahern [mailto:daahern@...co.com]
> Sent: Tuesday, January 31, 2012 4:31 PM
> To: Rose, Gregory V
> Cc: LKML
> Subject: Re: VFs go missing with latest kernel
> 
> On 01/31/2012 03:58 PM, Rose, Gregory V wrote:
> >> I am hitting some other problem trying to use the VF on 3.3.0-rc1 --
> KVM
> >> fails the KVM_CAP_IOMMU check though the server has one (works fine
> with
> >> the older kernel) and it is built into the kernel. Debugging that
> >> problem now.
> 
> second problem was due to a CONFIG setting.
> 
> Back to the missing VF problem: reverting the patch I mentioned before
> and my VM boots up fine with the even-numbered VFs assigned to it.

OK, thanks... I was staring at the dmesg output you sent me and it is odd because the even numbered VFs that go missing are there when you set their MAC addresses.  See output below the dotted line after my reply.

Also, the dmesg output indicates 28 VFs are created but the lspci output you've sent only shows 14, even from the stock FC 14 kernel.  So even in that case you seem to be missing 14 VFs from the lspci output.

So they're there at one point but then disappear.  Very odd.  I'm finishing up a few other things but will try to repro ASAP and get back to you with my results.

- Greg

------------
[   81.432421] igb 0000:07:00.0: setting MAC 02:12:34:56:79:41 on VF 1
[   81.432550] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[   81.432667] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[   81.432942] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[   81.434947] igb 0000:07:00.0: setting MAC 02:12:34:56:79:42 on VF 2
[   81.435060] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[   81.435174] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[   81.435450] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[   81.437429] igb 0000:07:00.0: setting MAC 02:12:34:56:79:43 on VF 3
[   81.437555] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[   81.437670] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[   81.437937] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[   81.439904] igb 0000:07:00.0: setting MAC 02:12:34:56:79:44 on VF 4
[   81.440016] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[   81.440132] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[   81.440400] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[   81.442328] igb 0000:07:00.0: setting MAC 02:12:34:56:79:45 on VF 5
[   81.442453] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[   81.442567] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[   81.442837] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[   81.444921] igb 0000:07:00.0: setting MAC 02:12:34:56:79:46 on VF 6
[   81.445035] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[   81.445149] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[   81.445417] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
-------------------

> 
> David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ