Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 665336

Summary: ixgbe driver fails due to unavailability of MMIO resource.
Product: Red Hat Enterprise Linux 5 Reporter: srinivas gowda <srinivas_g_gowda>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 5.6CC: agospoda, chrisw, linux-bugs, narayanan_d
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-07 15:17:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg
none
lspci -vvv
none
lspci -t none

Description srinivas gowda 2010-12-23 10:37:21 UTC 
Description of problem:

The ixgbe driver reports error when driver is loaded with parameter max_vfs=1 
Original source  -  Bug 566027. 
 

Steps to Reproduce:
1.Install RHEL5.6 on  a blade server having Intel82599 Ethernet Card( SRIOV )
2. Load the ixgbe module with parameter max_vfs=1.
3. Check the dmesg for error - 
ixgbe 0000:07:00.1: not enough MMIO resources for SR-IOV
ixgbe: 0000:07:00.1: ixgbe_probe_vf: Failed to enable PCI sriov: -12

  
Actual results:
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.84-k2
ixgbe: Copyright (c) 1999-2010 Intel Corporation.
PCI: Enabling device 0000:07:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:07:00.0[B] -> GSI 50 (level, low) -> IRQ 146
PCI: Setting latency timer of device 0000:07:00.0 to 64
ixgbe 0000:07:00.0: not enough MMIO resources for SR-IOV
ixgbe: 0000:07:00.0: ixgbe_probe_vf: Failed to enable PCI sriov: -12
ixgbe: 0000:07:00.0: ixgbe_init_interrupt_scheme: Multiqueue Enabled: Rx Queue count = 24, Tx Queue count = 24
ixgbe: 0000:07:00.0: ixgbe_probe: (PCI Express:5.0Gb/s:Width x8) 00:1b:21:6b:bc:90
ixgbe: 0000:07:00.0: ixgbe_probe: MAC: 2, PHY: 0, PBA No: e90209-006
ixgbe: eth0: ixgbe_probe: Intel(R) 10 Gigabit Network Connection
PCI: Enabling device 0000:07:00.1 (0000 -> 0002)
ACPI: PCI Interrupt 0000:07:00.1[A] -> GSI 40 (level, low) -> IRQ 163
PCI: Setting latency timer of device 0000:07:00.1 to 64
ixgbe 0000:07:00.1: not enough MMIO resources for SR-IOV
ixgbe: 0000:07:00.1: ixgbe_probe_vf: Failed to enable PCI sriov: -12
ixgbe: 0000:07:00.1: ixgbe_init_interrupt_scheme: Multiqueue Enabled: Rx Queue count = 24, Tx Queue count = 24
ixgbe: 0000:07:00.1: ixgbe_probe: (PCI Express:5.0Gb/s:Width x8) 00:1b:21:6b:bc:92
ixgbe: 0000:07:00.1: ixgbe_probe: MAC: 2, PHY: 0, PBA No: e90209-006
ixgbe: eth1: ixgbe_probe: Intel(R) 10 Gigabit Network Connection

Expected results:
Once the module is loaded as `modprobe ixgbe max_vfs=1` 
A new virtual interface should be created for each physical interface.
Comment 1 Narayanan D 2010-12-23 10:42:36 UTC 
This issue is raised based on Andy Gospodarek's comments in BZ566027
Comment 2 srinivas gowda 2010-12-23 10:45:02 UTC 
Created attachment 470399 [details]
dmesg

dmesg
Comment 3 srinivas gowda 2010-12-23 10:45:51 UTC 
Created attachment 470400 [details]
lspci -vvv

lspci -vvv
Comment 4 srinivas gowda 2010-12-23 10:46:55 UTC 
Created attachment 470401 [details]
lspci -t

lspci -t
Comment 5 srinivas gowda 2010-12-23 10:48:32 UTC 
Please find the dmesg (attachment 470399 [details]), lspci -vvv (attachment 470400 [details]) and lspci -t (attachment 470401 [details]) logs attached.
Comment 6 Prarit Bhargava 2011-01-07 15:17:47 UTC 

*** This bug has been marked as a duplicate of bug 665355 ***
Comment 7 Prarit Bhargava 2011-01-07 19:36:42 UTC 

*** This bug has been marked as a duplicate of bug 665335 ***
Comment 8 Prarit Bhargava 2011-01-07 19:37:16 UTC 
Fat fingered the dup BZ #.

Oops.  Sorry about that.

P.