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]

Kernel patches

2003-06-30 kernel 2.4.21 bug fix patch 02 ("June 2003")

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-02-june2003.tar.gz / MD5 ... accumulated patch, recommended (2003-06-30)

linux-2.4.21-s390-02-june2003-patches.tar.gz / MD5 ... per-problem-patches, recommended (2003-06-30)

These patches contain the following linux kernel bug fixes:

Description:
multicast or broadcast flood ping hang on HiperSockets
Symptom:
multicast or broadcast flood ping hang on HiperSockets
Problem:
delayed freeing of skbs
Solution:
poll for multicast queue earlier to not have skb hanging around for a long time
Problem-ID:
n/a
Description:
starting a LCS network device with specific module parameters causes an address exception
Symptom:
1. start LCS module with parameter model_no=1 and rel_adapter_no=1
2. starting the LCS network device causes an address exception
Problem:
init_waitqueue_head was not called for a lanstat_wait in kernel version > 2.3.0
Solution:
Properly initialize lanstat_wait
Problem-ID:
n/a
Description:
Wrong data direction of START STOP UNIT command.
Symptom:
"RSP_CODE_FIELD_INVALID" messages and unable to access device.
Problem:
When sending a START STOP UNIT command to a device the SCSI stack sets the data direction to SCSI_DATA_READ. Because of this the zfcp device driver creates an FCP_CMND IU where RDDATA is set to 1.
Some hardware will recognize this invalid setting and respond to this with an FCP_RSP IU where the RSP_CODE field is set to "FCP_CMND Fields Invalid".
Solution:
Set data direction to SCSI_DATA_NONE.
Problem-ID:
n/a
Description:
Deadlock in memory management code.
Symptom:
Mapping and accessing memory on a 64 bit zLinux system that requires a full segment table can lead to a deadlock if the system is low on memory.
Problem:
The extension of a half-sized pmd (8K) to a full-sized pmd (16K) requires the allocation of 4 consequitive pages. If the system starts swapping to allocate these 4 pages and touches the page table the reallocation is done for it deadlocks on the page table lock.
Solution:
Release the page table lock in pgd_populate before calling __get_free_pages.
Problem-ID:
n/a

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)

Note: If On-demand timer is required, apply as last patch:
+ linux-2.4.21-s390-timer-june2003.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.