- 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 3.3||kernel 3.3 - upstream with feature descriptions.|
|linux-3.3-s390-message-catalog.tar.gz / MD5||"Development Stream" kernel 3.3 - message-catalog (optional)|
To download the linux-3.3.tar.gz visit: http://www.kernel.org/pub/linux/kernel/v3.x
Since kernel 2.6.35, no more kernel kerntypes-patches (required for work with lcrash, from lkcdutils/LKCD) are provided: Use crash instead of lcrash.
The upstream kernel 3.3 contains the following functionality developed by the Linux on System z development team:
- kernel: add support for physical memory > 4TB
- Increase the maximum amount of memory a 64 bit kernel can utilize from 4 TB to 64 TB.
Memory sizes larger than 4 TB require a 4 level page table for the kernel address space which makes memory accesses by the kernel slightly slower.
The kernel will automatically choose the appropriate number of page table levels for a given memory size, 3 levels for up to 4 TB of memory, or 4 levels for bigger sizes.
- netiucv: allow multiple paths between the same Linux on System z instances
- The NETIUCV device driver allows to connect a Linux guest on z/VM to another z/VM guest based on the z/VM communication facility IUCV. Multiple output paths to different guests are possible, as well as multiple input paths from different guests.
With this feature, you can configure multiple point-to-point NETIUCV interfaces between your Linux on System z instance and another z/VM guest.
For details see Device Drivers, Features, and Commands, Chapter "NETIUCV device driver".
- dasd: add sanity check to detect path connection error
With this feature, the DASD device driver checks whether all available paths to a DASD lead to the same physical device as identified by a UID. This feature can help to detect cabling errors.
In case of an incorrect hardware configuration the paths assigned to a specific subchannel may actually lead to different storage servers. This can not be detected by hardware or microcode and would lead to data corruption on the DASD device.
The DASD device driver is now able to detect the mis-configuration and prevent data corruption, using a checking method which uses the unique identifier UID to detect a mis-cabling.
- oprofile: Add event interface to the System z hardware sampling module
OProfile 0.9.8 will provide the user space interface to support the CPU measurement facility (as available since z10) in a more convenient manner. It will be possible to configure the hardware sampling through the OProfile event interface as described in the OProfile manual.
This kernel feature provides the required interface.
Note that this feature can only be used when running Linux on System z in LPAR.
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'.