RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 845398 - igb's VF existence check is broken
Summary: igb's VF existence check is broken
Keywords:
Status: CLOSED DUPLICATE of bug 819102
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.3
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Stefan Assmann
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 845399
TreeView+ depends on / blocked
 
Reported: 2012-08-02 23:41 UTC by Don Dutile (Red Hat)
Modified: 2012-09-21 06:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 845399 (view as bug list)
Environment:
Last Closed: 2012-09-21 06:53:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Don Dutile (Red Hat) 2012-08-02 23:41:33 UTC 
Description of problem:
When igb's Physical Function(PF) probe is executed and it's SRIOV functionality is enabled, it does a check to see if VF devices already exist in the system due to a previous driver load/unload with VFs enabled.  The existence check is incorrect, and can erroneously match on VFs that are attached to other ixgbe PFs, and not the VF associated with the probe'd PF.

Version-Release number of selected component (if applicable):


How reproducible:
Always with multiple igb's in different PCI busses, but same PCI slot numbers, e.g. igb at 07:00.0, igb at 04:00.0

Steps to Reproduce:
1. Boot system
2. rmmod igb; modprobe igb max_vfs=2
3. 
  
Actual results:
VFs associated with second igb won't configure in, since the VF-matching check will match the first PF's VFs as being the second PF's VFs, incorrectly.

Expected results:
All VFs configure and work.

Additional info:
Intel is testing a patch provided by Stefan Assmann.
It is similar in form to the following patch for ixgbe:
Need to backport this upstream commit to rhel6.3:
commit 9297127b9cdd8d30c829ef5fd28b7cc0323a7bcd
Author: Alexander Duyck <alexander.h.duyck>
Date:   Wed May 23 02:58:40 2012 +0000

    ixgbe: Change how we check for pre-existing and assigned VFsDescription of problem:


Upstream igb is broken as well, and the patch Stefan provided will be pushed to upstream if testing shows positive results.
Comment 2 Stefan Assmann 2012-09-21 06:53:28 UTC 

*** This bug has been marked as a duplicate of bug 819102 ***
Note You need to log in before you can comment on or make changes to this bug.