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 652213

Summary: change igb max_vfs with wrong message
Product: Red Hat Enterprise Linux 5 Reporter: Hangbin Liu <haliu>
Component: kernelAssignee: Stefan Assmann <sassmann>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 5.6CC: ddutile, jarod, prarit
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-29 08:59: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:
Bug Depends On: 645284    
Bug Blocks:    

Description Hangbin Liu 2010-11-11 11:53:23 UTC
Description of problem:

while testing bug #645284 , change igb max_vfs on intel-s3eb1-01.rhts.eng.bos.redhat.com , but get a wrong message

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

[root@intel-s3eb1-01 ~]# uname -r
2.6.18-227.el5PAE 

[root@hp-dl2x170g6-01 ~]# lspci | grep 82576
05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection
(rev 01)
05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection
(rev 01)


How reproducible:

N/A

Steps to Reproduce:
1. modprobe -r igb;modprobe igb max_vfs=10
2.
3.
  
Actual results:

[root@intel-s3eb1-01 ~]# modprobe -r igb;modprobe igb max_vfs=10
dca service started, version 1.8
PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
PCI: Enabling device 0000:01:00.1 (0000 -> 0002)
PCI: Enabling device 0000:01:10.0 (0000 -> 0002)
[root@intel-s3eb1-01 ~]# igbvf 0000:01:10.0: PF still resetting
PCI: Enabling device 0000:01:10.2 (0000 -> 0002)
igbvf 0000:01:10.2: PF still resetting
PCI: Enabling device 0000:01:10.4 (0000 -> 0002)
igbvf 0000:01:10.4: PF still resetting
PCI: Enabling device 0000:01:10.6 (0000 -> 0002)
PCI: Enabling device 0000:01:11.0 (0000 -> 0002)
PCI: Enabling device 0000:01:11.2 (0000 -> 0002)
PCI: Enabling device 0000:01:11.4 (0000 -> 0002)
PCI: Enabling device 0000:01:10.1 (0000 -> 0002)
igbvf 0000:01:10.1: PF still resetting
PCI: Enabling device 0000:01:10.3 (0000 -> 0002)
igbvf 0000:01:10.3: PF still resetting
PCI: Enabling device 0000:01:10.5 (0000 -> 0002)
igbvf 0000:01:10.5: PF still resetting
PCI: Enabling device 0000:01:10.7 (0000 -> 0002)
igbvf 0000:01:10.7: PF still resetting
PCI: Enabling device 0000:01:11.1 (0000 -> 0002)
igbvf 0000:01:11.1: PF still resetting
PCI: Enabling device 0000:01:11.3 (0000 -> 0002)
igbvf 0000:01:11.3: PF still resetting
PCI: Enabling device 0000:01:11.5 (0000 -> 0002)
igbvf 0000:01:11.5: PF still resetting
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <9>
  next_to_use          <9>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <fffe817d>
  next_to_watch        <0>
  jiffies              <fffe8bc1>
  desc.status          <168000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <9>
  next_to_use          <9>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <fffe817d>
  next_to_watch        <0>
  jiffies              <fffe9390>
  desc.status          <168000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <9>
  next_to_use          <9>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <fffe817d>
  next_to_watch        <0>
  jiffies              <fffe9b60>
  desc.status          <168000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <9>
  next_to_use          <9>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <fffe817d>
  next_to_watch        <0>
  jiffies              <fffea330>
  desc.status          <168000>
eth0: igb_reset_task: Reset adapter


Expected results:

[root@intel-s3eb1-01 ~]# modprobe -r igb;modprobe igb max_vfs=10
dca service started, version 1.8
PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
PCI: Enabling device 0000:01:10.0 (0000 -> 0002)
igbvf 0000:01:10.0: PF still resetting
PCI: Enabling device 0000:01:10.2 (0000 -> 0002)
igbvf 0000:01:10.2: PF still resetting
PCI: Enabling device 0000:01:10.4 (0000 -> 0002)
igbvf 0000:01:10.4: PF still resetting
PCI: Enabling device 0000:01:10.6 (0000 -> 0002)
igbvf 0000:01:10.6: PF still resetting
PCI: Enabling device 0000:01:11.0 (0000 -> 0002)
igbvf 0000:01:11.0: PF still resetting
PCI: Enabling device 0000:01:11.2 (0000 -> 0002)
igbvf 0000:01:11.2: PF still resetting
PCI: Enabling device 0000:01:11.4 (0000 -> 0002)
igbvf 0000:01:11.4: PF still resetting
PCI: Enabling device 0000:01:00.1 (0000 -> 0002)
PCI: Enabling device 0000:01:10.1 (0000 -> 0002)
igbvf 0000:01:10.1: PF still resetting
PCI: Enabling device 0000:01:10.3 (0000 -> 0002)
igbvf 0000:01:10.3: PF still resetting
PCI: Enabling device 0000:01:10.5 (0000 -> 0002)
igbvf 0000:01:10.5: PF still resetting
PCI: Enabling device 0000:01:10.7 (0000 -> 0002)
igbvf 0000:01:10.7: PF still resetting
PCI: Enabling device 0000:01:11.1 (0000 -> 0002)
igbvf 0000:01:11.1: PF still resetting
PCI: Enabling device 0000:01:11.3 (0000 -> 0002)
igbvf 0000:01:11.3: PF still resetting
PCI: Enabling device 0000:01:11.5 (0000 -> 0002)
igbvf 0000:01:11.5: PF still resetting

Additional info:

I can't reproduce it later . just came out once.

Comment 1 Stefan Assmann 2010-11-15 12:05:11 UTC
I tried to reproduce this 10x on intel-s3eb1-01 (i386) and it works as expected. Closing this bug, please reopen if you're seeing it again.

Comment 2 Hangbin Liu 2010-11-29 05:58:22 UTC
saw it again

[root@intel-sunriseridge-01 ~]# uname -a
Linux intel-sunriseridge-01.lab.bos.redhat.com 2.6.18-227.el5 #1 SMP Tue Oct 12 18:50:50 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@intel-sunriseridge-01 ~]# lspci | grep 82576
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
02:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
[root@intel-sunriseridge-01 ~]# modprobe -r igb
[root@intel-sunriseridge-01 ~]# modprobe igb max_vfs=32
dca service started, version 1.8
PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
PCI: Enabling device 0000:01:00.1 (0000 -> 0002)
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
PCI: Enabling device 0000:02:00.1 (0000 -> 0002)
PCI: Enabling device 0000:01:10.0 (0000 -> 0002)
[root@intel-sunriseridge-01 ~]# PCI: Enabling device 0000:01:10.2 (0000 -> 0002)
PCI: Enabling device 0000:01:10.4 (0000 -> 0002)
PCI: Enabling device 0000:01:10.6 (0000 -> 0002)
PCI: Enabling device 0000:01:11.0 (0000 -> 0002)
PCI: Enabling device 0000:01:11.2 (0000 -> 0002)
PCI: Enabling device 0000:01:11.4 (0000 -> 0002)
PCI: Enabling device 0000:01:10.1 (0000 -> 0002)
igbvf 0000:01:10.1: PF still resetting
PCI: Enabling device 0000:01:10.3 (0000 -> 0002)
igbvf 0000:01:10.3: PF still resetting
PCI: Enabling device 0000:01:10.5 (0000 -> 0002)
igbvf 0000:01:10.5: PF still resetting
PCI: Enabling device 0000:01:10.7 (0000 -> 0002)
igbvf 0000:01:10.7: PF still resetting
PCI: Enabling device 0000:01:11.1 (0000 -> 0002)
igbvf 0000:01:11.1: PF still resetting
PCI: Enabling device 0000:01:11.3 (0000 -> 0002)
igbvf 0000:01:11.3: PF still resetting
PCI: Enabling device 0000:01:11.5 (0000 -> 0002)
igbvf 0000:01:11.5: PF still resetting
PCI: Enabling device 0000:02:10.0 (0000 -> 0002)
igbvf 0000:02:10.0: PF still resetting
PCI: Enabling device 0000:02:10.2 (0000 -> 0002)
igbvf 0000:02:10.2: PF still resetting
PCI: Enabling device 0000:02:10.4 (0000 -> 0002)
igbvf 0000:02:10.4: PF still resetting
PCI: Enabling device 0000:02:10.6 (0000 -> 0002)
igbvf 0000:02:10.6: PF still resetting
PCI: Enabling device 0000:02:11.0 (0000 -> 0002)
igbvf 0000:02:11.0: PF still resetting
PCI: Enabling device 0000:02:11.2 (0000 -> 0002)
igbvf 0000:02:11.2: PF still resetting
PCI: Enabling device 0000:02:11.4 (0000 -> 0002)
igbvf 0000:02:11.4: PF still resetting
PCI: Enabling device 0000:02:10.1 (0000 -> 0002)
igbvf 0000:02:10.1: PF still resetting
PCI: Enabling device 0000:02:10.3 (0000 -> 0002)
igbvf 0000:02:10.3: PF still resetting
PCI: Enabling device 0000:02:10.5 (0000 -> 0002)
igbvf 0000:02:10.5: PF still resetting
PCI: Enabling device 0000:02:10.7 (0000 -> 0002)
igbvf 0000:02:10.7: PF still resetting
PCI: Enabling device 0000:02:11.1 (0000 -> 0002)
igbvf 0000:02:11.1: PF still resetting
PCI: Enabling device 0000:02:11.3 (0000 -> 0002)
igbvf 0000:02:11.3: PF still resetting
PCI: Enabling device 0000:02:11.5 (0000 -> 0002)
igbvf 0000:02:11.5: Failed to initialize MSI-X interrupts.
igbvf 0000:02:11.5: PF still resetting
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <a>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003f822b>
  next_to_watch        <0>
  jiffies              <1003f8c61>
  desc.status          <168000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <a>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003f822b>
  next_to_watch        <0>
  jiffies              <1003f9430>
  desc.status          <168000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <a>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003f822b>
  next_to_watch        <0>
  jiffies              <1003f9c00>
  desc.status          <168000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <a>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003f822b>
  next_to_watch        <0>
  jiffies              <1003fa3d0>
  desc.status          <168000>
eth0: igb_reset_task: Reset adapter
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <1>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003fbdf1>
  next_to_watch        <0>
  jiffies              <1003fc6f8>
  desc.status          <558000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <1>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003fbdf1>
  next_to_watch        <0>
  jiffies              <1003fcec9>
  desc.status          <558000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <1>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003fbdf1>
  next_to_watch        <0>
  jiffies              <1003fd698>
  desc.status          <558000>
eth0: igb_reset_task: Reset adapter
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <1>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003ff889>
  next_to_watch        <0>
  jiffies              <1004000d4>
  desc.status          <558000>
igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <1>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <1003ff889>
  next_to_watch        <0>
  jiffies              <1004008a3>
  desc.status          <558000>
eth0: igb_reset_task: Reset adapter



[root@intel-sunriseridge-01 ~]# lspci | grep 82576
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
01:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
01:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
02:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
02:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
02:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
[root@intel-sunriseridge-01 ~]# modprobe -r igb;modprobe igb max_vfs=10
dca service started, version 1.8
PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
PCI: Enabling device 0000:01:10.0 (0000 -> 0002)
igbvf 0000:01:10.0: PF still resetting
PCI: Enabling device 0000:01:10.2 (0000 -> 0002)
igbvf 0000:01:10.2: PF still resetting
PCI: Enabling device 0000:01:10.4 (0000 -> 0002)
igbvf 0000:01:10.4: PF still resetting
PCI: Enabling device 0000:01:10.6 (0000 -> 0002)
igbvf 0000:01:10.6: PF still resetting
PCI: Enabling device 0000:01:11.0 (0000 -> 0002)
igbvf 0000:01:11.0: PF still resetting
PCI: Enabling device 0000:01:11.2 (0000 -> 0002)
igbvf 0000:01:11.2: PF still resetting
PCI: Enabling device 0000:01:11.4 (0000 -> 0002)
igbvf 0000:01:11.4: PF still resetting
PCI: Enabling device 0000:01:00.1 (0000 -> 0002)
PCI: Enabling device 0000:01:10.1 (0000 -> 0002)
igbvf 0000:01:10.1: PF still resetting
PCI: Enabling device 0000:01:10.3 (0000 -> 0002)
igbvf 0000:01:10.3: PF still resetting
PCI: Enabling device 0000:01:10.5 (0000 -> 0002)
igbvf 0000:01:10.5: PF still resetting
PCI: Enabling device 0000:01:10.7 (0000 -> 0002)
igbvf 0000:01:10.7: PF still resetting
PCI: Enabling device 0000:01:11.1 (0000 -> 0002)
igbvf 0000:01:11.1: PF still resetting
PCI: Enabling device 0000:01:11.3 (0000 -> 0002)
igbvf 0000:01:11.3: PF still resetting
PCI: Enabling device 0000:01:11.5 (0000 -> 0002)
igbvf 0000:01:11.5: PF still resetting
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
PCI: Enabling device 0000:02:10.0 (0000 -> 0002)
igbvf 0000:02:10.0: PF still resetting
PCI: Enabling device 0000:02:10.2 (0000 -> 0002)
igbvf 0000:02:10.2: PF still resetting
PCI: Enabling device 0000:02:10.4 (0000 -> 0002)
igbvf 0000:02:10.4: PF still resetting
PCI: Enabling device 0000:02:10.6 (0000 -> 0002)
igbvf 0000:02:10.6: PF still resetting
PCI: Enabling device 0000:02:11.0 (0000 -> 0002)
igbvf 0000:02:11.0: PF still resetting
PCI: Enabling device 0000:02:11.2 (0000 -> 0002)
igbvf 0000:02:11.2: PF still resetting
PCI: Enabling device 0000:02:11.4 (0000 -> 0002)
igbvf 0000:02:11.4: PF still resetting
PCI: Enabling device 0000:02:00.1 (0000 -> 0002)
PCI: Enabling device 0000:02:10.1 (0000 -> 0002)
igbvf 0000:02:10.1: PF still resetting
PCI: Enabling device 0000:02:10.3 (0000 -> 0002)
igbvf 0000:02:10.3: PF still resetting
PCI: Enabling device 0000:02:10.5 (0000 -> 0002)
igbvf 0000:02:10.5: PF still resetting
PCI: Enabling device 0000:02:10.7 (0000 -> 0002)
igbvf 0000:02:10.7: PF still resetting
PCI: Enabling device 0000:02:11.1 (0000 -> 0002)
igbvf 0000:02:11.1: PF still resetting
PCI: Enabling device 0000:02:11.3 (0000 -> 0002)
igbvf 0000:02:11.3: PF still resetting
PCI: Enabling device 0000:02:11.5 (0000 -> 0002)
igbvf 0000:02:11.5: Failed to initialize MSI-X interrupts.
igbvf 0000:02:11.5: PF still resetting


when set the igb max_vfs number > NR_ETH*7 , there will be messages like

igb 0000:01:00.0: Detected Tx Unit Hang
  Tx Queue             <0>
  TDH                  <0>
  TDT                  <0>
  next_to_use          <9>
  next_to_clean        <0>
buffer_info[next_to_clean]
  time_stamp           <10051e6d3>
  next_to_watch        <0>
  jiffies              <10051f738>
  desc.status          <168000>

Comment 4 Stefan Assmann 2010-11-29 08:59:47 UTC
You're using kernel -227 which is a bit old. You should always verify that the problem still exists with the latest released kernel.
This problem is fixed in kernel -229 (b7c36c6c7c243b23410d763cc4fc9a0a34889a72). That's why I couldn't reproduce it last time.