Description of problem: Failed to bring back PF interface while guest OS running Version-Release number of selected component (if applicable): SR-IOV PF driver 1.3.16-k2 How reproducible: With at least one guest OS running, PF driver seems in malfunction when the network interface is brought down, then up. 1. ifdown eth1 2. ifconfig eth1 192.168.1.200 "SIOCSIFFLAGS: Cannot allocate memory" 3. From dmesg log, the error msg "igb 0000:01:00.0: Unable to allocate memory for the transmit descriptor ring igb 0000:01:00.0: Allocation for Tx Queue 0 failed" 4. From VF side, it complied " PF is in resetting" 5. if all guest OSes got killed, PF driver working again. Actual results: Failed Expected results: After the PF interface back. The VF should fuctional. Additional info:
Does this work correctly on a recent upstream kernel?
sli6 7/7/2009 11:09:47 AM The defect only ocurs on PF driver of RHEL5.4. I tested it on XEN3.4.1 with latest PF driver 1.3.28.1. The defect doesn't occur on the PF driver 1.3.28.1 on XEN 3.4.1. gvrose 7/14/2009 4:34:08 PM The bug is reproducible using Intel igb PF driver 1.3.30 and igbvf VF driver 1.0.2. Using these same drivers on Xen 3.4.1 the problem does not occur so this would indicate that the issue results from some interaction with the system that is unique to RHEL 5.4. As noted in the description its a fairly simple memory allocation problem. The driver requests DMA memory and the request fails.
The problem is reproduced on two systems, when only one VM with one VF is running. I tested on my system. When one VM with one VF is running, the defect can not be produced on this system. However after I create 14 VMs, then destroy a VM, after this, create a VM. If bring the PF interface down and up. The defect occurs. Here is the dmseg igb 0000:01:00.0: Unable to allocate memory for the transmit descriptor ring igb 0000:01:00.0: Allocation for Tx Queue 0 failed pciback: vpci: 0000:01:10.0: assign to virtual slot 0 igb 0000:01:00.0: Unable to allocate memory for the transmit descriptor ring igb 0000:01:00.0: Allocation for Tx Queue 0 failed
Sibai- I understand that this bug is not reproducible in RHEL 5.4 GA. Can you verify that this is the case and then we can close the bug.
The defect is fixed, close it