 |
Kernel 2.4 based: June 2003 stream
|
 |
|
|
|
|
jump to next patch
jump
to xref jump to Download
Area
If you download any software from this web site please be aware of the
Warranty Disclaimer and Limitation of Liabilities.
linux-2.4.21-s390-11-june2003.tar.gz
/ MD5 ... accumulated patch, recommended (2004-03-24)
linux-2.4.21-s390-11-june2003-patches.tar.gz
/ MD5 ... per-problem-patches, recommended (2004-03-24)
These patches contain the following linux kernel bug fixes:
| Description: |
cmm: Adressing exception in collaborative memory management (cmm). |
| Symptom: |
Adressing exception when using cmm with more than 2047MB of
storage. |
| Problem: |
The diag10 used to indicate to VM that a page is now unused
can only be used if the page resides below 2047 MB. |
| Solution: |
Add an if statement to avoid the diag10 if the allocated pages
reside above 2047MB. |
| Problem-ID: |
- |
| Note: |
applicable for 64-bit Linux, only |
| Description: |
cmm: Missing default value for configuration option |
| Symptom: |
Make oldconfig waits for user input |
| Problem: |
Missing config option CONFIG_CMM_IUCV |
| Solution: |
Add missing config option CONFIG_CMM_IUCV to defconfig |
| Problem-ID: |
- |
| Description: |
dasd: Duplicate device entry in /proc/dasd/devices |
| Symptom: |
The first devno can be added more than once.
The additional entries showing up as 'unknown' in
/proc/dasd/devices and they waste major/minor numbers. |
| Problem: |
dasd_devindex_from_devno returns '0' for the first device entry
but dasd_add_range checks for '> 0' to determine if the devindex
is valid. |
| Solution: |
Check for '>= 0' as a valid devindex. |
| Problem-ID: |
6511 |
| Description: |
dasd: problems when setting a DASD device online/offline |
| Symptom: |
No request IRQ message during device bring-up.
Sometimes a kernel panic. |
| Problem: |
CIO does a path verification (during request_IRQ) which calls the
DASD oper_handler. This leads to a second thread trying to get
device online without synchronization (race condition). |
| Solution: |
The DASD oper_handler has to trigger device bring-up only if
the device is really down. |
| Problem-ID: |
6608 |
| 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/oiucv/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.21-s390-09-june2003.diff (2004-01-30). |
| Description: |
qeth: incorrect source MAC addresses |
| Symptom: |
Inbound source MAC address incorrect with fake_ll |
| Problem: |
Source MAC address was copied from wrong place |
| Solution: |
Copy source MAC from right place |
| Problem-ID: |
6097 |
| Description: |
sclp: Console driver causes bottom-half handling despite
disabled interrupts. |
| Symptom: |
Deadlock situations in various drivers (e.g. LVM) when there is
a lot of console output. |
| Problem: |
When the console buffer is full, SCLP opens up interupts and
waits synchronously for an external interrupt. After the
interrupt occured, the bottom half is erroneously handled. |
| Solution: |
Disable bottom-half handling while waiting for the interrupt. |
| Problem-ID: |
6617 |
| Description: |
sclp: VM guests receiving a signal shutdown may not logoff
correctly. |
| Symptom: |
Invoking a 'signal shutdown' command on a 64 bit VM guest will
sometimes not log off a VM guest, even though Linux is shut down
correctly. |
| Problem: |
On 64 bit systems, SMP function signal_processor_ps stores a
64 bit value at a 32 bit location. As a result, the signal
quiesce sense loop is rendered ineffective. |
| Solution: |
Correct respective parameter type of signal_processor_ps. |
| Problem-ID: |
6760 |
| Note: |
applicable for 64-bit Linux, only |
| Description: |
z90crypt fails to detect devices in domain 15 |
| Symptom: |
If PCICCs or PCIXCCs are present only in domain 15, they
are not found |
| Problem: |
Domain 15 was being ignored |
| Solution: |
Include domain 15 in search for devices |
| Problem-ID: |
6842 |
| Description: |
z90crypt: Unneeded message "Error in get_crypto_request_buffer: 16" |
| Symptom: |
Unneeded message "Error in get_crypto_request_buffer: 16" |
| Problem: |
Issuing error message when it is not appropriate |
| Solution: |
remove error message |
| Problem-ID: |
6855 |
Everybody should apply this patch.
To create the complete linux kernel sources, the following
patches need to be applied in sequence:
linux-2.4.21.tar.gz (see www.kernel.org)
+ linux-2.4.21-s390-june2003.diff (IBM)
+ linux-2.4.21-s390-01-june2003.diff (IBM)
+ linux-2.4.21-s390-02-june2003.diff (IBM)
+ linux-2.4.21-s390-03-june2003.diff (IBM)
+ linux-2.4.21-s390-04-june2003.diff (IBM)
+ linux-2.4.21-s390-05-june2003.diff (IBM)
+ linux-2.4.21-s390-06-june2003.diff (IBM)
+ linux-2.4.21-s390-07-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-09-june2003.diff (IBM)
+ linux-2.4.21-s390-10-june2003.diff (IBM)
+ xip2fs1 (see linuxvm.org/patches/index.html)
+ xip2fs2 (see linuxvm.org/patches/index.html)
+ linux-2.4.21-s390-11-june2003.diff (IBM)
Note: If On-demand timer is required, apply as last patch:
+ linux-2.4.21-s390-timer-03-june2003.diff (IBM)
|
|
|
|
|
