Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

2008-05-07 kernel 2.6.16 bug fix patch 22 ("October 2005")

If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.

linux-2.6.16-s390-22-october2005.tar.gz / MD5 ... accumulated patch, recommended (2008-05-07)

linux-2.6.16-s390-22-october2005-patches.tar.gz / MD5 ... per-problem-patches, recommended (2008-05-07)

This patch contains the following linux kernel bug fixes:

Description:
dasd: Add 'failfast' device feature.
Symptom:
md-raid1 can not operate and manage md array, when no path is operational.
Problem:
md-raid1 does not set the FAILFAST flag, because that would break SCSI functionality due to ambiguous meaning of the flag.
Solution:
Add a new dasd feature 'failfast' which controls the dasd driver handling of requests and can be configured per device independently of the setting of the FAILFAST flag per request.
If the 'failfast' feature is enabled for a device, the dasd driver will handle requests as if the request had the FAILFAST flag set, particularly posting I/O failure, when no path is operational to the device.
The 'failfast' feature can be configured via the new sysfs attribute 'failfast' or via the 'dasd=' parameter, just like any other feature. By default, the 'failfast' feature is not set.
Problem-ID:
43066
Description:
qdio: Undetected inbound traffic with many online FCP devices.
Symptom:
zfcp host/bus re-set because of problems with unit (LPAR).
Problem:
Usually every FCP device has its own indicator field which the adapter uses to signal outstanding work. Once a certain limit of devices is reached, a common indicator field is used. In certain scenarios qdio re-sets this common indicator field, but handles only part of the FCP-devices sharing the common indicator field. Thus inbound traffic on the non-processed shared FCP-devices is not recognized immediately.
Solution:
Make sure common indicator field is re-set only, if all FCP-devices sharing the indicator are processed.
Problem-ID:
44083
Description:
qeth: CCL-sequence numbers created for non-802.2 packets.
Symptom:
Slow CCL response time.
Problem:
An 802.2-protocol check for CCL sequence numbers is missing (CCL: Communication Controller for Linux on System z).
Solution:
Add missing 802.2-protocol check before manipulating CCL sequence numbers.
Problem-ID:
-
Description:
qeth: Avoid inconsistent lock state for inet6_dev->lock.
Symptom:
qeth recovery hang was observed, but other problems may have been possible.
Problem:
ipv6_regen_rndid in net/ipv6/addrconf.c makes use of "write_lock_bh" for its inet6_dev->lock. It may run in softirq-context. qeth makes use of "read_lock" for the same inet_dev->lock. This can cause a deadlock.
Solution:
Use read_lock_bh to get inet6_dev->lock.
Problem-ID:
44102
Description:
qeth: eddp skb buff problem running EDDP guestlan.
Symptom:
Kernel panic.
Problem:
Wrong skb buffer size calculation.
Solution:
Corrected buffer size calculation.
Problem-ID:
43200

Everybody should apply this patch.

To create the complete linux kernel sources, the following patches need to be applied in sequence:

linux-2.6.16.tar.gz (from http://www.kernel.org/pub/linux/kernel/v2.6)
+ linux-2.6.16-s390-base-october2005.diff (IBM)
+ linux-2.6.16-s390-01-october2005.diff (IBM)
+ linux-2.6.16-s390-02-october2005.diff (IBM)
+ linux-2.6.16-s390-03-october2005.diff (IBM)
+ linux-2.6.16-s390-04-october2005.diff (IBM)
+ linux-2.6.16-s390-05-october2005.diff (IBM)
+ linux-2.6.16-s390-06-october2005.diff (IBM)
+ linux-2.6.16-s390-07-october2005.diff (IBM)
+ linux-2.6.16-s390-08-october2005.diff (IBM)
+ linux-2.6.16-s390-09-october2005.diff (IBM)
+ linux-2.6.16-s390-10-october2005.diff (IBM)
+ linux-2.6.16-s390-11-october2005.diff (IBM)
+ linux-2.6.16-s390-12-october2005.diff (IBM)
+ linux-2.6.16-s390-13-october2005.diff (IBM)
+ linux-2.6.16-s390-14-october2005.diff (IBM)
+ linux-2.6.16-s390-15-october2005.diff (IBM)
+ linux-2.6.16-s390-16-october2005.diff (IBM)
+ linux-2.6.16-s390-17-october2005.diff (IBM)
+ linux-2.6.16-s390-18-october2005.diff (IBM)
+ linux-2.6.16-s390-19-october2005.diff (IBM)
+ linux-2.6.16-s390-20-october2005.diff (IBM)
+ linux-2.6.16-s390-21-october2005.diff (IBM)
+ linux-2.6.16-s390-22-october2005.diff (IBM)

Contact the IBM team

If you want to contact the Linux on System z IBM team refer to the Contact the Linux on System z IBM team page.