- 2016-08-24: kernel 4.7
- 2016-08-24: kernel 4.6
- 2016-07-21: kernel 4.5
- 2016-04-21: kernel 4.4
- 2016-02-02: kernel 4.3
- 2015-09-18: kernel 4.2
- 2015-09-18: kernel 4.1
- 2015-07-10: kernel 4.0
- 2015-06-01: kernel 3.19
- 2015-04-08: kernel 3.18
- 2015-02-20: kernel 3.17
- 2014-12-12: kernel 3.16
- 2014-09-19: kernel 3.14
- 2014-01-08: kernel 3.12
- 2013-10-31: kernel 3.11
- 2013-07-31: kernel 3.10
- 2013-06-12: kernel 3.9
- 2013-02-28: kernel 3.8
- 2012-12-19: kernel 3.7
- 2012-11-05: kernel 3.5
- 2012-06-13: kernel 3.4
- 2012-03-31: kernel 3.3
- 2012-02-29: kernel 3.2
- 2011-11-30: kernel 3.1
- 2011-08-31: kernel 3.0
- 2011-06-30 kernel 2.6.39
- 2011-05-19 kernel 2.6.38
- 2011-01-27 kernel 2.6.37
- 2010-10-22 kernel 2.6.36
- 2010-09-16 kernel 2.6.35
- 2010-05-28 kernel 2.6.34
- 2010-03-12 kernel 2.6.33
- 2009-12-11 kernel 2.6.32
- 2009-09-23 kernel 2.6.31
- 2009-05-08 kernel 2.6.29
- 2008-11-25 kernel 2.6.27
- 2008-05-07 kernel 2.6.25
If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.
|upstream kernel 2.6.35||kernel 2.6.35 - upstream with feature descriptions.|
|linux-2.6.35-s390-message-catalog.tar.gz / MD5||"Development Stream" kernel 2.6.35 - message-catalog (optional)|
To download the linux-2.6.35.tar.gz visit: http://www.kernel.org/pub/linux/kernel/v2.6
Starting with kernel 2.6.35, no more kernel kerntypes-patches (which are required for work with lcrash, from lkcdutils/LKCD) will be provided: Use crash instead of lcrash.
The upstream kernel 2.6.35 contains the following functionality developed by the Linux on System z development team:
- dasd: Dynamic PAV toleration
- Tolerate dynamic Parallel Access Volume (PAV) changes for base PAV: PAV changes in the hardware configuration are detected and the mapping of base and alias devices in Linux is adjusted accordingly.
Refer to How to Improve Performance with PAV (kernel 2.6.35) for details.
- kernel: Breaking-event-address for user space programs
- Record breaking-event-addresses for user space processes. A breaking-event-address is the last instruction to cause a break in the sequential execution of a CPU. The recorded addresses are valuable debugging data and can be read with the ptrace interface.
This function requires hardware capabilities available with z10 or later.
- qeth: support new CHPIDs OSX and OSM introduced with z196
- The z196 introduces two new CHPID types:
With this feature, qeth recognizes these CHPIDs and handles them appropriately.
Note: znetconf in s390-tools 1.10.0 supports OSX and OSM CHPIDs.
- qeth: Offload Outbound Checksumming to OSA within qeth driver
- TCP and UDP use checksumming to ensure data integrity. Calculating the checksum adds significant CPU load to the host processor. Therefore the OSA card supports offloading the calculation of the TCP/UDP checksum from the host CPU to the OSA network card.
This feature adds support to the qeth device driver to enable hardware send checksumming and avoid calculating the checksum on the host CPU.
- qeth: Optimized Latency Mode (OLM) toleration
- z/OS may activate Optimized Latency Mode (OLM) for a connection through an OSA Express3 adapter, which reduces the number of allowed concurrent connections, when adapter is used in shared mode. If activation of an OSA-connection fails due to an active OLM-connection on the shared OSA-adapter, qeth now issues a meaningful message.
This patch contains:
- Kernel message catalog.
- Add support for automatic message tags to the printk macro families dev_xyz and pr_xyz. The message tag consists of a component name and a 24 bit hash of the message text. For each message that is documented in the included kernel message catalog a man page can be created with a script (which is included in the patch). The generated man pages contain explanatory text that is intended to help understand the messages.
Note that only s390 specific messages are prepared appropriately and included in the generated message catalog.
This patch is optional as it is very unlikely to be accepted in upstream kernel, but is recommended for all distributions which are built based on the 'Development stream'.