Kernel 2.4 based: August 2001 stream

Linux for S/390 31-bit distributions and Linux for zSeries 64-bit distributions can be built using:

• kernel (two alternate kernel levels are available)
• kernel 2.4.17
• kernel 2.4.7
  For both kernel levels separate On-demand timer and Order-2 patches are provided.
• OCO modules for the kernel levels
• kernel 2.4.17: qdio, qeth, tape_3590_mod
• kernel 2.4.7: qdio, qeth, tape_3590_mod


• Special OCO modules for On-demand timer
  No special OCO modules for Order-2

• tool-chain:
• binutils 2.11.90.0.27
• gcc 2.95.3
• glibc 2.2.4
• utilities:
• modutils 2.4.7
• s390-tools 1.0.6
• debug tools:
• gdb 5.0
• strace 4.2.2

Note that most new functions introduced with the "June 2003 stream" and "May 2002 stream" are not available on this combination of levels. For an overview of the three parallel kernel 2.4 streams refer to Downloads for kernel 2.4 page.

	kernel 2.4.17 downloads for the "August 2001 stream"
	OCO modules (kernel 2.4.17) for the "August 2001 stream"
	kernel 2.4.7 downloads for the "August 2001 stream"
	OCO modules (kernel 2.4.7) for the "August 2001 stream"
	Tool-chain for the "August 2001 stream"
	Utilities for the "August 2001 stream"
	Debug tools for the "August 2001 stream"

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

Note: lkcdutils-4.0 includes the dump analysis tool lcrash. lkcdutils-4.0 can be downloaded at http://lkcd.sourceforge.net or http://sourceforge.net/projects/lkcd.

Below are the downloads (with description) for the kernel 2.4.7/17 "August 2001 stream", listed in reverse chronological order. This can be used to backtrack the "August 2001 stream".
The System Build Cross Reference shows the most current set of downloads for the "August 2001 stream" and ignores superseded patches and modules (which are still shown below).

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

• kernel 2.4.17 ("August 2001", 2004-07-14)
• • accumulated patch: linux-2.4.17-s390-15.tar.gz MD5 recommended (2004-07-14)
  • per-problem-patch: linux-2.4.17-s390-15-patches.tar.gz MD5 recommended (2004-07-14)

  This patch contains the following Linux kernel bug fix:

  Description:	Kernel: Lost dirty bits.
  Symptom:	Data corruption under memory pressure.
  Problem:	The hardware dirty bit is cleared every time SetPageUptodate is called. The common memory management code calls the function, even if the page already is up to date. In this case the dirty bit may not be cleared because the page is potentially mapped writable in some user process which could have written to the page since the last writeback.
  Solution:	Add a check to arch_set_page_uptodate to skip the clearing of the dirty bit, if the page is already up to date.
  Problem-ID:	8165

  
  

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)
  + linux-2.4.17-s390-10.diff (IBM)
  + linux-2.4.17-s390-11.diff (IBM)
  + linux-2.4.17-s390-12.diff (IBM)
  + linux-2.4.17-s390-13.diff (IBM)
  + linux-2.4.17-s390-14.diff (IBM)
  + linux-2.4.17-s390-15.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-7.diff (IBM)

• kernel 2.4.7 ("August 2001", 2004-07-14)
• • accumulated patch: linux-2.4.7-s390-20.tar.gz MD5 recommended(2004-07-14)
  • per-problem-patch: linux-2.4.7-s390-20-patches.tar.gz MD5 recommended (2004-07-14)

  This patch contains the following Linux kernel bug fix:

  Description:	Kernel: Lost dirty bits.
  Symptom:	Data corruption under memory pressure.
  Problem:	The hardware dirty bit is cleared every time SetPageUptodate is called. The common memory management code calls the function, even if the page already is up to date. In this case the dirty bit may not be cleared because the page is potentially mapped writable in some user process which could have written to the page since the last writeback.
  Solution:	Add a check to arch_set_page_uptodate to skip the clearing of the dirty bit, if the page is already up to date.
  Problem-ID:	8165

  
  

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)
  + linux-2.4.7-s390-15.diff (IBM)
  + linux-2.4.7-s390-16.diff (IBM)
  + linux-2.4.7-s390-17.diff (IBM)
  + linux-2.4.7-s390-18.diff (IBM)
  + linux-2.4.7-s390-19.diff (IBM)
  + linux-2.4.7-s390-20.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-8.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-9.diff (IBM)



• Order-2 ("August 2001", 2004-07-14)

  linux-2.4.7-order2-9.tar.gz MD5 recommended (2004-07-14)

  The "order 2 allocation relief" patch is a complete replacement of the recommended patch shipped on 2004-06-09. This patch is functionally equivalent to the 2004-06-09 patch.

  • This patch is very s/390 specific, but does not break other architectures.
  • This patch does only work for a 64-bit Linux for zSeries kernel, but can also be applied if you intend to build a 31-bit kernel.
  • This patch is compatible with the "On-demand timer patch" and does not require special OCO modules.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.7 patches on top of linux-2.4.7.tar.gz (see www.kernel.org) and as last patch
  + linux-2.4.7-order2-9.diff (IBM), or on top of linux-2.4.7-timer-8.diff (IBM) if timer is required.

• kernel 2.4.17 ("August 2001", 2004-06-09)
• • accumulated patch: linux-2.4.17-s390-14.tar.gz MD5 recommended (2004-06-09)
  • per-problem-patches: linux-2.4.17-s390-14-patches.tar.gz MD5 recommended (2004-06-09)

  These patches contain the following Linux kernel bug fixes:

  Description:	cio: Deferred cc=3 on BASIC SENSE leads to data corruption.
  Symptom:	Data corruption after heavy I/O workload while ESS is doing failover.
  Problem:	BASIC SENSE after a unit check returns with deferred cc=3. The device driver is called with the device status for the BASIC SENSE which it should not see.
  Solution:	If a deferred cc=3 after a BASIC SENSE happens, call the device driver with the device status for the preceding unit check and reset the w4sense flag.
  Problem-ID:	9055

  
  

  Description:	iucv: restart of multiple IUCV connections fails.
  Symptom:	Further IUCV connections are only possible after reloading of module netiucv.
  Problem:	When restarting IUCV connections, the old IUCV pathids are not reused. Thus repeated restart of a single IUCV connection resp. few restarts of multiple IUCV connections result in reaching the maximum number limit of IUCV paths.
  Solution:	Handling of an IUCV connection severed by partner is changed: No reconnect is made; instead the IUCV connection stays in state STARTWAIT till a "Connection Pending" interrupt arrives.
  Problem-ID:	7640

  
  

  Description:	kernel: mlock() gets stuck in get_user_pages/follow_page.
  Symptom:	Process doing mlock loops in the kernel with kernel locks held.
  Problem:	set_pte/pte_mkdirty does not cause pte_dirty to return true but the common mm code relies on it.
  Solution:	Set page dirty if required but do not loop on !pte_dirty().
  Problem-ID:	8210

  
  

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)
  + linux-2.4.17-s390-10.diff (IBM)
  + linux-2.4.17-s390-11.diff (IBM)
  + linux-2.4.17-s390-12.diff (IBM)
  + linux-2.4.17-s390-13.diff (IBM)
  + linux-2.4.17-s390-14.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-7.diff (IBM)

• kernel 2.4.7 ("August 2001", 2004-06-09)
• • accumulated patch: linux-2.4.7-s390-19.tar.gz MD5 recommended(2004-06-09)
  • per-problem-patches: linux-2.4.7-s390-19-patches.tar.gz MD5 recommended (2004-06-09)

  These patches contain the following Linux kernel bug fixes:

  Description:	cio: Deferred cc=3 on BASIC SENSE leads to data corruption.
  Symptom:	Data corruption after heavy I/O workload while ESS is doing failover.
  Problem:	BASIC SENSE after a unit check returns with deferred cc=3. The device driver is called with the device status for the BASIC SENSE which it should not see.
  Solution:	If a deferred cc=3 after a BASIC SENSE happens, call the device driver with the device status for the preceding unit check and reset the w4sense flag.
  Problem-ID:	9055

  
  

  Description:	iucv: restart of multiple IUCV connections fails.
  Symptom:	Further IUCV connections are only possible after reloading of module netiucv.
  Problem:	When restarting IUCV connections, the old IUCV pathids are not reused. Thus repeated restart of a single IUCV connection resp. few restarts of multiple IUCV connections result in reaching the maximum number limit of IUCV paths.
  Solution:	Handling of an IUCV connection severed by partner is changed: No reconnect is made; instead the IUCV connection stays in state STARTWAIT till a "Connection Pending" interrupt arrives.
  Problem-ID:	7640

  
  

  Description:	kernel: mlock() gets stuck in get_user_pages/follow_page.
  Symptom:	Process doing mlock loops in the kernel with kernel locks held.
  Problem:	set_pte/pte_mkdirty does not cause pte_dirty to return true but the common mm code relies on it.
  Solution:	Set page dirty if required but do not loop on !pte_dirty().
  Problem-ID:	8210

  
  

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)
  + linux-2.4.7-s390-15.diff (IBM)
  + linux-2.4.7-s390-16.diff (IBM)
  + linux-2.4.7-s390-17.diff (IBM)
  + linux-2.4.7-s390-18.diff (IBM)
  + linux-2.4.7-s390-19.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-8.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-8.diff (IBM)

• Order-2 ("August 2001", 2004-06-09) (superseded)

  linux-2.4.7-order2-8.tar.gz MD5 recommended (2004-06-09)

  The "order 2 allocation relief" patch is a complete replacement of the recommended patch shipped on 2003-09-04. This patch is functionally equivalent to the 2003-09-04 patch.

  • This patch is very s/390 specific, but does not break other architectures.
  • This patch does only work for a 64-bit Linux for zSeries kernel, but can also be applied if you intend to build a 31-bit kernel.
  • This patch is compatible with the "On-demand timer patch" and does not require special OCO modules.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.7 patches on top of linux-2.4.7.tar.gz (see www.kernel.org) and as last patch
  + linux-2.4.7-order2-8.diff (IBM), or on top of linux-2.4.7-timer-8.diff (IBM) if timer is required.

• kernel 2.4.17 ("August 2001", 2004-03-24)
• • accumulated patch: linux-2.4.17-s390-13.tar.gz MD5 recommended (2004-03-24)
  • per-problem-patches: linux-2.4.17-s390-13-patches.tar.gz MD5 recommended (2004-03-24)

  These patches contain the following Linux kernel bug fixes:

  Description:	iucv: IUCV send failure.
  Symptom:	strace of ping shows that sendmsg returns ENOBUFS.
  Problem:	tx_queue_len of the iucv net_device is set to zero.
  Solution:	Set tx_queue_len to the message limit returned from the ACCEPT function of IUCV.
  Problem-ID:	6157

  
  

  Description:	iucv: unable to reconnect after reboot
  Symptom:	Connection FSM state: Stopped in /proc/net/iucv/iucv0/statistics of iucv-partner of the rebooting system
  Problem:	The iucv-partner of a rebooting system does not try to reconnect when remote partner severed connection
  Solution:	Added connect retry when remote severed connection
  Problem-ID:	6631
  Note:	This patch fixes a problem introduced with the fix for Problem-ID 5912 in linux-2.4.17-s390-12.diff (2004-01-26).

  
  

  Description:	lcs: multicast joins and drops not noticed by drivers
  Symptom:	multicast traffic is not received
  Problem:	driver did not notice stack using multicast addresses
  Solution:	use notifier_call_chain to notify drivers
  Problem-ID:	5921

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)
  + linux-2.4.17-s390-10.diff (IBM)
  + linux-2.4.17-s390-11.diff (IBM)
  + linux-2.4.17-s390-12.diff (IBM)
  + linux-2.4.17-s390-13.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-7.diff (IBM)

• kernel 2.4.7 ("August 2001", 2004-03-24)
• • accumulated patch: linux-2.4.7-s390-18.tar.gz MD5 recommended(2004-03-24)
  • per-problem-patches: linux-2.4.7-s390-18-patches.tar.gz MD5 recommended (2004-03-24)

  These patches contain the following Linux kernel bug fixes:

  Description:	iucv: IUCV send failure.
  Symptom:	strace of ping shows that sendmsg returns ENOBUFS.
  Problem:	tx_queue_len of the iucv net_device is set to zero.
  Solution:	Set tx_queue_len to the message limit returned from the ACCEPT function of IUCV.
  Problem-ID:	6157

  
  

  Description:	iucv: unable to reconnect after reboot
  Symptom:	Connection FSM state: Stopped in /proc/net/iucv/iucv0/statistics of iucv-partner of the rebooting system
  Problem:	The iucv-partner of a rebooting system does not try to reconnect when remote partner severed connection
  Solution:	Added connect retry when remote severed connection
  Problem-ID:	6631
  Note:	This patch fixes a problem introduced with the fix for Problem-ID 5912 in linux-2.4.7-s390-17.diff (2004-01-26).

  
  

  Description:	lcs: multicast joins and drops not noticed by drivers
  Symptom:	multicast traffic is not received
  Problem:	driver did not notice stack using multicast addresses
  Solution:	use notifier_call_chain to notify drivers
  Problem-ID:	5921

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)
  + linux-2.4.7-s390-15.diff (IBM)
  + linux-2.4.7-s390-16.diff (IBM)
  + linux-2.4.7-s390-17.diff (IBM)
  + linux-2.4.7-s390-18.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-8.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-7.diff (IBM)

• kernel 2.4.17 ("August 2001", 2004-01-26)
• • accumulated patch: linux-2.4.17-s390-12.tar.gz MD5 recommended (2004-01-26)
  • per-problem-patches: linux-2.4.17-s390-12-patches.tar.gz MD5 recommended (2004-01-26)

  These patches contain the following Linux kernel bug fixes:

  Description:	dasd: Driver sets improper default cache mode on ESS
  Symptom:	Performance limitation.
  Problem:	Suboptimal caching behavior for 'default' workload limits I/O performance.
  Solution:	Set proper default (normal caching).
  Problem-ID:	5409

  
  

  Description:	dasd: BUG when pulling/plug in fibers associated with ESS.
  Symptom:	BUG in dasd ERP leads to kernel panic.
  Problem:	The (paranoia) macro in dasd_3990_erp_alternate_path assumes that the status of the request is ERROR, but it might also be FILLED (if the situation happens the first time)
  Solution:	Only reduce status to QUEUED (do not enhance)
  Problem-ID:	5702

  
  

  Description:	dasd: Massive workload combined with ESS FlashCopy leading to I/O hang.
  Symptom:	FlashCopy I/O hang
  Problem:	State change interrupt handler checks only first request in cqr-queue, but in case the fastpath for start_IO was successful, it might happen that the second request is long busy.
  Solution:	Check the whole cqr-queue for long busy.
  Problem-ID:	4676

  
  

  Description:	iucv: Disable message interrupts during connection setup
  Symptom:	--
  Problem:	--
  Solution:	Honor incoming connection severed during connection setup.
  Problem-ID:	5912
  Note:	This patch introduces a problem that is resolved with the fix for Problem-ID 6631 in linux-2.4.17-s390-13.diff (2004-03-24).

  
  

  Description:	z90crypt: Unnecessary restriction to length of inputdata for MEX request
  Symptom:	errno = EINVAL for valid data
  Problem:	checking for even inputdatalength for both CRT and MEX request
  Solution:	only check for CRT request
  Problem-ID:	5633

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)
  + linux-2.4.17-s390-10.diff (IBM)
  + linux-2.4.17-s390-11.diff (IBM)
  + linux-2.4.17-s390-12.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-7.diff (IBM)

  Note: If you apply this patch and are using iucv you may run into Problem-ID 6631, the fix for which is included in linux-2.4.17-s390-13.diff (2004-03-24).

• kernel 2.4.7 ("August 2001", 2004-01-26)
• • accumulated patch: linux-2.4.7-s390-17.tar.gz MD5 recommended(2004-01-26)
  • per-problem-patches: linux-2.4.7-s390-17-patches.tar.gz MD5 recommended (2004-01-26)

  These patches contain the following Linux kernel bug fixes:

  Description:	dasd: Driver sets improper default cache mode on ESS
  Symptom:	Performance limitation.
  Problem:	Suboptimal caching behavior for 'default' workload limits I/O performance.
  Solution:	Set proper default (normal caching).
  Problem-ID:	5409

  
  

  Description:	dasd: BUG when pulling/plug in fibers associated with ESS.
  Symptom:	BUG in dasd ERP leads to kernel panic.
  Problem:	The (paranoia) macro in dasd_3990_erp_alternate_path assumes that the status of the request is ERROR, but it might also be FILLED (if the situation happens the first time)
  Solution:	Only reduce status to QUEUED (do not enhance)
  Problem-ID:	5702

  
  

  Description:	dasd: Massive workload combined with ESS FlashCopy leading to I/O hang.
  Symptom:	FlashCopy I/O hang
  Problem:	State change interrupt handler checks only first request in cqr-queue, but in case the fastpath for start_IO was successful, it might happen that the second request is long busy.
  Solution:	Check the whole cqr-queue for long busy.
  Problem-ID:	4676

  
  

  Description:	iucv: Disable message interrupts during connection setup
  Symptom:	--
  Problem:	--
  Solution:	Honor incoming connection severed during connection setup.
  Problem-ID:	5912
  Note:	This patch introduces a problem that is resolved with the fix for Problem-ID 6631 in linux-2.4.7-s390-18.diff (2004-03-24).

  
  

  Description:	z90crypt: Unnecessary restriction to length of inputdata for MEX request
  Symptom:	errno = EINVAL for valid data
  Problem:	checking for even inputdatalength for both CRT and MEX request
  Solution:	only check for CRT request
  Problem-ID:	5633

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)
  + linux-2.4.7-s390-15.diff (IBM)
  + linux-2.4.7-s390-16.diff (IBM)
  + linux-2.4.7-s390-17.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-8.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-7.diff (IBM)

  Note: If you apply this patch and are using iucv you may run into Problem-ID 6631, the fix for which is included in linux-2.4.7-s390-18.diff (2004-03-24).

• kernel 2.4.17 ("August 2001", 2003-12-05)
• • accumulated patch: linux-2.4.17-s390-11.tar.gz MD5 recommended (2003-12-05)
  • per-problem-patches: linux-2.4.17-s390-11-patches.tar.gz MD5 recommended (2003-12-05)

  These patches contain the following Linux kernel bug fixes:

  Description:	Crashes, triggered by iucv and ctc when calling dst_link_failure()
  Symptom:	Miscellaneous crashes, triggered by calling dst_link_failure()
  Problem:	Calling dst_link_failure() triggers a bug in common code.
  Solution:	Removed call of dst_link_failure() in both netiucv.c and ctcmain.c
  Problem-ID:	5098

  
  

  Description:	Fixed S390 Debug Feature usage.
  Symptom:	Segmentation fault when DBF file is read.
  Problem:	The sprintf event/exception functions write a pointer to the format string (%s) into the log. This means that the string must be valid at the time the DBF-log is read.
  Solution:	Don't write 'volatile' strings to DBF.
  Problem-ID:	4822

  
  

  Description:	Unable to reconnect when using z/VM 3.1 at remote peer.
  Symptom:	When peer interface was recycled, iucv is unable to reconnect.
  Problem:	Incoming message interrupt during setup leads to illegal driver state.
  Solution:	Disable all interrupts during setup
  Problem-ID:	3061

  
  

  Description:	crashes triggered by s390 network drivers calling dst_link_failure
  Symptom:	crashes, bugs in icmp.c
  Problem:	network driver called dst_link_failure
  Solution:	remove dst_link_failure call
  Problem-ID:	5108

  
  

  Description:	ctc: loglevel parameter could not be set to maximum
  Symptom:	Numbers with more than 1 digit are ignored when writing to /proc/net/ctc/ctc0/loglevel
  Problem:	Check for maximum string length was wrong.
  Solution:	Corrected check for maximum string length.
  Problem-ID:	4342

  
  

  Description:	reduce stack usage (for qeth: export show_trace symbol)
  Symptom:	symlink loops on NFS share causes oops
  Problem:	stack overflow
  Solution:	reduce stack usage by inlining some functions and check for stack usage. Export show_trace symbol which is needed for the corresponding qeth fix.
  Problem-ID:	3344

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)
  + linux-2.4.17-s390-10.diff (IBM)
  + linux-2.4.17-s390-11.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-7.diff (IBM)

• On-demand timer patch kernel 2.4.17 ("August 2001", 2003-12-05)
  

  Release notes: Adaption to above 2003-12-05 kernel-patch.
  This patch is a complete replacement of the patch contained in linux-2.4.17-timer-6.tar.gz shipped on 2003-09-04.
  This patch is functionaly equivalent to the 2003-09-04 patch.

  linux-2.4.17-timer-7.tar.gz MD5 recommended (2003-12-05)

  On demand timer patch:
  Contains a patch for the linux kernel 2.4.17 that changes the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The drawback is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_IDLE_HZ_TIMER that lets you choose between the old and the new behavior. Note that you'll need different qdio, qeth and tape_3590_mod modules if you use the no hz timer option.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.17 patches on top of linux-2.4.17.tar.gz (see www.kernel.org) and as last patch

  + linux-2.4.17-timer-7.diff (IBM)

• qdio kernel 2.4.17 ("August 2001", 2003-12-05)

  31-bit: qdio-2.4.17-s390-7.tar.gz MD5 and qdio-2.4.17-s390-7-timer.tar.gz MD5 (2003-12-05)

  64-bit: qdio-2.4.17-s390x-7.tar.gz MD5 and qdio-2.4.17-s390x-7-timer.tar.gz MD5 (2003-12-05)

• The qdio 31-bit and 64-bit OCO-modules of 2003-12-05 are replacements for the 2003-07-07 recommended qdio modules.

• qeth kernel 2.4.17 ("August 2001", 2003-12-05)

  31-bit: qeth-2.4.17-s390-7.tar.gz MD5 and qeth-2.4.17-s390-7-timer.tar.gz MD5 (2003-12-05)

  64-bit: qeth-2.4.17-s390x-7.tar.gz MD5 and qeth-2.4.17-s390x-7-timer.tar.gz MD5 (2003-12-05)

• The qeth 31-bit and 64-bit OCO-modules of 2003-12-05 are replacements for the 2003-07-07 recommended qeth modules containing the below bug fixes.

  Description:	spinlock problem with unsupported ioctls in qeth
  Symptom:	deadlock in ioctl of unsupported ioctl of qeth
  Problem:	spinlock was not released
  Solution:	release spinlock before leaving function
  Problem-ID:	3287

  
  

  Description:	reduce stack usage
  Symptom:	symlink loops on NFS share causes oops
  Problem:	stack overflow
  Solution:	reduce stack usage by inlining some functions and check for stack usage
  Problem-ID:	3344

  
  

  Description:	avoid hang during initialization on I/O errors
  Symptom:	system hangs when initializing
  Problem:	on I/O errors, a lock was not released
  Solution:	release the lock
  Problem-ID:	4971

  
  

  Description:	crashes triggered by s390 network drivers calling dst_link_failure
  Symptom:	crashes, bugs in icmp.c
  Problem:	network driver called dst_link_failure
  Solution:	remove dst_link_failure call
  Problem-ID:	5108

  
  

  Description:	VIPA and Proxy ARP problems on qeth
  Symptom:	add_rxip4, add_vipa4 etc. do not work
  Problem:	control flags not set correctly, netmask bad for VSWITCH
  Solution:	fixed flags, use 0 as default netmask
  Problem-ID:	5178

• kernel 2.4.7 ("August 2001", 2003-12-05)
• • accumulated patch: linux-2.4.7-s390-16.tar.gz MD5 recommended(2003-12-05)
  • per-problem-patches: linux-2.4.7-s390-16-patches.tar.gz MD5 recommended (2003-12-05)

  These patches contain the following Linux kernel bug fixes:

  Description:	Crashes, triggered by iucv and ctc when calling dst_link_failure()
  Symptom:	Miscellaneous crashes, triggered by calling dst_link_failure()
  Problem:	Calling dst_link_failure() triggers a bug in common code.
  Solution:	Removed call of dst_link_failure() in both netiucv.c and ctcmain.c
  Problem-ID:	5098

  
  

  Description:	Incorrect calculation of max_blocks in DIAG discipline
  Symptom:	BUG in dasd_alloc_request
  Problem:	Maximum size request can not be handled by dasd device driver.
  Solution:	Make sure the request size fits (correct calculation).
  Problem-ID:	4922
  Note:	applicable for 31-bit Linux, only

  
  

  Description:	Unable to reconnect when using z/VM 3.1 at remote peer.
  Symptom:	When peer interface was recycled, iucv is unable to reconnect.
  Problem:	Incoming message interrupt during setup leads to illegal driver state.
  Solution:	Disable all interrupts during setup
  Problem-ID:	3061

  
  

  Description:	crashes triggered by s390 network drivers calling dst_link_failure
  Symptom:	crashes, bugs in icmp.c
  Problem:	network driver called dst_link_failure
  Solution:	remove dst_link_failure call
  Problem-ID:	5108

  
  

  Description:	ctc: loglevel parameter could not be set to maximum
  Symptom:	Numbers with more than 1 digit are ignored when writing to /proc/net/ctc/ctc0/loglevel
  Problem:	Check for maximum string length was wrong.
  Solution:	Corrected check for maximum string length.
  Problem-ID:	4342

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)
  + linux-2.4.7-s390-15.diff (IBM)
  + linux-2.4.7-s390-16.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-8.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-7.diff (IBM)

• qdio kernel 2.4.7 ("August 2001", 2003-12-05)

  31-bit: qdio-2.4.7-s390-14.tar.gz MD5 and qdio-2.4.7-s390-14-timer.tar.gz MD5 (2003-12-05)

  64-bit: qdio-2.4.7-s390x-14.tar.gz MD5 and qdio-2.4.7-s390x-14-timer.tar.gz MD5 (2003-12-05)

• The qdio 31-bit and 64-bit OCO-modules of 2003-12-05 are replacements for the 2003-07-07 recommended qdio modules.

• qeth kernel 2.4.7 ("August 2001", 2003-12-05)

  31-bit: qeth-2.4.7-s390-14.tar.gz MD5 and qeth-2.4.7-s390-14-timer.tar.gz MD5 (2003-12-05)

  64-bit: qeth-2.4.7-s390x-14.tar.gz MD5 and qeth-2.4.7-s390x-14-timer.tar.gz MD5 (2003-12-05)

• The qeth 31-bit and 64-bit OCO-modules of 2003-12-05 are replacements for the 2003-07-07 recommended qeth modules containing the below bug fixes.

  Description:	spinlock problem with unsupported ioctls in qeth
  Symptom:	deadlock in ioctl of unsupported ioctl of qeth
  Problem:	spinlock was not released
  Solution:	release spinlock before leaving function
  Problem-ID:	3287

  
  

  Description:	reduce stack usage
  Symptom:	symlink loops on NFS share causes oops
  Problem:	stack overflow
  Solution:	reduce stack usage by inlining some functions and check for stack usage
  Problem-ID:	3344

  
  

  Description:	avoid hang during initialization on I/O errors
  Symptom:	system hangs when initializing
  Problem:	on I/O errors, a lock was not released
  Solution:	release the lock
  Problem-ID:	4971

  
  

  Description:	crashes triggered by s390 network drivers calling dst_link_failure
  Symptom:	crashes, bugs in icmp.c
  Problem:	network driver called dst_link_failure
  Solution:	remove dst_link_failure call
  Problem-ID:	5108

  
  

  Description:	VIPA and Proxy ARP problems on qeth
  Symptom:	add_rxip4, add_vipa4 etc. do not work
  Problem:	control flags not set correctly, netmask bad for VSWITCH
  Solution:	fixed flags, use 0 as default netmask
  Problem-ID:	5178

• kernel 2.4.17 ("August 2001", 2003-09-04)
• • accumulated patch: linux-2.4.17-s390-10.tar.gz MD5 recommended (2003-09-04)
  • per-problem-patches: linux-2.4.17-s390-10-patches.tar.gz MD5 recommended (2003-09-04)

  These patches contain the following Linux kernel bug fixes:

  Description:	<ccwcache>: Incorrect cache index determination
  Symptom:	random kernel oops
  Problem:	The incorrect comparison caused the wrong cache line to be selected for maximum size requests.
  Solution:	fixed the comparison
  Problem-ID:	3450

  
  

  Description:	siginfo_t structure on user stack incorrect.
  Symptom:	Unwinding over a rt signal frame crashes user programs.
  Problem:	The kernel definition of the siginfo_t structure for s390x is 136 bytes long instead of the correct length of 128. The kernel will create a stack frame for rt signal that the unwind code can't process.
  Solution:	Reduce the size of the _pad array.
  Problem-ID:	3490
  Note:	applicable for 64-bit Linux, only

  
  

  Description:	dasd: erroneous message about failing dasd format
  Symptom:	When hitting CTRL-S/CTRL-Q during a dasd format /var/log/messages shows a message like: dasd: /dev/dasdv ( 94: 84),4324@1a42: Formatting of unit 1420 failed with rc = -512
  Problem:	The return code of dasd_sleep_on_request is not checked properly.
  Solution:	Suppress message when return code of dasd_sleep_on_request returns -ERESTARTSYS.
  Problem-ID:	3847

  
  

  Description:	dasd_diag: buggy CMS label recognition in fs/partitions/ibm.c
  Symptom:	CMS reserved minidisk detection doesn't work as expected
  Problem:	CMS label is read from page, that had been freed before
  Solution:	no longer use freed storage for CMS label recognition
  Problem-ID:	3611

  
  

  Description:	crash when using ctc tty with gcov
  Symptom:	See description
  Problem:	Invalid use of netif_stop_queue() and netif_wake_queue() for ctc ttys
  Solution:	code fixed
  Problem-ID:	4174

  
  

  Description:	Oops in iucv code
  Symptom:	Crash with kernel oops when shutting down an iucv connection
  Problem:	Interrupt buffer was released too early
  Solution:	Moved call of iucv_retrieve_buffer() into iucv_exit()
  Problem-ID:	3314

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)
  + linux-2.4.17-s390-10.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-6.diff (IBM)

• On-demand timer patch kernel 2.4.17 ("August 2001", 2003-09-04)
  

  Release notes: Adaption to above 2003-09-04 kernel-patch.
  This patch is a complete replacement of the patch contained in linux-2.4.17-timer-5.tar.gz shipped on 2003-07-07.

  linux-2.4.17-timer-6.tar.gz MD5 recommended (2003-09-04) (superseded)

  On demand timer patch:
  Contains a patch for the linux kernel 2.4.17 that changes the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The drawback is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_IDLE_HZ_TIMER that lets you choose between the old and the new behavior. Note that you'll need different qdio, qeth and tape_3590_mod modules if you use the no hz timer option.

  This patch fixes the following bug:

  Description:	missing local irq disable
  Symptom:	CPUs are idle even if system is under full load
  Problem:	race condition in cpu_idle that results in lost reschedule events
  Solution:	protect with local irq disable
  Problem-ID:	2914

  To create the complete linux kernel sources, apply all IBM kernel 2.4.17 patches on top of linux-2.4.17.tar.gz (see www.kernel.org) and as last patch

  + linux-2.4.17-timer-6.diff (IBM)

• kernel 2.4.7 ("August 2001", 2003-09-04)
• • accumulated patch: linux-2.4.17-s390-15.tar.gz MD5 recommended(2003-09-04)
  • per-problem-patches: linux-2.4.17-s390-15-patches.tar.gz MD5 recommended (2003-09-04)

  These patches contain the following Linux kernel bug fixes:

  Description:	<ccwcache>: Incorrect cache index determination
  Symptom:	random kernel oops
  Problem:	The incorrect comparison caused the wrong cache line to be selected for maximum size requests.
  Solution:	fixed the comparison
  Problem-ID:	3450

  
  

  Description:	siginfo_t structure on user stack incorrect.
  Symptom:	Unwinding over a rt signal frame crashes user programs.
  Problem:	The kernel definition of the siginfo_t structure for s390x is 136 bytes long instead of the correct length of 128. The kernel will create a stack frame for rt signal that the unwind code can't process.
  Solution:	Reduce the size of the _pad array.
  Problem-ID:	3490
  Note:	applicable for 64-bit Linux, only

  
  

  Description:	dasd: erroneous message about failing dasd format
  Symptom:	When hitting CTRL-S/CTRL-Q during a dasd format /var/log/messages shows a message like: dasd: /dev/dasdv ( 94: 84),4324@1a42: Formatting of unit 1420 failed with rc = -512
  Problem:	The return code of dasd_sleep_on_request is not checked properly.
  Solution:	Suppress message when return code of dasd_sleep_on_request returns -ERESTARTSYS.
  Problem-ID:	3847

  
  

  Description:	dasd_diag: buggy CMS label recognition in fs/partitions/ibm.c
  Symptom:	CMS reserved minidisk detection doesn't work as expected
  Problem:	CMS label is read from page, that had been freed before
  Solution:	no longer use freed storage for CMS label recognition
  Problem-ID:	3611

  
  

  Description:	crash when using ctc tty with gcov
  Symptom:	See description
  Problem:	Invalid use of netif_stop_queue() and netif_wake_queue() for ctc ttys
  Solution:	code fixed
  Problem-ID:	4174

  
  

  Description:	Oops in iucv code
  Symptom:	Crash with kernel oops when shutting down an iucv connection
  Problem:	Interrupt buffer was released too early
  Solution:	Moved call of iucv_retrieve_buffer() into iucv_exit()
  Problem-ID:	3314

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)
  + linux-2.4.7-s390-15.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-8.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-7.diff (IBM)

• On demand timer ("August 2001", 2003-09-04)

  Release notes: Adaption to above 2003-09-04 kernel-patch.
  This patch is a complete replacement of the patch contained in linux-2.4.7-timer-7.tar.gz shipped on 2003-07-07.

  linux-2.4.7-timer-8.tar.gz MD5 recommended (2003-09-04)

  Category operating system.
  Contains a patch for the linux kernel 2.4.7 that changes the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The drawback is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_IDLE_HZ_TIMER that lets you choose between the old and the new behavior. Note that you'll need different qdio, qeth and tape_3590_mod modules if you use the no hz timer option.

  This patch fixes the following bug:

  Description:	missing local irq disable
  Symptom:	CPUs are idle even if system is under full load
  Problem:	race condition in cpu_idle that results in lost reschedule events
  Solution:	protect with local irq disable
  Problem-ID:	2914

  To create the complete linux kernel sources, apply all IBM kernel 2.4.7 patches on top of linux-2.4.7.tar.gz (see www.kernel.org) and as last patch

  + linux-2.4.7-timer-8.diff (IBM)

• Order-2 ("August 2001", 2003-09-04)

  linux-2.4.7-order2-7.tar.gz MD5 recommended (2003-09-04) (superseded)

  The "order 2 allocation relief" patch is a complete replacement of the recommended patch shipped on 2003-07-07. This patch is functionaly equivalent to the 2003-07-07 patch. The original patch decreased the kernel stack size to 8KB which turned out to be not enough. As a side-effect of this new patch there is no longer a need for special OCO-modules and the timer patch can be applied to the same kernel.

  • This patch is very s/390 specific, but doesn't break other architectures.
  • This patch does only work for a 64-bit Linux for zSeries kernel, but can also be applied if you intend to build a 31-bit kernel.
  • This patch is compatible with the "On-demand timer patch" and does not require special OCO modules.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.7 patches on top of linux-2.4.7.tar.gz (see www.kernel.org) and as last patch
  + linux-2.4.7-order2-7.diff (IBM), or on top of linux-2.4.7-timer-8.diff (IBM) if timer is required.

• kernel 2.4.17 ("August 2001", 2003-07-07)
• • accumulated patch: linux-2.4.17-s390-9.tar.gz MD5 recommended(2003-07-07)
  • per-problem-patches: linux-2.4.17-s390-9-patches.tar.gz MD5 recommended (2003-07-07)

  These patches contain the following Linux kernel bug fixes:

  Description:	kernel: s390dbf - invalid call of create_proc_entry() within spin_lock_irqsave() section
  Symptom:	Kernel hang when registering a s390dbf view in low memory situations
  Problem:	It is not allowed to call kmalloc() with GFP_KERNEL when interrupts are disabled! create_proc_entry() calls kmalloc(). create_proc_entry() is called when interrupts are disabled.
  Solution:	Call create_proc_entry() before critical section is entered and before interrupts are disabled
  Problem-ID:	2719

  
  

  Description:	Address space switching instruction in user space does not fault.
  Symptom:	System crash due to cpus entering an endless program check loop.
  Problem:	A non-priviledged instruction which can change the primary space origin is not fenched correctly.
  Solution:	Set control register 5 to some value unequal to zero.
  Problem-ID:	2893

  
  

  Description:	dasd: Problems when echoing invalid devno to /proc/dasd/devices.
  Symptom:	Linux hangs when non-existing device is 'set off'.
  Problem:	The spinlock was not released in error path.
  Solution:	Release the spinlock.
  Problem-ID:	2927

  
  

  Description:	/proc/cio_ignore parsing.
  Symptom:	Piping various combinations of device ranges and device numbers to /proc/cio_ignore leads to "illegal operation" or "Trying to vfree() bad address".
  Problem:	Parser called from /proc/cio_ignore didn't work properly.
  Solution:	Backport working /proc/cio_ignore parser from 2.5.
  Problem-ID:	2934

  
  

  Description:	CTC: System hang on shutdown of remote OS/390
  Symptom:	Shutting down a remotely connected OS/390 system causes a system hang.
  Problem:	Receiving garbage data from remote was not properly handled.
  Solution:	Added additional validation of received data.
  Problem-ID:	2314

  
  

  Description:	Clearing of .bss section.
  Symptom:	Kernel compiled with gcc 3.3 doesn't work.
  Problem:	gcc 3.3 puts global variables with an initial value of zero to the .bss section. gcc < 3.3 puts these variables to the .data section. This makes a difference because the clearing of the .bss section is done after the store of the detected memory size to memory_size.
  Solution:	Move clearing of the .bss section before the memory detection.
  Problem-ID:	3135

  
  

  Description:	Fixed-point divide exception in boot process.
  Symptom:	Kernel crashes with a fixed-point device exception.
  Problem:	The clock comparator interrupt is enabled before the clock comparator is set to its initial value. If the system is started without doing a system clear first, the clock comparator may still have an old value. The clock comparator can then interrupt too early.
  Solution:	Initialise clock comparator first, then enable the clock comparator interrupt.
  Problem-ID:	3137

  
  

  Description:	chandev configuration
  Symptom:	Argument errors when writing to /proc/chandev.
  Problem:	The parsing of the auto_msck and del_auto_msck verbs is broken because of missing breaks in a switch statement.
  Solution:	Add breaks.
  Problem-ID:	3139

  
  

  Description:	Many iucv devices.
  Symptom:	Deadlock when starting more than 160 iucv devices.
  Problem:	iucv_connect allocates an iparml_control structure to do the iucv connect. Between the allocation and the release of the structure an iucv_setmask is done which needs a iparml_control element too. If 160 iucv connection are started simultaneously all iparml_control structures are allocated and iucv_setmask loops indefinitly in grab_param.
  Solution:	Release iparml_control structure immediatly after connect.
  Problem-ID:	3140

  
  

  Description:	Module loader.
  Symptom:	Module load fails with error messages "init_module: changed module name ...".
  Problem:	There are two problem in the kernel module code. 1) A size-check in sys_create_module is off by one byte. 2) sys_init_module checks the module name using a buffer that might have been overwritten. This happens if the struct module used by insmod is larger than the one used by the kernel (e.g. modutils with the gcov patch).
  Solution:	Correct the two checks.
  Problem-ID:	3141

  
  

  Description:	noop elevator
  Symptom:	Performance improvement.
  Problem:	The dasd driver shouldn't use an elevator algorithm because the emulation of a dasd devices in the storage subsystems removes any potential for disk head optimization.
  Solution:	Enable the no-op elevator.
  Problem-ID:	3142

  
  

  Description:	vmalloc with user specified length.
  Symptom:	Error message "kernel BUG at vmalloc.c"
  Problem:	cio_ignore_proc_write calls vmalloc with an arbitrary user specified length. If the user passes a value that exceeds the memory size a BUG() is triggered in vmalloc.c.
  Solution:	Limit user specified length to 64K.
  Problem-ID:	3143

  
  

  Description:	memory management: dirty bit clearing.
  Symptom:	I/O errors on read only disks.
  Problem:	The dirty bit for a new page needs to get set to zero. So far this is done in mk_pte/set_pte. The call to mk_pte for the first user of a page sets a bit in the pte that causes set_pte to clear the dirty bit. This is a race condition if two processes want to access the same page simultaneously.
  Solution:	Move dirty bit clearing from mk_pte() to SetPageUptodate().
  Problem-ID:	3144

  
  

  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:	call init_waitqueue_head for kernel version >= 2.3.0
  Problem-ID:	3158

  
  

  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:	3231

  
  

  Description:	xpram parameter parsing.
  Symptom:	The xpram driver doesn't accept hexadecimal sizes on the xpram_parts parameter with a single digit after the 0x.
  Problem:	The check in xpram_int_format that determines if a number is in hexadecimal is broken.
  Solution:	Fix the check for hexadecimal numbers.
  Problem-ID:	3284

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)
  + linux-2.4.17-s390-9.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-5.diff (IBM)

• On-demand timer patch kernel 2.4.17 ("August 2001", 2003-07-07)

  linux-2.4.17-timer-5.tar.gz MD5 recommended (2003-07-07) (superseded)

  On demand timer patch:
  Contains a patch for the linux kernel 2.4.17 that changes the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The drawback is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_IDLE_HZ_TIMER that lets you choose between the old and the new behavior. Note that you'll need different qdio, qeth and tape_3590_mod modules if you use the no hz timer option.

  This patch is a complete replacement of the patch contained in linux-2.4.17-timer-4.tar.gz shipped on 2003-02-20.

  This patch is functionaly equivalent to the 2003-02-20 patch.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.17 patches on top of linux-2.4.17.tar.gz (see www.kernel.org) and as last patch

  + linux-2.4.17-timer-5.diff (IBM)

• qdio kernel 2.4.17 ("August 2001", 2003-07-07)

  31-bit: qdio-2.4.17-s390-6.tar.gz MD5 and qdio-2.4.17-s390-6-timer.tar.gz MD5 (2003-07-07) (superseded)

  64-bit: qdio-2.4.17-s390x-6.tar.gz MD5 and qdio-2.4.17-s390x-6-timer.tar.gz MD5 (2003-07-07) (superseded)

• The qdio 31-bit and 64-bit OCO-modules of 2003-07-07 are replacements for the 2003-02-20 recommended qdio modules.

• qeth kernel 2.4.17 ("August 2001", 2003-07-07)

  31-bit: qeth-2.4.17-s390-6.tar.gz MD5 and qeth-2.4.17-s390-6-timer.tar.gz MD5 (2003-07-07) (superseded)

  64-bit: qeth-2.4.17-s390x-6.tar.gz MD5 and qeth-2.4.17-s390x-6-timer.tar.gz MD5 (2003-07-07) (superseded)

• The qeth 31-bit and 64-bit OCO-modules of 2003-07-07 are replacements for the 2003-02-20 recommended qeth modules containing the below bug fixes.

  Description:	High percentage of dropped packets using UDP
  Symptom:	qeth had high percentage of dropped UDP packets running on VM in V=V mode and also in V=R mode
  Problem-ID:	2574

  
  

  Description:	qeth sent wrong command when doing ioctl
  Symptom:	When issueing SIOCDEVPRIVATE+2, a wrong command code was sent to the card
  Problem-ID:	2545

  
  

  Description:	Improper multicast IP housekeeping.
  Symptom:	Msg on interface shutdown, cannot delete multicast IP
  Problem-ID:	2090

• kernel 2.4.7 ("August 2001", 2003-07-07)
• • accumulated patch: linux-2.4.7-s390-14.tar.gz MD5 recommended(2003-07-07)
  • per-problem-patches: linux-2.4.7-s390-14-patches.tar.gz MD5 recommended (2003-07-07)

  These patches contain the following Linux kernel bug fixes:

  Description:	kernel: s390dbf - invalid call of create_proc_entry() within spin_lock_irqsave() section
  Symptom:	Kernel hang when registering a s390dbf view in low memory situations
  Problem:	It is not allowed to call kmalloc() with GFP_KERNEL when interrupts are disabled! create_proc_entry() calls kmalloc(). create_proc_entry() is called when interrupts are disabled.
  Solution:	Call create_proc_entry() before critical section is entered and before interrupts are disabled
  Problem-ID:	2719

  
  

  Description:	Address space switching instruction in user space does not fault.
  Symptom:	System crash due to cpus entering an endless program check loop.
  Problem:	A non-priviledged instruction which can change the primary space origin is not fenched correctly.
  Solution:	Set control register 5 to some value unequal to zero.
  Problem-ID:	2893

  
  

  Description:	dasd: Problems when echoing invalid devno to /proc/dasd/devices.
  Symptom:	Linux hangs when non-existing device is 'set off'.
  Problem:	The spinlock was not released in error path.
  Solution:	Release the spinlock.
  Problem-ID:	2927

  
  

  Description:	/proc/cio_ignore parsing.
  Symptom:	Piping various combinations of device ranges and device numbers to /proc/cio_ignore leads to "illegal operation" or "Trying to vfree() bad address".
  Problem:	Parser called from /proc/cio_ignore didn't work properly.
  Solution:	Backport working /proc/cio_ignore parser from 2.5.
  Problem-ID:	2934

  
  

  Description:	CTC: System hang on shutdown of remote OS/390
  Symptom:	Shutting down a remotely connected OS/390 system causes a system hang.
  Problem:	Receiving garbage data from remote was not properly handled.
  Solution:	Added additional validation of received data.
  Problem-ID:	2314

  
  

  Description:	Clearing of .bss section.
  Symptom:	Kernel compiled with gcc 3.3 doesn't work.
  Problem:	gcc 3.3 puts global variables with an initial value of zero to the .bss section. gcc < 3.3 puts these variables to the .data section. This makes a difference because the clearing of the .bss section is done after the store of the detected memory size to memory_size.
  Solution:	Move clearing of the .bss section before the memory detection.
  Problem-ID:	3135

  
  

  Description:	Fixed-point divide exception in boot process.
  Symptom:	Kernel crashes with a fixed-point device exception.
  Problem:	The clock comparator interrupt is enabled before the clock comparator is set to its initial value. If the system is started without doing a system clear first, the clock comparator may still have an old value. The clock comparator can then interrupt too early.
  Solution:	Initialise clock comparator first, then enable the clock comparator interrupt.
  Problem-ID:	3137

  
  

  Description:	chandev configuration
  Symptom:	Argument errors when writing to /proc/chandev.
  Problem:	The parsing of the auto_msck and del_auto_msck verbs is broken because of missing breaks in a switch statement.
  Solution:	Add breaks.
  Problem-ID:	3139

  
  

  Description:	Many iucv devices.
  Symptom:	Deadlock when starting more than 160 iucv devices.
  Problem:	iucv_connect allocates an iparml_control structure to do the iucv connect. Between the allocation and the release of the structure an iucv_setmask is done which needs a iparml_control element too. If 160 iucv connection are started simultaneously all iparml_control structures are allocated and iucv_setmask loops indefinitly in grab_param.
  Solution:	Release iparml_control structure immediatly after connect.
  Problem-ID:	3140

  
  

  Description:	Module loader.
  Symptom:	Module load fails with error messages "init_module: changed module name ...".
  Problem:	There are two problem in the kernel module code. 1) A size-check in sys_create_module is off by one byte. 2) sys_init_module checks the module name using a buffer that might have been overwritten. This happens if the struct module used by insmod is larger than the one used by the kernel (e.g. modutils with the gcov patch).
  Solution:	Correct the two checks.
  Problem-ID:	3141

  
  

  Description:	noop elevator
  Symptom:	Performance improvement.
  Problem:	The dasd driver shouldn't use an elevator algorithm because the emulation of a dasd devices in the storage subsystems removes any potential for disk head optimization.
  Solution:	Enable the no-op elevator.
  Problem-ID:	3142

  
  

  Description:	vmalloc with user specified length.
  Symptom:	Error message "kernel BUG at vmalloc.c"
  Problem:	cio_ignore_proc_write calls vmalloc with an arbitrary user specified length. If the user passes a value that exceeds the memory size a BUG() is triggered in vmalloc.c.
  Solution:	Limit user specified length to 64K.
  Problem-ID:	3143

  
  

  Description:	memory management: dirty bit clearing.
  Symptom:	I/O errors on read only disks.
  Problem:	The dirty bit for a new page needs to get set to zero. So far this is done in mk_pte/set_pte. The call to mk_pte for the first user of a page sets a bit in the pte that causes set_pte to clear the dirty bit. This is a race condition if two processes want to access the same page simultaneously.
  Solution:	Move dirty bit clearing from mk_pte() to SetPageUptodate().
  Problem-ID:	3144

  
  

  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:	call init_waitqueue_head for kernel version >= 2.3.0
  Problem-ID:	3158

  
  

  Description:	xpram parameter parsing.
  Symptom:	The xpram driver doesn't accept hexadecimal sizes on the xpram_parts parameter with a single digit after the 0x.
  Problem:	The check in xpram_int_format that determines if a number is in hexadecimal is broken.
  Solution:	Fix the check for hexadecimal numbers.
  Problem-ID:	3284

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)
  + linux-2.4.7-s390-14.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-7.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-6.diff (IBM)

• On demand timer ("August 2001", 2003-07-07)

  Release notes: Adaption to above 2003-07-07 kernel-patch

  linux-2.4.7-timer-7.tar.gz MD5 recommended(2003-07-07) (superseded)

  Category operating system.
  Contains a patch for the linux kernel 2.4.7 that changes the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The drawback is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_IDLE_HZ_TIMER that lets you choose between the old and the new behavior. Note that you'll need different qdio, qeth and tape_3590_mod modules if you use the no hz timer option.

  This patch is a complete replacement of the patch contained in linux-2.4.7-timer-6.tar.gz shipped on 2003-02-20.

  This patch is functionaly equivalent to the 2003-02-20 patch.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.7 patches on top of linux-2.4.7.tar.gz (see www.kernel.org) and as last patch

  + linux-2.4.7-timer-7.diff (IBM)

• Order-2 ("August 2001", 2003-07-07)

  linux-2.4.7-order2-6.tar.gz MD5 recommended (2003-07-07) (superseded)

  The "order 2 allocation relief" patch is a complete replacement of the recommended patch shipped on 2003-02-20.

  This patch is functionaly equivalent to the 2003-02-20 patch.

  The original patch decreased the kernel stack size to 8KB which turned out to be not enough.

  As a side-effect of this new patch there is no longer a need for special OCO-modules and the timer patch can be applied to the same kernel.
  • This patch is very s/390 specific, but doesn't break other architectures.
  • This patch does only work for a 64-bit Linux for zSeries kernel, but can also be applied if you intend to build a 31-bit kernel.
  • This patch is compatible with the "On-demand timer patch" and does not require special OCO modules.

  To create the complete linux kernel sources, apply all IBM kernel 2.4.7 patches on top of linux-2.4.7.tar.gz (see www.kernel.org) and as last patch
  + linux-2.4.7-order2-6.diff (IBM), or on top of linux-2.4.7-timer-7.diff (IBM) if timer is required.

• qdio kernel 2.4.7 ("August 2001", 2003-07-07)

  31-bit: qdio-2.4.7-s390-13.tar.gz MD5 and qdio-2.4.7-s390-13-timer.tar.gz MD5 (2003-07-07) (superseded)

  64-bit: qdio-2.4.7-s390x-13.tar.gz MD5 and qdio-2.4.7-s390x-13-timer.tar.gz MD5 (2003-07-07) (superseded)

The qdio 31-bit and 64-bit OCO-modules of 2003-07-07 are replacements for the 2003-02-20 recommended qdio modules.

• qeth kernel 2.4.7 ("August 2001", 2003-07-07)

  31-bit: qeth-2.4.7-s390-13.tar.gz MD5 and qeth-2.4.7-s390-13-timer.tar.gz MD5 (2003-07-07) (superseded)

  64-bit: qeth-2.4.7-s390x-13.tar.gz MD5 and qeth-2.4.7-s390x-13-timer.tar.gz MD5 (2003-07-07) (superseded)

• The qeth 31-bit and 64-bit OCO-modules of 2003-07-07 are replacements for the 2003-02-20 recommended qeth modules containing the below bug fixes.

  Description:	High percentage of dropped packets using UDP
  Symptom:	qeth had high percentage of dropped UDP packets running on VM in V=V mode and also in V=R mode
  Problem-ID:	2574

  
  

  Description:	qeth sent wrong command when doing ioctl
  Symptom:	When issueing SIOCDEVPRIVATE+2, a wrong command code was sent to the card
  Problem-ID:	2545

  
  

  Description:	Improper multicast IP housekeeping.
  Symptom:	Msg on interface shutdown, cannot delete multicast IP
  Problem-ID:	2090

• kernel 2.4.17 ("August 2001", 2003-04-16)

• • accumulated patch: linux-2.4.17-s390-8.tar.gz MD5 recommended (2003-04-16)
  • per-problem-patches: linux-2.4.17-s390-8-patches.tar.gz MD5 recommended (2003-04-16)

  Note: In addition to the usual tarball containing one large "accumulated" patch we now provide another tarball, containing a set of "per-problem-patches" which when combined correspond to the accumulated patch.

  These patches contain the following Linux kernel bug fixes:

  Description:	dasd: IFCC handling fixed
  Symptom:	IO errors after interface control check
  Problem:	dasd interrupt handler does recognize an interface control check and triggers the error recovery mechanism but does not provide sense data (none available) which cannot be handled by the error recovery.
  Solution:	retry the request
  Problem-ID:	2167

  
  

  Description:	dasd: discipline load order problem (with DIAG)
  Symptom:	CMS RESERVED minidisks are accessed via ECKD discipline even if dasd_diag module was loaded.
  Problem:	The discipline load order is responsible for the decision which discipline (ECKD or DIAG) is used to access CMS RESERVED minidisks.
  Solution:	Load DIAG always to the beginning. This means that DIAG is used as soon as the module is loaded.
  Problem-ID:	2256
  Note:	applicable for 31-bit Linux, only

  
  

  Description:	cio: Handling of not operational paths.
  Symptom:	Devices for which a path is not operational are not recognized.
  Problem:	Only deferred cc=3 was handled correcty; cc=3 on ssch() with a specified lpm was always treated as device not operational (this only happens on some models).
  Solution:	Make SensePGID and SetPGID handle cc=3 on ssch() correctly (switch off path and not device).
  Problem-ID:	2406

  
  

  Description:	cio: oopses from debug feature.
  Symptom:	Oops when looking at cio_msg dbf.
  Problem:	s390_displayhex2, which was supposed to dump data into sprintf feature, didn't work.
  Solution:	Replace s390_displayhex2 with directly dumping into cio_trace hex_ascii view.
  Problem-ID:	2409

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)
  + linux-2.4.17-s390-8.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-4.diff (IBM)

• kernel 2.4.7 ("August 2001", 2003-04-16)
• • accumulated patch linux-2.4.7-s390-13.tar.gz MD5 recommended (2003-04-16)
  • per-problem-patches: linux-2.4.7-s390-13-patches.tar.gz MD5 recommended (2003-04-16)

  Note: In addition to the usual tarball containing one large "accumulated" patch we now provide another tarball, containing a set of "per-problem-patches" which when combined correspond to the accumulated patch.

  These patches contain the following Linux kernel bug fixes:

  Description:	dasd: IFCC handling fixed
  Symptom:	IO errors after interface control check
  Problem:	dasd interrupt handler does recognize an interface control check and triggers the error recovery mechanism but does not provide sense data (none available) which cannot be handled by the error recovery.
  Solution:	retry the request
  Problem-ID:	2167

  
  

  Description:	dasd: discipline load order problem (with DIAG)
  Symptom:	CMS RESERVED minidisks are accessed via ECKD discipline even if dasd_diag module was loaded.
  Problem:	The discipline load order is responsible for the decision which discipline (ECKD or DIAG) is used to access CMS RESERVED minidisks.
  Solution:	Load DIAG always to the beginning. This means that DIAG is used as soon as the module is loaded.
  Problem-ID:	2256
  Note:	applicable for 31-bit Linux, only

  
  

  Description:	cio: Handling of not operational paths.
  Symptom:	Devices for which a path is not operational are not recognized.
  Problem:	Only deferred cc=3 was handled correcty; cc=3 on ssch() with a specified lpm was always treated as device not operational (this only happens on some models).
  Solution:	Make SensePGID and SetPGID handle cc=3 on ssch() correctly (switch off path and not device).
  Problem-ID:	2406

  
  

  Description:	cio: oopses from debug feature.
  Symptom:	Oops when looking at cio_msg dbf.
  Problem:	s390_displayhex2, which was supposed to dump data into sprintf feature, didn't work.
  Solution:	Replace s390_displayhex2 with directly dumping into cio_trace hex_ascii view.
  Problem-ID:	2409

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)
  + linux-2.4.7-s390-13.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-6.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-5.diff (IBM)

• kernel 2.4.17 ("August 2001", 2003-03-17)
• • accumulated patch: linux-2.4.17-s390-7.tar.gz MD5 recommended (2003-03-17)
  • per-problem-patches linux-2.4.17-s390-7-patches.tar.gz MD5 recommended (2003-03-17)

  Note: In addition to the usual tarball containing one large "accumulated" patch we now provide another tarball, containing a set of "per-problem-patches" which when combined correspond to the accumulated patch.

  These patches contain the following Linux kernel bug fixes:

  Description:	DASD devices will not be set 'online' on slow/fast systems.
  Symptom:	Root volume does not go online.
  Problem:	Bottom half raises DASD state before main path.
  Solution:	Extend scope of irq_lock to include change of state.
  Problem-ID:	1919

  
  

  Description:	Fixes for low memory emergency IDAL handling.
  Symptom:	Kernel might hang in low memory situations.
  Problem:	Possible memory overwrite during emergency idal creation.
  Solution:	Check if data fit into the available emergency IDAL page before writing them.
  Problem-ID:	2098
  Note:	applicable for 64-bit Linux, only

  
  

  Description:	DIAG250-disk on 64Bit system causes endless loop.
  Symptom:	System hang when accessing DASD with diag250.
  Problem:	Wrong preload of return code, used with diag250 exception.
  Solution:	Preload a value of 11 instead of 3, causing an I/O error.
  Problem-ID:	1341
  Note:	applicable for 64-bit Linux, only

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-s390-7.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.17-timer-4.diff (IBM)

• kernel 2.4.7 ("August 2001", 2003-03-17)
• • accumulated patch: linux-2.4.7-s390-12.tar.gz MD5 recommended (2003-03-17)
  • per-problem-patches linux-2.4.7-s390-12-patches.tar.gz MD5 recommended (2003-03-17)

  Note: In addition to the usual tarball containing one large "accumulated" patch we now provide another tarball, containing a set of "per-problem-patches" which when combined correspond to the accumulated patch.

  These patches contain the following Linux kernel bug fixes:

  Description:	DASD driver statistics backport from 2.4.17
  Symptom:	/proc/dasd/statistics is showing a bunch of zeros
  Problem:	Missing functionality.
  Solution:	Backport the functionality form 2.4.17 branch.
  Problem-ID:	1940

  
  

  Description:	DASD devices will not be set 'online' on slow/fast systems.
  Symptom:	Root volume does not go online.
  Problem:	Bottom half raises DASD state before main path
  Solution:	Extend scope of irq_lock to include change of state.
  Problem-ID:	1919

  
  

  Description:	Fixes for low memory emergency IDAL handling.
  Symptom:	Kernel might hang in low memory situations.
  Problem:	Possible memory overwrite during emergency idal creation.
  Solution:	Check if data fit into the available emergency IDAL page before writing them.
  Problem-ID:	2098
  Note:	applicable for 64-bit Linux, only

  
  

  Description:	DIAG250-disk on 64Bit system causes endless loop.
  Symptom:	System hang when accessing DASD with diag250.
  Problem:	Wrong preload of return code, used with diag250 exception.
  Solution:	Preload a value of 11 instead of 3, causing an I/O error.
  Problem-ID:	1341
  Note:	applicable for 64-bit Linux, only

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-s390-12.diff (IBM)

  Note: If On-demand timer is required, apply on top of above patches:
  + linux-2.4.7-timer-6.diff (IBM)

  Note: If Order-2 is required, apply as last patch (i.e. on top of On-demand timer patch if needed):
  + linux-2.4.7-order2-5.diff (IBM)

• kernel 2.4.17 ("August 2001", 2003-02-20)
• • accumulated patch: linux-2.4.17-s390-6.tar.gz MD5 recommended (2003-02-20)
  • per-problem-patches: linux-2.4.17-s390-6-patches.tar.gz MD5 recommended (2003-02-20)

  Note: In addition to the usual tarball containing one large "accumulated" patch we now provide another tarball, containing a set of "per-problem-patches" which when combined correspond to the accumulated patch.

  These patches contain the following Linux kernel bug fixes:

  Description:	64 bit xpram driver.
  Symptom:	64 bit systems only see odd numbered xpram devices.
  Problem:	The sizes array of the xpram driver is declared as 'unsigned long' but the block device layer accesses the array as 'unsigned int'.
  Solution:	Use the correct type for the sizes array.
  Problem-ID:	1928
  Note:	applicable for 64-bit Linux

  
  

  Description:	Crashes in copy_to_user.
  Symptom:	Kernel oops message.
  Problem:	The fixup routine __copy_to_user that is called after an unresolvable fault of the mvcle instruction accesses the program check old psw and the translation exception address fields in the lowcore. But the program check handler may have already called schedule and another process may have overwritten this information.
  Solution:	Don't rely on any information stored in the lowcore in the fixup routine of __copy_to_user.
  Problem-ID:	1923

  
  

  Description:	Codepage conversion problem.
  Symptom:	Input strings with certain length are not translated correctly.
  Problem:	codepage_convert for strings with n*256+1 bytes only convert (n-1)*256+1 bytes because of an incorrect branch instruction.
  Solution:	Correct branch instruction.
  Problem-ID:	1926

  
  

  Description:	TLBs not flushed under heavy swapping.
  Symptom:	Random memory corruption leading to program crashes or wrong data.
  Problem:	The __flush_tlb_mm function sets the cpu_vm_mask to the current cpu if it does a global flush. This is wrong in the case the flush is done for a different mm than the current one for the cpu. The next flush can fail to remove the tlb another cpu has created for this mm.
  Solution:	Reset cpu_vm_mask to the current cpu only if the mm is the active mm for this cpu and the cpu is the exclusive user for the mm.
  Problem-ID:	1924

  
  

  Description:	Status pending handling.
  Symptom:	Possibly all kinds of erratic behavior.
  Problem:	Upon encountering a cc=1 (status pending) condition when trying to start an I/O operation, Linux called the common interrupt handler to process the pending status, but couldn't call the registered interrupt handler. This could lead to interrupts not reported to the device driver which contained important information.
  Solution:	Only process cc=1 internally when doing sync. I/O; otherwise return -EBUSY and process the interrupt as soon as interrupts are enabled again.
  Problem-ID:	1844

  
  

  Description:	Path not operational handling.
  Symptom:	Paths with are fine appear as not operational.
  Problem:	When Linux encountered a deferred condition code 3, or another not operational situation, it considered the path designated in the last path used mask (lpum) to be not operational and switched it off. However, (1) the lpum shows the last *successfully* used path, and (2) deferred cc 3 doesn't necessarily mean the path is not operational.
  Solution:	Don't switch off paths for all devices, and switch off paths for a device only according to the path not operational mask (pnom).
  Problem-ID:	1614

  
  

  Description:	Zero sense data.
  Symptom:	Device drivers get confused by non-existent sense data.
  Problem:	Zero sense data was obtained by the common I/O layer, but the DEVSTAT_SENSE_AVAIL flag is set.
  Solution:	Reset DEVSTAT_SENSE_AVAIL if sense_count is zero.
  Problem-ID:	1615

  
  

  Description:	Basic sense return code.
  Symptom:	Zero sense data, lost interrupt information.
  Problem:	The common I/O layer didn't check if starting the basic sense ccw was successful and therefore didn't realize the next incoming interrupt didn't signify the successful completion of the basic sense operation.
  Solution:	Check return code of basic sense.
  Problem-ID:	1616

  
  

  Description:	Synchronous isc not correctly set.
  Symptom:	Linux runs into deadlock with all cpus in enable_cpu_sync_isc.
  Problem:	When msch() fails to set the sync isc in enable_cpu_sync_isc and encounters a status pending, s390_process_IRQ() is called while the syncio bit is set for the subchannel. I/O called from there assumes it is synchronous and has isc 5 exclusively, which is not true and can lead into another subchannel trying to get the sync_isc lock.
  Solution:	(1) Set the syncio flag only after a successful msch(). (2) Reset sync_isc_count and give up the sync_isc lock if sync isc is not set.
  Problem-ID:	1618

  
  

  Description:	'mt' causing more than 511 skip commands fails.
  Symptom:	Trying to skip more than 511 records or files with one 'mt' command will give an error message and cause the command to fail.
  Problem:	The tape driver cannot handle more than 511 repetitions without special handling.
  Solution:	Internally split these commands into several parts of 511.
  Problem-ID:	1554

  
  

  Description:	Fixes for ESS DASD device support.
  Symptom:	Various effects (from "not visible for user" up to "system hang").
  Problem:	Error recovery problems in ESS DASD specific scenarios.
  Solution:	Enhanced and fixed various ERP scenarios.
  Problem-ID:	1838

  
  

  Description:	Memory allocations not checked.
  Symptom:	Possible oopses or BUG()s (not observed yet).
  Problem:	Failure to check if an allocation was successful. Missing flags.
  Solution:	Check if allocation worked; clean up if not. Add GFP_ATOMIC.
  Problem-ID:	1892

  
  

  Description:	Handling of copy_to_user/copy_from_user return codes.
  Symptom:	ptrace returns positive numbers instead of -EFAULT if an invalid address is passed on the ptrace call.
  Problem:	copy_to_user/copy_from_user do not return an error code if they fail but the number of bytes not copied. This needs to be converted into -EFAULT.
  Solution:	Check return value of copy_to_user/copy_from_user and replace any non-zero return value with -EFAULT.
  Problem-ID:	1962

  
  

  Description:	munmap frees pages still in use.
  Symptom:	User process crashes and/or kernel oops in page_alloc.c.
  Problem:	sys_munmap for a mapping near the end of the address space frees pages still in use. This is caused by an address calculation overflow in free_pgtables.
  Solution:	Check for the overflow in free_pgtables.
  Problem-ID:	1233

  This patch contains an enhancement of the device driver for channel attached tape devices. It implements an infrastructure which allows to have different tape disciplines as separate Kernel modules. The generic tape driver (tape390) tries to automatically load the known tape disciplines. 3480 and 3490 tape disciplines are included in this patch. The 3590 tape discipline can be downloaded separately from this web site: tape_3590_mod. Basically this functionality is a backport of the May2002 tape driver. For documentation how to use this enhanced tape device driver please refer to "Chapter 5.Channel-attached tape device driver" of the "Linux for zSeries and S/390 Device Drivers and Installation Commands" manual of the May 2002 stream.

  This patch also contains the following backports from 2.4.19:
  • Update tape device driver to the same release as kernel 2.4.19 in the May 2002 stream. This is required in order to use the tape_3590_mod OCO module.
  • Add the z90crypt driver from the May 2002 stream
    Please refer to "Chapter 6.Generic cryptographic device driver" of the "Linux for zSeries and S/390 Device Drivers and Installation Commands" Documentation of the May 2002 stream for information on how to use this module.
  and some cosmetic changes.

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  

• Order-2 ("August 2001", 2003-02-20)

• linux-2.4.17-order2-2.tar.gz MD5 recommended (2003-02-20) (superseded)

  The "order 2 allocation relief" patch is a complete replacement of the patch contained in linux-2.4.17-order2-1.tar.gz shipped on 2002-03-18.

  This patch is functionally equivalent to the 2002-03-18 patch, but applies without warnings.

  Description:	Order 2 allocation relief
  Symptom:	Under stress and after long uptimes of a 64 bit system the error message "__alloc_pages: 2-order allocation failed." appears and either the fork of a new process fails or an active process dies.
  Problem:	The order 2 allocation problem is based in the size of the region and segment tables as defined by the zSeries architecture. A full region or segment table in 64 bit mode takes 16 KB of contiguous real memory. The page allocation routines do not guarantee that a higher order allocation will succeed due to memory fragmentation.
  Solution:	The order 2 allocation fix is supposed to reduce the number of order 2 allocations for the region and segment tables to a minimum. To do so it uses a feature of the architecture that allows to create incomplete region and segment tables. In almost all cases a process does not need full region or segment tables. If a full region or segment table is needed it is reallocated to the full size.

  
  
  • This patch is very s/390 specific, but doesn't break other architectures.
  • This patch does only work for a 64-bit Linux for zSeries kernel, but can also be applied if you intend to build a 31-bit kernel.
  • This patch is compatible with the "On-demand timer patch" and does not require special OCO modules.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)

• On demand timer ("August 2001", 2003-02-20)

  Release notes: Adaption to above 2003-02-20 kernel-patch

  linux-2.4.17-timer-4.tar.gz MD5 recommended (2003-02-20) (superseded)

  Category operating system.
  Contains a patch for the linux kernel 2.4.17 that will change the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The backdraw is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_HZ_TIMER that lets you choose between the old and the new behaviour.

  Note that you'll need different qdio, qeth and tape_3590_mod modules if you use the no hz timer option.

  This patch is a complete replacement of the patch contained in linux-2.4.17-timer-3.tar.gz shipped on 2002-06-17.

  This patch is functionaly equivalent to the 2002-06-17 patch, but applies without warnings.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)
  + linux-2.4.17-order2-2.diff (IBM)
  + linux-2.4.17-s390-6.diff (IBM)
  + linux-2.4.17-timer-4.diff (IBM)

• qdio kernel 2.4.17 ("August 2001", 2003-02-20)

  The qdio 31-bit and 64-bit OCO-modules of 2003-02-20 are replacements for the 2002-12-19 recommended qdio modules.

  31-bit: qdio-2.4.17-s390-5.tar.gz MD5 and qdio-2.4.17-s390-5-timer.tar.gz MD5 (2003-02-20) (superseded)

  64-bit: qdio-2.4.17-s390x-5.tar.gz MD5 and qdio-2.4.17-s390x-5-timer.tar.gz MD5 (2003-02-20) (superseded)

• qeth kernel 2.4.17 ("August 2001", 2003-02-20)

  The qeth 31-bit and 64-bit OCO-modules of 2003-02-20 are replacements for the 2002-12-19 recommended qeth modules.

  bit: qeth-2.4.17-s390-5.tar.gz MD5 and qeth-2.4.17-s390-5-timer.tar.gz MD5 (2003-02-20) (superseded)

  64-bit: qeth-2.4.17-s390x-5.tar.gz MD5 and qeth-2.4.17-s390x-5-timer.tar.gz MD5 (2003-02-20) (superseded)

• tape_3590_mod kernel 2.4.17 ("August 2001", 2003-02-20)

  Note: This OCO 3590 discipline module implements the 3590 specific parts of the Linux on zSeries tape driver. It can only be used in conjunction with the updated generic tape driver (tape390) which is included in the patch linux-2.4.17-s390-6.diff (Open Source). The generic tape driver tries to automatically load the 3590 discipline module. To be able to use this feature, the 3590 discipline module has to be named "tape_3590_mod.o".

  31-bit: tape3590-2.4.17-s390.tar.gz MD5 and tape3590-2.4.17-s390-timer.tar.gz MD5 (2003-02-20)

  64-bit: tape3590-2.4.17-s390x.tar.gz MD5 and tape3590-2.4.17-s390x-timer.tar.gz MD5 (2003-02-20)

• kernel 2.4.7 ("August 2001", 2003-02-20)
• • accumulated patch: linux-2.4.7-s390-11.tar.gz MD5 recommended (2003-02-20)
  • per-problem-patches: linux-2.4.7-s390-11-patches.tar.gz MD5 recommended (2003-02-20)

  Note: In addition to the usual tarball containing one large "accumulated" patch we now provide another tarball, containing a set of "per-problem-patches" which when combined correspond to the accumulated patch.

  These patches contain the following Linux kernel bug fixes:

  Description:	IPL from labeled tapes.
  Symptom:	The IPL from a labeled tape with an initial ramdisk doesn't work for a 64 bit kernel (on 31 bit the IPL succeeds after several retries).
  Problem:	The code to skip the HDR and EOF records of a labeled tapes loads the address of the initial ramdisk with an incorrect offset. The retry after a HDR or EOF record has been found loads the ramdisk to 0.
  Solution:	Load the address of the initial ramdisk from the correct memory location.
  Problem-ID:	1957
  Note:	applicable for 64-bit Linux

  
  

  Description:	Memory management: mprotect problem.
  Symptom:	Writes to memory areas that have been write protected with the mprotect system call do not cause segmentation faults.
  Problem:	A check for the VM_WRITE bit in the page fault handler is missing.
  Solution:	Add missing check.
  Problem-ID:	1958

  
  

  Description:	ptrace locking
  Symptom:	Crashes in kernel space or kernel hangs while using debugging tools like strace or gdb.
  Problem:	The traced process was not properly locked in sys_ptrace.
  Solution:	Add get_task_struct/free_task_struct calls in sys_ptrace.
  Problem-ID:	1959

  
  

  Description:	Floating point use in the 31 bit emulation.
  Symptom:	Floating point register contents of 31-bit emu applications get corrupted.
  Problem:	The 31-bit emu signal handler dispatch code clobbered floating point registers.
  Solution:	Do not use floating point arithmetic in kernel space.
  Problem-ID:	1961
  Note:	applicable for 64-bit Linux

  
  

  Description:	Handling of copy_to_user/copy_from_user return codes.
  Symptom:	ptrace returns positive numbers instead of -EFAULT if an invalid address is passed on the ptrace call.
  Problem:	copy_to_user/copy_from_user do not return an error code if they fail but the number of bytes not copied. This needs to be converted into -EFAULT.
  Solution:	Check return value of copy_to_user/copy_from_user and replace any non-zero return value with -EFAULT.
  Problem-ID:	1962

  
  

  Description:	System hang with unformatted dasd devices.
  Symptom:	fdasd on an unformatted dasd device causes a system hang.
  Problem:	BIODASDINFO ioctl accesses the request_queue of the device without checking if the request_queue has been initialized.
  Solution:	Access request_queue only if it was initialzed.
  Problem-ID:	1964

  
  

  Description:	Mount of unformatted dasd.
  Symptom:	Kernel panic after mounting an unformatted dasd device.
  Problem:	An unformatted dasd doesn't have a valid blocksize and the number of blocks is unknown. A register_disk of such a device causes the panic.
  Solution:	Check if blocksize and number of blocks is valid before calling register_disk.
  Problem-ID:	1965

  
  

  Description:	State change pending interrupts.
  Symptom:	Kernel panic.
  Problem:	If a state change pending interrupt comes in the dasd interrupt handler tries to restart the first request on the ccw queue. The request that got the long busy condition normally stays on the ccw queue but some special requests get removed by timeouts. In that case the request queue might be empty but the interrupt handler tries to access the head of the queue unconditionally.
  Solution:	Check if the ccw queue is empty before accessing it.
  Problem-ID:	1966

  
  

  Description:	Dasd partition check.
  Symptom:	System hang when dasd partitions are checked.
  Problem:	Large empty device ranges leads to system hang.
  Solution:	Fix race condition in dasd_enable_ranges.
  Problem-ID:	1967

  
  

  Description:	ctrl-c during format of dasd device.
  Symptom:	Kernel panic.
  Problem:	Unable to abort dasd formatting.
  Solution:	Fix race condition in dasd_sleep_on_request.
  Problem-ID:	1968

  
  

  Description:	Dynamic attach of diag dasd devices.
  Symptom:	Diag dasd device showing up as eckd dasd device.
  Problem:	Diag dasd devices do not get registered with the diag discipline when they are dynamically attached because the eckd discipline gets them first.
  Solution:	Try diag discipline before eckd discipline.
  Problem-ID:	1969

  
  

  Description:	Dynamic attach of dasd devices.
  Symptom:	The kernel loops when a dasd is defined under VM.
  Problem:	Deadlock in device bring-up.
  Solution:	Fix deadlock in device bring-up.
  Problem-ID:	1970

  
  

  Description:	Dasd autodetect.
  Symptom:	System hangs if dasd= parameter is missing.
  Problem:	For system with a huge device range the ipl needs a very long time.
  Solution:	Switched off autodetect/probeonly as default parameter.
  Problem-ID:	1971

  
  

  Description:	Kernel oops while formatting dasd.
  Symptom:	Segmentation fault in the dasd driver when an unformatted dasd device is disabled.
  Problem:	An unformatted dasd device doesn't not have a request_queue. dasd_disable_blkdev doesn't check if the request_queue pointer is valid.
  Solution:	Check for validity of device->request_queue before accessing its members in dasd_disable_blkdev.
  Problem-ID:	1972

  
  

  Description:	Crashes in copy_to_user.
  Symptom:	Kernel oops message
  Problem:	The fixup routine __copy_to_user that is called after an unresolvable fault of the mvcle instruction accesses the program check old psw and the translation exception address fields in the lowcore. But the program check handler may have already called schedule and another process may have overwritten this information.
  Solution:	Don't rely on any information stored in the lowcore in the fixup routine of __copy_to_user.
  Problem-ID:	1923

  
  

  Description:	Codepage conversion problem.
  Symptom:	Input strings with certain length are not translated correctly.
  Problem:	codepage_convert for strings with n*256+1 bytes only convert (n-1)*256+1 bytes because of an incorrect branch instruction.
  Solution:	Correct branch instruction.
  Problem-ID:	1926

  
  

  Description:	TLBs not flushed under heavy swapping.
  Symptom:	Random memory corruption leading to program crashes or wrong data.
  Problem:	The __flush_tlb_mm function sets the cpu_vm_mask to the current cpu if it does a global flush. This is wrong in the case the flush is done for a different mm than the current one for the cpu. The next flush can fail to remove the tlb another cpu has created for this mm.
  Solution:	Reset cpu_vm_mask to the current cpu only if the mm is the active mm for this cpu and the cpu is the exclusive user for the mm.
  Problem-ID:	1924

  
  

  Description:	Status pending handling.
  Symptom:	Possibly all kinds of erratic behavior.
  Problem:	Upon encountering a cc=1 (status pending) condition when trying to start an I/O operation, Linux called the common interrupt handler to process the pending status, but couldn't call the registered interrupt handler. This could lead to interrupts not reported to the device driver which contained important information.
  Solution:	Only process cc=1 internally when doing sync. I/O; otherwise return -EBUSY and process the interrupt as soon as interrupts are enabled again.
  Problem-ID:	1844

  
  

  Description:	Path not operational handling.
  Symptom:	Paths with are fine appear as not operational.
  Problem:	When Linux encountered a deferred condition code 3, or another not operational situation, it considered the path designated in the last path used mask (lpum) to be not operational and switched it off. However, (1) the lpum shows the last *successfully* used path, and (2) deferred cc 3 doesn't necessarily mean the path is not operational.
  Solution:	Don't switch off paths for all devices, and switch off paths for a device only according to the path not operational mask (pnom).
  Problem-ID:	1614

  
  

  Description:	Zero sense data.
  Symptom:	Device drivers get confused by non-existent sense data.
  Problem:	Zero sense data was obtained by the common I/O layer, but the DEVSTAT_SENSE_AVAIL flag is set.
  Solution:	Reset DEVSTAT_SENSE_AVAIL if sense_count is zero.
  Problem-ID:	1615

  
  

  Description:	Basic sense return code.
  Symptom:	Zero sense data, lost interrupt information.
  Problem:	The common I/O layer didn't check if starting the basic sense ccw was successful and therefore didn't realize the next incoming interrupt didn't signify the successful completion of the basic sense operation.
  Solution:	Check return code of basic sense.
  Problem-ID:	1616

  
  

  Description:	Synchronous isc not correctly set.
  Symptom:	Linux runs into deadlock with all cpus in enable_cpu_sync_isc.
  Problem:	When msch() fails to set the sync isc in enable_cpu_sync_isc and encounters a status pending, s390_process_IRQ() is called while the syncio bit is set for the subchannel. I/O called from there assumes it is synchronous and has isc 5 exclusively, which is not true and can lead into another subchannel trying to get the sync_isc lock.
  Solution:	(1) Set the syncio flag only after a successful msch(). (2) Reset sync_isc_count and give up the sync_isc lock if sync isc is not set.
  Problem-ID:	1618

  
  

  Description:	Fixes for ESS DASD device support.
  Symptom:	Various effects (from "not visible for user" up to "system hang").
  Problem:	Error recovery problems in ESS DASD specific scenarios.
  Solution:	Enhanced and fixed various ERP scenarios.
  Problem-ID:	1838

  
  

  Description:	Memory allocations not checked.
  Symptom:	Possible oopses or BUG()s (not observed yet).
  Problem:	Failure to check if an allocation was successful. Missing flags.
  Solution:	Check if allocation worked; clean up if not. Add GFP_ATOMIC.
  Problem-ID:	1892

  
  

  Description:	munmap frees pages still in use.
  Symptom:	User process crashes and/or kernel oops in page_alloc.c.
  Problem:	sys_munmap for a mapping near the end of the address space frees pages still in use. This is caused by an address calculation overflow in free_pgtables.
  Solution:	Check for the overflow in free_pgtables.
  Problem-ID:	1233

  This patch contains an enhancement of the device driver for channel attached tape devices. It implements an infrastructure which allows to have different tape disciplines as separate Kernel modules. The generic tape driver (tape390) tries to automatically load the known tape disciplines. 3480 and 3490 tape disciplines are included in this patch. The 3590 tape discipline can be downloaded separately from this web site: tape_3590_mod. Basically this functionality is a backport of the May2002 tape driver. For documentation how to use this enhanced tape device driver please refer to "Chapter 5.Channel-attached tape device driver" of the "Linux for zSeries and S/390 Device Drivers and Installation Commands" manual of the May 2002 stream.

  This patch also contains:
  
  • the following backports from 2.4.17:
  • • patch to enable multipathing with LVM.
    • dasd i/o timestamp support
    • enable setting of cache attributes (Sequential Prestage)
  
  
  • the following backports from 2.4.19:
  • • Update tape device driver to the same release as kernel 2.4.19 in the May 2002 stream. This is required in order to use the 3590 OCO module.
    • Add the z90crypt driver from the May 2002 stream
      Please refer to "Chapter 6.Generic cryptographic device driver" of the "Linux for zSeries and S/390 Device Drivers and Installation Commands" Documentation of the May 2002 stream for information on how to use this module.
  and some cosmetic changes.

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)

• On demand timer ("August 2001", 2003-02-20)

  Release notes: Adaption to above 2003-02-20 kernel-patch

  linux-2.4.7-timer-6.tar.gz MD5 (2003-02-20) (superseded)

  Category operating system.
  Contains a patch for the linux kernel 2.4.7 that will change the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The backdraw is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_HZ_TIMER that lets you choose between the old and the new behaviour. Note that you'll need different lcs and qeth modules if you use the no hz timer option.

  This linux-2.4.7-timer-6.tar.gz is a complete replacement for the already shipped timer patches:
  • linux-2.4.7-timer-5.tar.gz (2002-09-13)
  • linux-2.4.7-timer-4.tar.gz (2002-04-15)
  • linux-2.4.7-timer-3.tar.gz (2002-01-21)
  • linux-2.4.7-timer-2.tar.gz (2001-11-23)
  • linux-2.4.7-timer.tar.gz (2001-10-12)

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.tar.gz (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-timer-6.diff (IBM)

• Order-2 ("August 2001", 2003-02-20)

  linux-2.4.7-order2-5.tar.gz MD5 recommended (2003-02-20) (superseded)

  The "order 2 allocation relief" patch is a complete replacement of the recommended patch shipped on 2002-03-18.

  The original patch decreased the kernel stack size to 8KB which turned out to be not enough.

  As a side-effect of this new patch there is no longer a need for special OCO-modules and the timer patch can be applied to the same kernel.

  Description:	Order 2 allocation relief
  Symptom:	Under stress and after long uptimes of a 64 bit system the error message "__alloc_pages: 2-order allocation failed." appears and either the fork of a new process fails or an active process dies.
  Problem:	The order 2 allocation problem is based in the size of the region and segment tables as defined by the zSeries architecture. A full region or segment table in 64 bit mode takes 16 KB of contiguous real memory. The page allocation routines do not guarantee that a higher order allocation will succeed due to memory fragmentation.
  Solution:	The order 2 allocation fix is supposed to reduce the number of order 2 allocations for the region and segment tables to a minimum. To do so it uses a feature of the architecture that allows to create incomplete region and segment tables. In almost all cases a process does not need full region or segment tables. If a full region or segment table is needed it is reallocated to the full size.

  
  
  • This patch is very s/390 specific, but doesn't break other architectures.
  • This patch does only work for a 64-bit Linux for zSeries kernel, but can also be applied if you intend to build a 31-bit kernel.
  • This patch is compatible with the "On-demand timer patch" and does not require special OCO modules.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)
  + linux-2.4.7-s390-11.diff (IBM)
  + linux-2.4.7-order2-5.diff (IBM), or on top of linux-2.4.7-timer-6.diff (IBM) if timer is required.

• qdio kernel 2.4.7 ("August 2001", 2003-02-20)

  The qdio 31-bit and 64-bit OCO-modules of 2003-02-20 are replacements for the 2002-12-19 recommended qdio modules.

  31-bit: qdio-2.4.7-s390-12.tar.gz MD5 and qdio-2.4.7-s390-12-timer.tar.gz MD5 (2003-02-20) (superseded)

  64-bit: qdio-2.4.7-s390x-12.tar.gz MD5 and qdio-2.4.7-s390x-12-timer.tar.gz MD5 (2003-02-20) (superseded)

• qeth kernel 2.4.7 ("August 2001", 2003-02-20)

  The qeth 31-bit and 64-bit OCO-modules of 2003-02-20 are replacements for the 2002-12-19 recommended qeth modules.

  31-bit: qeth-2.4.7-s390-12.tar.gz MD5 and qeth-2.4.7-s390-12-timer.tar.gz MD5 (2003-02-20) (superseded)

  64-bit qeth-2.4.7-s390x-12.tar.gz MD5 and qeth-2.4.7-s390x-12-timer.tar.gz MD5 (2003-02-20) (superseded)

• tape_3590_mod kernel 2.4.7 ("August 2001", 2003-02-20)

  Note: This OCO 3590 discipline module implements the 3590 specific parts of the Linux on zSeries tape driver. It can only be used in conjunction with the updated generic tape driver (tape390) which is included in the patch linux-2.4.7-s390-11.diff (Open Source). The generic tape driver tries to automatically load the 3590 discipline module. To be able to use this feature, the 3590 discipline module has to be named "tape_3590_mod.o".

  31-bit: tape3590-2.4.7-s390.tar.gz MD5 and tape3590-2.4.7-s390-timer.tar.gz MD5 (2003-02-20)

  64-bit: tape3590-2.4.7-s390x.tar.gz MD5 and tape3590-2.4.7-s390x-timer.tar.gz MD5 (2003-02-20)

• s390-tools 1.0.6 ("August 2001", 2003-02-20)
  

  Category: operating system. Contains the source tree of a set of user space utilities that should to be used together with the zSeries and S/390 Linux kernel and device drivers.

  s390-tools-1.0.6-august2001.tar.gz MD5 recommended (2003-02-20)

  This version of the s390-tools consists out of the following accumulated patches:

  s390-tools.tar.gz (IBM)
  + s390-tools-1.diff (IBM)
  + s390-tools-2.diff (IBM)
  + s390-tools-3.diff (IBM)
  + s390-tools-4.diff (IBM)
  + s390-tools-5.diff (IBM)
  

  Besides these patches, the following changes are included in the s390-tools-1.0.6 package:

  Description:	Wrong VTOC bit for large DASD
  Symptom:	The z/OS tool IEHLIST fails on a CDL formatted 3390/9 DASD with rc 8.
  Problem:	The DS4DOSBT bit in the FMT4 DSCB of the VTOC was not set for large DASD.
  Solution:	Set DS4VTOCI in the FMT4 DSCB initially to 0xa0 instead to 0x20. This indicates an invalid FMT5 DSCB and to use the FMT7 DSCB (extended free space management)
  Problem-ID:	1861

  
  

  Description:	zgetdump does not complain if filesystem is full.
  Symptom:	It looks like dump has been copied successfully, but in fact it is not complete.
  Problem:	Error code of write() was not checked.
  Solution:	Check error code and write error message.
  Problem-ID:	1946

  
  

  Description:

  Added Multi Volume support for System Dump on 3590 tape devices.

  
  

  Description:

  Added shell script 'dbginfo.sh' (which collects information useful for debugging purposes) to s390-tools package.

  
  

  Description:

  Added tool 'tape390_display' to s390-tools package.

The qdio and qeth 31-bit and 64-bit OCO-modules of 2002-12-19 are replacements for the 2002-08-16 recommended qdio and qeth modules.

Recommended OCO modules 31-bit (superseded)

• qdio-2.4.17-s390-4.tar.gz MD5 and qdio-2.4.17-s390-4-timer.tar.gz MD5



• qeth-2.4.17-s390-4.tar.gz MD5 and qeth-2.4.17-s390-4-timer.tar.gz MD5

• qdio-2.4.17-s390x-4.tar.gz MD5 and qdio-2.4.17-s390x-4-timer.tar.gz MD5



• qeth-2.4.17-s390x-4.tar.gz MD5 and qeth-2.4.17-s390-4-timer.tar.gz MD5

The qdio and qeth 31-bit and 64-bit OCO-modules of 2002-12-19 are replacements for the 2002-08-16 recommended qdio and qeth modules.

Recommended OCO modules 31-bit (superseded)

• qdio-2.4.7-s390-11.tar.gz MD5 and qdio-2.4.7-s390-11-timer.tar.gz MD5



• qeth-2.4.7-s390-11.tar.gz MD5 and qeth-2.4.7-s390-11-timer.tar.gz MD5

• qdio-2.4.7-s390x-11.tar.gz MD5 and qdio-2.4.7-s390x-11-timer.tar.gz MD5



• qeth-2.4.7-s390x-11.tar.gz MD5 and qeth-2.4.7-s390x-11-timer.tar.gz MD5

• linux-2.4.17-s390-5.tar.gz MD5 recommended (2002-11-25)

• Description:	Tape attach fails.
  Symptom:	Linux hangs after a tape attach, or an attached tape is not recognized.
  Problem:	Msch in enable_subchannel encounters a pending status first; a second msch succeeds, but the return code is still -EIO.
  Solution:	Set the return code to 0 after a successful msch.

  
  

  Description:	Unsolicited interrupts.
  Symptom:	Dasd reports an unsolicited interrupt.
  Problem:	The I/O layer detected a condition code 3 situation during a SetPGID and erroneously called dasd's interrupt handler.
  Solution:	Don't call the device driver's interrupt handler when a "device/path not operational" situation occurs during an internal I/O.

  
  

  Description:	Hang on 64 bit.
  Symptom:	Possible hangs on 64 bit systems.
  Problem:	Flags variable in read_dev_chars is too short.
  Solution:	Change flags variable to unsigned long.

  
  

  Description:	Linux hangs.
  Symptom:	Possible hang when loading a device driver (not observed yet).
  Problem:	Read_dev_chars and read_conf_data leave interrupts disabled on error.
  Solution:	Do __restore_flags() in both cases

  
  

  Description:	Path grouping fails.
  Symptom:	Path groups are not correctly set, leading to "Unexpected error 0" messages in /proc/s390dbf/cio_msg/sprintf.
  Problem:	Incorrect check for errors in DevicePathVerification.
  Solution:	Correctly check for errors in DevicePathVerification.

  
  

  Description:	Deferred cc 3 handling.
  Symptom:	Linux fails to detect devices after 'not operational' messages.
  Problem:	After a deferred cc 3 in SensePGID, Linux failed to try path grouping for other paths.
  Solution:	Correctly retry after 'not operational' conditions.

  
  

  Description:	LCS does not compile with gcc 3.2
  Symptom:	Compile error in lcs.c
  Problem:	lcs uses '#if BUG' (BUG is a kernel macro)
  Solution:	Use '#if 0' instead

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)
  + linux-2.4.17-s390-5.diff (IBM)

• linux-2.4.7-s390-10.tar.gz MD5 recommended (2002-11-25)

• Description:	Hangs after machine checks.
  Symptom:	Linux hangs after a device is gone.
  Problem:	S390_free_irq tried synchronous halt_IO on the subchannel, but no interrupt was reported back.
  Solution:	Don't do synchronous halt_IO in s390_free_irq.

  
  

  Description:	Tape attach fails.
  Symptom:	Linux hangs after a tape attach, or an attached tape is not recognized.
  Problem:	Msch in enable_subchannel encounters a pending status first; a second msch succeeds, but the return code is still -EIO.
  Solution:	Set the return code to 0 after a successful msch.

  
  

  Description:	Unsolicited interrupts.
  Symptom:	Dasd reports an unsolicited interrupt.
  Problem:	The I/O layer detected a condition code 3 situation during a SetPGID and erroneously called dasd's interrupt handler.
  Solution:	Don't call the device driver's interrupt handler when a "device/path not operational" situation occurs during an internal I/O.

  
  

  Description:	Hang on 64 bit.
  Symptom:	Possible hangs on 64 bit systems.
  Problem:	Flags variable in read_dev_chars is too short.
  Solution:	Change flags variable to unsigned long.

  
  

  Description:	Linux hangs.
  Symptom:	Possible hang when loading a device driver (not observed yet).
  Problem:	Read_dev_chars and read_conf_data leave interrupts disabled on error.
  Solution:	Do __restore_flags() in both cases.

  
  

  Description:	Path grouping fails.
  Symptom:	Path groups are not correctly set, leading to "Unexpected error 0" messages in /proc/s390dbf/cio_msg/sprintf are "Unexpected error 0" messages.
  Problem:	Incorrect check for errors in DevicePathVerification.
  Solution:	Correctly check for errors in DevicePathVerification.

  
  

  Description:	Deferred cc 3 handling.
  Symptom:	Linux fails to detect devices after 'not operational' messages.
  Problem:	After a deferred cc 3 in SensePGID or SetPGID, Linux failed to try path grouping for other paths.
  Solution:	Correctly retry after 'not operational' conditions.

  
  

  Description:	LCS does not compile with gcc 3.2
  Symptom:	Compile error in lcs.c
  Problem:	lcs uses '#if BUG' (BUG is a kernel macro)
  Solution:	Use '#if 0' instead

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-s390-10.diff (IBM)

• linux-2.4.7-s390-9-extfix.tar.gz MD5 recommended (2002-09-13)

• Description:	DIAG access to CMS reserved minidisks clashes with PFAULT support
  Symptom:	Endlessly looping system.
  Problem:	DIAG and PFAULT share the same external interrupt 0x2603. Because PFAULT is initialized before kmalloc works the registration code keeps a static buffer for the registration of the pfault interrupt handler. Since DIAG uses the same external interrupt number the same static buffer is used for both interrupt handlers. This create a loop in the interrupt chain causing the system to loop.
  Solution:	Add two functions [un]register_early_external_interrupt and use these functions for early registration of external interrupts. The two new functions require the static buffer to be passed to them. This prevents that DIAG and PFAULT use the same static buffer.

  Everybody should apply this patch.

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.diff (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)

• linux-2.4.7-timer-5.tar.gz MD5 recommended (2002-09-13) (superseded)

• Release notes: (2002-09-13: adaption to above 2002-09-13 kernel-patch)
  On demand timer patch Category operating system. Contains a patch for the linux kernel 2.4.7 that will change the timing method from the regular 100 hz interrupts to on demand timer interrupts. This saves some cpu cycles in an idle linux image. The backdraw is that a busy linux image will do a small amount of additional work every time the switch between user mode and kernel mode is done. In short if you are running many images under VM the on demand timers are useful but you probably don't want to use it running under LPAR or native. The patch introduces a configuration option CONFIG_NO_HZ_TIMER that lets you choose between the old and the new behaviour. Note that you'll need different lcs and qeth modules if you use the no hz timer option.

  This linux-2.4.7-timer-5.tar.gz is a complete replacement for the already shipped timer patches:
  • linux-2.4.7-timer-4.tar.gz (2002-04-15)
  • linux-2.4.7-timer-3.tar.gz (2002-01-21)
  • linux-2.4.7-timer-2.tar.gz (2001-11-23)
  • linux-2.4.7-timer.tar.gz (2001-10-12)

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

  linux-2.4.7.tar.gz (see www.kernel.org)
  + linux-2.4.7-s390.diff (IBM)
  + linux-2.4.7-s390-1.diff (IBM)
  + linux-2.4.7-s390-2.diff (IBM)
  + linux-2.4.7-s390-3.diff (IBM)
  + linux-2.4.7-s390-4.diff (IBM)
  + linux-2.4.7-s390-5.diff (IBM)
  + linux-2.4.7-s390-6-lcs.diff (IBM)
  + linux-2.4.7-s390-7.diff (IBM)
  + linux-2.4.7-s390-8-iucv.tar.gz (IBM)
  + linux-2.4.7-s390-9-extfix.diff (IBM)
  + linux-2.4.7-timer-5.diff (IBM)
  

• linux-2.4.17-s390-4-iucv.tar.gz MD5 recommended (2002-08-16)

• This is a backport of the latest fixes in the linux IUCV driver to linux 2.4.17.

  Corrected 2002-09-18 to apply in the standard manner.

  It addresses a patch by David Kennedy <dkennedy@linuxcare.com> which eliminates a race condition during initialization.

  David's patch however, does introduce another SERIOUS problem: When running on a guest with more than one CPU it can CRASH YOUR VM!!!
  This has been fixed with this patch.

  Everybody should apply this patch.

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

  linux-2.4.17.tar.gz (see www.kernel.org)
  + linux-2.4.17-s390.diff (IBM)
  + linux-2.4.17-s390-1-lcs.diff (IBM)
  + linux-2.4.17-s390-2.diff (IBM)
  + linux-2.4.17-s390-3.diff (IBM)
  + linux-2.4.17-s390-4-iucv.diff (IBM)