Kernel 2.6 based: October 2005 stream
If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.
Category: operating system. Contains the source tree of a set of user space utilities that should to be used together with the Linux on System z kernel and device drivers.
These s390-tools-1.6.2 (applicable for the "October 2005 stream") replace s390-tools-1.6.1.
Added new tools:
- chchp: Tool to modify channel-path state.
- lschp: Tool to list information about available channel-paths.
- mon_procd: Daemon that writes process information data to the z/VM monitor stream.
- vmur: Tool to work with z/VM spool file queues (reader, punch, printer).
- zfcpdump_v2: Version 2 of the zfcpdump tool. Now based on the upstream Linux kernel 2.6.23.
Changes of existing tools:
- dbginfo.sh: Collect more debug data.
- lszfcp: Updated man page.
- mon_fstatd: Fixed error handling for invalid options.
- zipl: Update zipl to enable zfcpdump_v2.
- All tools: Use "-O3" compile option for all tools.
- tape390_crypt: -query results in wrong message if mt setblk has been used before.
- Query operation fails with message "Kernel does not support tape encryption".
- The query operation triggers a dummy read to enforce the key exchange between tape control unit and EKM. If the tape blocksize is not set to "auto", the read will fail, if the blocksize of the read request is smaller than the configured tape blocksize.
- Use max blocksize for dummy read.
- zconf/lsdasd: Passing a list of DASDs does not work properly.
- Showing only the last DASD from a given list of DASDs.
- The variable holding the DASDs is overwritten each time a parameter is analysed.
- Append DASDs to the list instead of overwriting it.
- zfcpdump: SCSI dump does not work in some cases.
- When a SCSI dump is started, it does not work and no messages are written to the console. This problem only occurs from time to time.
- Error handling of the 3215 console driver init function assumes, that a failure of the called ccw_device_probe_console() function is reported with a NULL pointer. Unfortunately this function mixes NULL pointer error reporting with the usage of the ERR_PTR macros. Therefore the 3215 code misinterpreted an ERR_PTR as valid return pointer. This can lead to a kernel panic.
- Always use the ERR_PTR macro for error reporting in the ccw_device_probe_console() function.
- zipl/dump tools: Memory detection sometimes does not work correctly.
- Error message "Device too small" and invalid dump.
- In the 64 bit memory detection code a 32 bit XOR operation is used to set a register to zero. If the leftmost four bytes of the register are not zero, after that operation the register will not be zero.
- Use 64 bit XOR operation.