Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to comment #2)
> Does the VF work in the guest? What happens with pci-assign?
I rem VF works in guest.
This issue is not easy to reproduce. So far, even with vfio-pci, I haven't successfully reproduced yet.
(In reply to Alex Williamson from comment #4)
> Can this be reproduced on current bits? If not, let's close it.
No, cannot reproduce with 3.10.0-55.el7.x86_64, qemu-kvm-1.5.3-19.el7.x86_64
Created attachment 709877 [details] host /var/log/message Description of problem: Assigned 82599 VF to guest through vfio-pci, "Detected Tx Unit Hang" message was flooding. Version-Release number of selected component (if applicable): 3.8.0-0.40.el7.x86_64 qemu-kvm-1.4.0-1.el7.x86_64 # modinfo ixgbe filename: /lib/modules/3.8.0-0.40.el7.x86_64/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version: 3.11.33-k license: GPL description: Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, <linux.nics> How reproducible: 1/1 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: # /usr/libexec/qemu-kvm -name SR-IOV -M pc-i440fx-1.4 -cpu Nehalem -enable-kvm -m 4096 -smp 4,sockets=4,cores=1,threads=1 -uuid 8caf1895-52ef-4231-e4ec-73171b8b265b -nodefaults -rtc base=utc -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/root/sriov.raw,if=none,id=drive-scsi0-0-0,format=raw -device scsi-hd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6c:08:46,bus=pci.0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -balloon none -device vfio-pci,host=09:00.0,id=emulex_pf -device vfio-pci,host=06:1f.4,id=intel82599_vf [75112.838431] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 47 [75113.702158] ixgbe 0000:06:00.0 p4p1: Detected Tx Unit Hang Tx Queue <0> TDH, TDT <0>, <6> next_to_use <6> next_to_clean <0> tx_buffer_info[next_to_clean] time_stamp <1047788b2> jiffies <10477941c> [75113.778127] ixgbe 0000:06:00.0 p4p1: tx hang 606 detected on queue 0, resetting adapter [75113.784111] ixgbe 0000:06:00.0 p4p1: Reset adapter [75113.794150] ixgbe 0000:06:00.0 p4p1: RXDCTL.ENABLE on Rx queue 126 not cleared within the polling period [75113.986876] ixgbe 0000:06:00.0: master disable timed out [75115.997979] ixgbe 0000:06:00.0 p4p1: RXDCTL.ENABLE on Rx queue 126 not cleared within the polling period [75116.178394] ixgbe 0000:06:00.0 p4p1: detected SFP+: 5 [75116.531784] ixgbe 0000:06:00.0 p4p1: NIC Link is Up 10 Gbps, Flow Control: RX/TX [75116.557016] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 19 [75116.567936] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 25 [75116.579988] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 50 [75116.589092] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 0 [75116.603050] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 3 [75116.611374] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 6 [75116.629053] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 23 [75116.643055] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 32 [75116.651496] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 49 [75116.666588] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 13 [75116.676914] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 9 [75116.691705] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 37 [75116.706091] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 38 [75116.715836] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 11 [75116.728100] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 8 [75116.744065] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 40 [75116.752526] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 46 [75116.766381] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 15 [75116.777303] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 20 [75116.789801] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 48 [75116.804651] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 26 [75116.813361] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 54 [75116.826317] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 21 [75116.839305] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 61 [75116.848649] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 44 [75116.863787] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 28 [75116.873157] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 2 [75116.890579] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 12 [75116.904635] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 27 [75116.916916] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 19 [75116.929990] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 51 [75116.946567] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 12 [75118.803948] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 41 [75118.827938] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 47 [75119.846102] ixgbe 0000:06:00.0 p4p1: VF Reset msg received from vf 17 [75120.617826] ixgbe 0000:06:00.0 p4p1: Detected Tx Unit Hang Tx Queue <0> TDH, TDT <0>, <6> next_to_use <6> next_to_clean <0> tx_buffer_info[next_to_clean] time_stamp <10477a150> jiffies <10477af2c> [75120.699441] ixgbe 0000:06:00.0 p4p1: tx hang 607 detected on queue 0, resetting adapter ....