- 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
If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.
|upstream kernel 3.5||kernel 3.5 - upstream with feature descriptions.|
|linux-3.5-s390-message-catalog.tar.gz / MD5||"Development Stream" kernel 3.5 - message-catalog (optional)|
To download the linux-3.5.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.5 contains the following functionality developed by the Linux on System z development team:
- Fuzzy Live Dump: Used for creating non-disruptive kernel dumps on a running Linux system using the zgetdump tool
Sometimes a kernel dump of a Linux system is required for debugging purposes but no down-time is acceptable.
The most common scenario for this is that a Linux system can still provide the required service, even there are kernel or device driver problems that need analysis of kernel memory.
For details see Using the Dump Tools, Chapter 'Creating live-system dumps with zgetdump'.
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'.