Kernel 3.0

If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.

Kernel downloads for the "Development stream"

Download Description
upstream kernel 3.0 kernel 3.0 - upstream with feature descriptions.
linux-3.0-s390-message-catalog.tar.gz / MD5 "Development Stream" kernel 3.0 - message-catalog (optional)

2011-08-31: kernel 3.0 - upstream (feature description)

Note that kernel 3.0 would have been 2.6.40 if the versioning scheme had not changed.

To download the linux-3.0.tar.gz visit:

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.0 contains the following functionality developed by the Linux on System z development team:

kernel: Identifying the System z hardware
This features provides information to identify the particular hardware system on which a Linux instance is running. There are two new sysfs attributes that contain the CPC name and the network name of the machine. This information is useful in high availability configurations with multiple System z machines.

This support is available only, when running Linux on System z in an LPAR.

See Device Drivers, Features, and Commands, Chapter "Identifying the System z hardware".

kernel: Exploit z196 hardware-accelerated crypto algorithms
Add support for the new CPACF algorithms supported by z196 to the in-kernel crypto subsystem. The new hardware accelerated algorithms are:
  • CTR mode for AES
  • CTR mode for AES and 3DES
  • CTR mode for AES with key lengths of 128 and 256 bits
  • GHASH message digest for GCM mode

The hardware functionality is only available since z196.

cio: Handle channel path description changes
With this feature, the common I/O layer handles dynamic IODF changes that result in changed capabilities of channel paths.

This support is available only, when running Linux on System z in an LPAR.

kernel: Remove data execution protection
Data execution protection support relies on the assumption that the CPU will always use the secondary space for data accesses while it is running in the secondary space mode, which was the case for System z until z9.

As this is no longer the case since the introduction of z10, binaries compiled with march=z10 (or later) are incompatible with the data execution protection support. Therefore, data execution protection was removed.

Data execution protection support for Linux on System z was introduced for kernel 2.6.16.

The chapter "Data execution protection for user processes" has been removed from Device Drivers, Features, and Commands.

qeth: Add OSA concurrent hardware trap
To improve problem determination (FFDC: first failure data capture) the qeth driver now requests a hardware trace when the device driver or the hardware detect an error, allowing correlation between OSA- and Linux on System z-traces. Furthermore, a new user command interface to capture a hardware trace is provided.

This feature is not available for VM emulated devices (GuestLAN or VSWITCH).

See Device Drivers, Features, and Commands, section "Capturing a hardware trace" in Chapter "qeth device driver for OSA-Express (QDIO) and HiperSockets".

2011-08-31: "Development Stream" kernel 3.0 message catalog (feature - optional patch)

linux-3.0-s390-message-catalog.tar.gz / MD5 ... recommended (2011-08-31)

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'.