Kernel 2.4 based: June 2003 stream

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

linux-2.4.21-s390-19-june2003.tar.gz / MD5 ... accumulated patch, recommended (2004-11-02)

linux-2.4.21-s390-19-june2003-patches.tar.gz / MD5 ... per-problem-patches, recommended (2004-11-02)

These patches contain the following linux kernel bug fixes:

Description:

ctcmpc: Fixes missing channel id (used by chandev) bug and adds additional debug statements.

Symptom:

chandev reports unknown verb when attempting to load ctcmpc device. The module is not loaded.

Problem:

channel type id missing.

Solution:

channel type id added.

Problem-ID:

12107

Description:

dasd: FBA error recovery for 3370 and 9336 not called.

Symptom:

none (found by source analysis)

Problem:

The dev_model was used to determine the device type and so the case never became true.

Solution:

Use the dev_type.

Problem-ID:

12026

Description:

dasd: FBA requests failing under memory pressure.

Symptom:

Failing I/O requests on FBA devices causing several problems going along with the messages "dasd: (xxxx) CCW creation failed on request <ppp>" and "end_request: I/O error, dev xx:yy (dasd), sector <sss>".

Problem:

A memory allocation failure while building IDALs (only done if more than 2G main memory available) in 'dasd_set_normalized_cda' was not properly reported as ENOMEM, which would have caused the request to be re-queued. Instead an unspecified error condition was reported, which caused the I/O request to be terminated.

Solution:

Report memory allocation error as ENOMEM to enable re-queuing.

Problem-ID:

12029

Note:

applicable for 64 bit Linux, only

Description:

qeth: checksum is generated by stack even with no_checksumming.

Symptom:

Even when no_checksumming parameter was set, Linux network stack generates checksum for each incoming packet, causing performance degradations.

Problem:

skb->ip_summed was not set correctly when no_checksumming had been set in chandev.conf

Solution:

Set skb->ip_summed correctly.

Problem-ID:

12142

Description:

qeth: socket write queue is blocked when network cable is pulled.

Symptom:

When the network cable is pulled, the write queue of the associated socket fills up. Normally, the queue should not fill but packets should be discarded by the driver.

Problem:

We did a netif_stop_queue before checking if we are startlan-ed (i.e. cable is plugged in). Then we did the check and never started the queue again.

Solution:

First check if we are startlan-ed. If not, drop packet.

Problem-ID:

12090

Description:

zfcp: FCP port cannot recover after aborted nameserver request.

Symptom:

Due to faulty handling of aborted nameserver requests ports are marked as failed by mistake. This involves that such a port is not automatically recovered anymore.

Problem:

zfcp_fsf_gid_pn_handler() does not check if the corresponding request has succesfully completed. Hence the flag ZFCP_STATUS_PORT_INVALID_WWPN is set if a nameserver request was aborted. This in turn involves that the port is marked as failed.

Solution:

Check if the request was succesfully executed before response is evaluated in zfcp_fsf_gid_pn_handler().

Problem-ID:

12175

Description:

zfcp: Insufficient debugging information in /var/log/messages for 'LUN sharing violation'.

Symptom:

If a LUN is already in use by another LPAR zfcp does not log the CSS ID.

Problem:

If a LUN is already in use by another LPAR zfcp logs only an LPAR number inside CSS but not the ID of the CSS.

Solution:

Log LPAR number and CSS ID.

Problem-ID:

11576

Description:

zfcp: Kernel panic possible when a timeout handler of a memory pool is called.

Symptom:

In case of low memory a kernel panic may happen.

Problem:

When a timeout handler of a memory pool is registered a false pointer to a handler parameter is provided.

Solution:

Provide a correct pointer to parameter when registering a timeout handler.

Problem-ID:

12032

Everybody should apply this patch.

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

linux-2.4.21.tar.gz (see www.kernel.org)
+ linux-2.4.21-s390-june2003.diff (IBM)
+ linux-2.4.21-s390-01-june2003.diff (IBM)
+ linux-2.4.21-s390-02-june2003.diff (IBM)
+ linux-2.4.21-s390-03-june2003.diff (IBM)
+ linux-2.4.21-s390-04-june2003.diff (IBM)
+ linux-2.4.21-s390-05-june2003.diff (IBM)
+ linux-2.4.21-s390-06-june2003.diff (IBM)
+ linux-2.4.21-s390-07-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-09-june2003.diff (IBM)
+ linux-2.4.21-s390-10-june2003.diff (IBM)
+ xip2fs1 (see linuxvm.org/patches/index.html)
+ xip2fs2 (see linuxvm.org/patches/index.html)
+ linux-2.4.21-s390-11-june2003.diff (IBM)
+ linux-2.4.21-s390-12-june2003.diff (IBM)
+ linux-2.4.21-s390-13-june2003.diff (IBM)
+ linux-2.4.21-s390-14-june2003.diff (IBM)
+ linux-2.4.21-s390-15-june2003.diff (IBM)
+ linux-2.4.21-s390-16-june2003.diff (IBM)
+ linux-2.4.21-s390-17-june2003.diff (IBM)
+ linux-2.4.21-s390-18-fixed-june2003.diff (IBM)
+ linux-2.4.21-s390-19-june2003.diff (IBM)

Note: If On-demand timer is required, apply as last patch:
+ linux-2.4.21-s390-timer-04-june2003.diff (IBM)

Note: If you apply the above patches, you need as a minimum the 2004-07-14 version of the tape_3590 OCO module "tape3590-2.4.21-s390(x)-02-june2003.tar.gz".

Back to top