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 1025213 - 82599 PF not work properly after S3
Summary: 82599 PF not work properly after S3
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Bandan Das
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: Virt-S3/S4-7.0
TreeView+ depends on / blocked
 
Reported: 2013-10-31 09:24 UTC by Xu Han
Modified: 2015-03-04 05:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-04 05:37:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Dmesg (5.88 KB, text/plain)
2013-10-31 09:27 UTC, Xu Han 		no flags Details
View All

Description Xu Han 2013-10-31 09:24:37 UTC 
Description of problem:
82599 PF not work properly after S3.
Not very sure if it is a kernel issue, because host not support S3 and fail to test.
# lspci | grep 82599
05:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)


Version-Release number of selected component (if applicable):
kernel-3.10.0-40.el7.x86_64
qemu-kvm-rhev-1.5.3-10.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot guest with 82599 PF via vfio
# /usr/libexec/qemu-kvm -nodefaults -M pc -m 4G -cpu Nehalem -smp 4,cores=2,threads=2,sockets=1 -boot menu=on -monitor stdio -vga qxl -spice disable-ticketing,port=5932 -drive file=/home/vfio-RHEL7.0-64-1.qcow2_v3,id=guest-img,if=none,cache=none,aio=native -device virtio-blk-pci,scsi=off,drive=guest-img,id=os-disk,bootindex=1 -device virtio-balloon-pci,id=balloon -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -qmp tcp:0:5556,server,nowait -serial unix:/tmp/guest-sock-1,server,nowait -monitor unix:/tmp/vfio-hotplug-1,server,nowait \
-device vfio-pci,host=05:00.0,id=pf0

2. do S3 on guest.

3. resume guest.

Actual results:
After guest resumed, PF not work properly and have failure in dmesg (in attachment).

Expected results:
After resume from S3, PF still work properly.

Additional info:
Test with VF hit other issue.
Comment 1 Xu Han 2013-10-31 09:27:34 UTC 
Created attachment 817772 [details]
Dmesg
Comment 3 Alex Williamson 2013-10-31 12:23:45 UTC 
(In reply to xuhan from comment #0)
> Description of problem:
> 82599 PF not work properly after S3.
> Not very sure if it is a kernel issue, because host not support S3 and fail
> to test.

This is exactly the issue with S3 on server class assigned devices.  There is zero precedent that the drivers work.
Note You need to log in before you can comment on or make changes to this bug.