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.
Created attachment 479157[details]
linux-2.6.32-s390-qeth-chpath-change.patch
linux-2.6.32-s390-qeth-chpath-change.patch
Description: qeth: allow channel path changes in suspend state
Symptom: qeth device does not recover successfully during resume
Problem: Channel path information is determined only when qeth
device is grouped. In order to recognize channel path
changes at resume time, channel path information has to
be re-determined during online setting.
One possible change is the number of OSA-supported TCP/IP
stacks determining the number of available outbound
queues. Switching them from 480 to 1920 while being
suspended results in failing recovery when resuming.
Solution: Determine channel path capabilities during online
setting of the device and reestablish outbound qdio
queues during recovery in case the number of
OSA-supported TCP/IP stacks has changed.
Server architecture(s): System z
Server type: s390x
General component: kernel
Other components involved: No
Does the server have the latest GA firmware?
Yes.
Has the problem been shown to occur on more than one system?
Yes.
Is a tested patch available?
Yes.
If yes to the above, has it been approved upstream?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-
2.6.git;a=commitdiff;h=d0ff1f52361d714863c49abb721a8714ea4e76d6
What is the latest official Red Hat build on which this bug has been seen?
RHEL6
The patch has been tested, fixes the problem, and is part of the upstream
kernel.
With best regards,
Hendrik
Comment 2Hendrik Brueckner
2011-03-07 10:15:10 UTC
The patch has been posted to rhkernel by Hendrik Brueckner <brueckner>
Comment 3RHEL Program Management
2011-03-07 15:21:20 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
------- Comment From brueckner.ibm.com 2011-02-16 12:00 EDT-------
(In reply to comment #6)
> I have sent this up for engineering to review.
Please let me know the RHBZ.
Thanks.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0542.html