- 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 3.11||kernel 3.11 - upstream with feature descriptions.|
|linux-3.11-s390-message-catalog.tar.gz / MD5||"Development Stream" kernel 3.11 - message-catalog (optional)|
To download the linux-3.11.tar.gz visit: http://www.kernel.org/pub/linux/kernel/v3.x
The upstream kernel 3.11 contains the following functionality developed by the Linux on System z development team:
- sclp: improve robustness of the sclp line mode console
The sclp line mode console relies on I/O to the service element for the reads and writes to the console.
In case of an outage of the service element the sclp line mode driver has a fixed number of output buffers to store console message until the service element is available again.
To prevent CPUs from blocking if the output buffers are full two new parameters are added, sclp_con_pages to specify the number of output buffers to allocate and sclp_con_drop to allow console messages to be dropped to make room for new messages.
For details see Device Drivers, Features, and Commands, Chapter 'Console Device Drivers', section 'Setting up the console device drivers'.
- zfcp: remove access control tables interface
This patch removes an interface that was used to manage access control tables within the HBA and removes consequently the handling for conditions related to those access control tables.
That initiator-based access control feature was only needed until the introduction of NPIV and was withdrawn with z10 years ago.
For details see Device Drivers, Features, and Commands, Chapter 'SCSI-over-Fibre Channel device driver', section 'Working with SCSI devices' and Kernel Messages, Chapter 'zfcp'.
- zfcp: module parameter dbflevel for early debugging
With the new zfcp module parameter "dbflevel", you can choose a non-default log level for zfcp device driver trace messages.
This enables early debugging, e.g. before an FCP device is set online for the first time since boot.
This complements the already existing module parameter dbfsize to choose a non-default number of pages for each trace area of each FCP device.
For details see Device Drivers, Features, and Commands, Chapter 'SCSI-over-Fibre Channel device driver', sections 'zfcp device driver kernel parameters' and 'zfcp module parameters'.
- qeth: Increase default MTU
Increases the default MTU size for OSA Layer 2 devices (real and vNICs) from 1492 to 1500 bytes.
For details see Device Drivers, Features, and Commands, Chapter 'qeth device driver for OSA-Express (QDIO) and HiperSockets', section 'Activating an interface'.
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'.