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.

Bug 679514

Summary: qeth: remove needless IPA-commands in offline
Product: Red Hat Enterprise Linux 6 Reporter: Joseph Kachuck <jkachuck>
Component: kernelAssignee: Hendrik Brueckner <brueckner>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: arozansk, cward, dtian, jjarvis, peterm
Target Milestone: rcKeywords: OtherQA
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard:
Fixed In Version: kernel-2.6.32-130.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 12:14:38 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:    
Bug Blocks: 684385    
Attachments:
Description Flags
linux-2.6.32-s390-qeth-no-ipa-in-offline.patch none

Description Joseph Kachuck 2011-02-22 19:10:35 UTC
Created attachment 480214 [details]
linux-2.6.32-s390-qeth-no-ipa-in-offline.patch

linux-2.6.32-s390-qeth-no-ipa-in-offline.patch

Description: qeth: remove needless IPA-commands in offline
Symptom: slow or even hanging shutdown of qeth devices
Problem: If a qeth device is set offline, data and control
subchannels are cleared, which means removal of all
IP Assist Primitive settings implicitly. There is
no need to delete those settings explicitly.
Moreover shutdown of qeth devices may even hang
if hardware currently has a problem to handle those
IPA-commands.
Solution: This patch removes all IP Assist invocations from
offline.

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?
The patch has been sent upstream for inclusion into an -rc version.

What is the latest official Red Hat build on which this bug has been seen?
RHEL6.1 Alpha


The patch has been tested and fixes the problem.

With best regards,
Hendrik

Comment 1 Hendrik Brueckner 2011-03-07 10:14:46 UTC
The patch has been posted to rhkernel by Hendrik Brueckner <brueckner>

Comment 2 RHEL Program Management 2011-03-07 15:20:57 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 3 Joseph Kachuck 2011-03-10 15:22:24 UTC
=== In Red Hat Customer Portal Case 00426281 ===
--- Comment by IBM bug, proxy on 3/10/2011 9:16 AM ---

------- Comment From mgrf.com 2011-03-10 09:10 EDT-------
Hello Joe, John,

Please handle this via exception process for RHEL 6.1

Business justification:
====================
Symptom:
Significantly increased waiting times of several minutes up to
hangs with network device recoveries when certain HW issues
occur in parallel that should not have any impact to customers

Impact:
Customers observe unacceptable waiting times or even hangs
with network device recoveries that should be handled by the
system without customer impact.
This did not generate customer impact in the past but can be
significantly now with more complex (re-)configuration scenarios.
Especially because waiting times occur randomly (more or less impact) depending on possible parallel HW issues being handled.

Business Impact:
Customers will not accept waiting times up to 4 minutes and hangs
with network operations and experience the distribution as not usable
for production.
====================

Comment 4 John Jarvis 2011-03-18 13:22:30 UTC
IBM will test and provide feedback, setting OtherQA.

Comment 5 IBM Bug Proxy 2011-03-26 17:35:01 UTC
------- Comment From tpnoonan.com 2011-03-02 17:26 EDT-------
red hat, please consider under exception process

Comment 6 John Jarvis 2011-03-30 21:03:29 UTC
This fix is planned for inclusion in snapshot 3

Comment 7 Aristeu Rozanski 2011-04-07 14:14:16 UTC
Patch(es) available on kernel-2.6.32-130.el6

Comment 10 Chris Ward 2011-05-06 11:41:22 UTC
@IBM, test results?

Comment 11 errata-xmlrpc 2011-05-19 12:14:38 UTC
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