2005-12-09 kernel 2.6.5 bug fix patch 32 ("April 2004")

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

linux-2.6.5-s390-32-april2004.tar.gz / MD5 ... accumulated patch, recommended (2005-12-09)

linux-2.6.5-s390-32-april2004-patches.tar.gz / MD5 ... per-problem-patches, recommended (2005-12-09)

These patches contain the following linux kernel bug fixes:

Description:
qdio: avoid duplicate timeout.
Symptom:
Kernel BUG at drivers/s390/cio/qdio.c:1815 seen in a crash dump.
Problem:
BUG() in qdio_timeout_handler() should never occur. qdio_establish() schedules timeout handling twice - with its ccw_device_start_timeout() invocation and with its wait_event_interruptible_timeout() invocation. This may result in a race condition.
Solution:
Change the wait_event_interruptible_timeout() invocation into a wait_event_interruptible() invocation.
Problem-ID:
19639
Description:
qeth: unpredictable recovery results on cable pull/insert.
Symptom:
When pulling a cable and inserting back again, we get unpredictable results, e.g. broadcast packets starts working some minutes later although uni- and multicast packets are already flowing.
Problem:
When cable is inserted back, qeth gets a STARTLAN command initiated by OSA. qeth just registers IP addresses without any initialization commands and wakes up the net_device queue. We have to reinitialize the device once we get a STARTLAN command.
Solution:
Schedule recovery when STARTLAN command has been received.
Problem-ID:
19446
Description:
qeth: fix Layer2 multicast address processing.
Symptom:
Appletalk does not work with VSWITCH and OSA-level 2 card.
Problem:
qeth support for Multicast scans mc-lists anchored in ip_ptr and ip6_ptr, however all Layer 2 addresses are listed in dev->mc_list, like Appletalk Layer 2 address. qeth Layer 2 multicast support needs extension for mc_list processing.
Solution:
When running in Layer 2 mode, walk through dev->mc_list and register these entries.
Problem-ID:
17536
Description:
qeth: additional s390dbf output for qdio errors.
Symptom:
Missing output in /proc/s390dbf/qeth_qerr/hex_ascii.
Problem:
qeth does not add any entries to /proc/s390dbf/qeth_qerr/hex_ascii for problems detected during qdio SIGA processing.
Solution:
Provide qdio error information within /proc/s390dbf/qeth_qerr/hex_ascii.
Problem-ID:
19849
Description:
qeth: broken list handling with card_ip_address de-register.
Symptom:
deadlock (with kexec).
Problem:
List was subject to race-condition - due to weak locking.
Solution:
List processing changed to "do it all over again".
Problem-ID:
19886
Description:
qeth: connectivity lost after Layer 2 device recovery.
Symptom:
Recovery of non-guestLAN Layer 2 device failed which results in connectivity lost.
Problem:
Recovery of non-guestLAN Layer 2 device failed due to trying to register the real MAC address we got from the READ_MAC adapter parameters command.
Solution:
We have to keep the "old" MAC address when we process the reply of a READ_MAC, means ignore the new one.
Problem-ID:
19984
Description:
qeth: customer wants qeth driver to be loaded and running without ipv6 module loaded prior to.
Symptom:
qeth module built with ipv6 support will not load when ipv6 module is not loaded.
Problem:
qeth driver is using basic ipv6 functions which are needed to register IPv6 IP addresses. These functions are not available when ipv6 module is not loaded.
Solution:
Use symbol_put/symbol_get and get function addresses when available and call them. Use wrapper functions then in qeth.
Problem-ID:
19880
Description:
zfcp: Cannot set FCP adapter online on z900.
Symptom:
Adapter erp failed when setting adapter online.
Problem:
With NPIV support an additional function (exchange port data) is called during opening sequence for an FCP adapter. This function is not available on z900 and the opening sequence fails.
Solution:
Call exchange port data function during opening sequence for an adapter only if the adapter supports it.
Problem-ID:
19212

Everybody should apply this patch.

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

linux-2.6.5.tar.gz (see www.kernel.org/pub/linux/kernel/v2.6)
+ linux-2.6.5-s390-base-april2004.diff (IBM)
+ linux-2.6.5-s390-01-april2004.diff (IBM)
+ xipfs612 (see linuxvm.org/patches/index.html)
+ xipfs622 (see linuxvm.org/patches/index.html)
+ linux-2.6.5-s390-02-april2004.diff (IBM)
+ linux-2.6.5-s390-03-april2004.diff (IBM)
+ single threaded workqueue patch (see marc.theaimsgroup.com/?l=bk-commits-head&m=108305028322900&q=raw)
+ linux-2.6.5-s390-04-april2004.diff (IBM)
+ linux-2.6.5-s390-05-april2004.diff (IBM)
+ linux-2.6.5-s390-06-april2004.diff (IBM)
+ linux-2.6.5-s390-07-april2004.diff (IBM)
+ linux-2.6.5-s390-08-april2004.diff (IBM)
+ linux-2.6.5-s390-09-april2004.diff (IBM)
+ linux-2.6.5-s390-10-april2004.diff (IBM)
+ linux-2.6.5-s390-11-april2004.diff (IBM)
+ linux-2.6.5-s390-12-april2004.diff (IBM)
+ linux-2.6.5-s390-13-april2004.diff (IBM)
+ linux-2.6.5-s390-14-april2004.diff (IBM)
+ linux-2.6.5-s390-15-april2004.diff (IBM)
+ linux-2.6.5-s390-16-april2004.diff (IBM)
+ linux-2.6.5-s390-17-april2004.diff (IBM)
+ linux-2.6.5-s390-18-april2004.diff (IBM)
+ linux-2.6.5-s390-19-april2004.diff (IBM)
+ linux-2.6.5-s390-20-april2004.diff (IBM)
+ linux-2.6.5-s390-21-april2004.diff (IBM)
+ linux-2.6.5-s390-22-april2004.diff (IBM)
+ linux-2.6.5-s390-23-april2004.diff (IBM)
+ linux-2.6.5-s390-24-april2004.diff (IBM)
+ linux-2.6.5-s390-25-april2004.diff (IBM)
+ linux-2.6.5-s390-26-april2004.diff (IBM)
+ linux-2.6.5-s390-27-april2004.diff (IBM)
+ linux-2.6.5-s390-28-april2004.diff (IBM)
+ linux-2.6.5-s390-29-april2004.diff (IBM)
+ linux-2.6.5-s390-30-april2004.diff (IBM)
+ linux-2.6.5-s390-31-april2004.diff (IBM)
+ linux-2.6.5-s390-32-april2004.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.