relayfs previously had a buffer size limit of 64MB. In this update, the limitation of the memory allocated to relayfs for on-memory buffers has been increased to 4095MB. This allows SystemTap and other tracing tools that utilize relayfs the ability to trace more events.
The driver for Dell Remote Access Controller 4 (DRAC4) was not present. Consequently, any virtual devices provided by the DRAC4 were not being detected by the kernel. In this update, the pata_sil680 kernel module that provides the appropriate driver has been added, which resolves this issue.
The message buffers for the relay interface were only allocated for online CPUs when relay_open() was called. Consequently, if an off-line CPU was turned on after relay_open() was called, a kernel panic would occur. In this update, a new message buffer is allocated dynamically if any new CPUs are added.
The driver for 8250 based serial ports has been updated to add support for DSR/DTR hardware flow control.
Support for
Dell Wireless Wide Area Network (WWAN) cards has been added to the kernel. Devices that are now supported are:
Dell Wireless 5700 Mobile Broadband CDMA/EVDO Mini-Card
Dell Wireless 5500 Mobile Broadband HSDPA Mini-Card
Dell Wireless 5505 Mobile Broadband HSDPA Mini-Card
Dell Wireless 5700 Mobile Broadband CDMA/EVDO ExpressCard
Dell Wireless 5510 Mobile Broadband HSDPA ExpressCard
Dell Wireless 5700 Mobile Broadband CDMA/EVDO Mini-Card
Dell Wireless 5700 Mobile Broadband CDMA/EVDO Mini-Card
Dell Wireless 5720
Dell Wireless HSDPA 5520
Dell Wireless HSDPA 5520
Dell Wireless 5520 Voda I Mobile Broadband (3G HSDPA) Mini-Card
the thinkpad_acpi kernel module has been updated to provide enhanced support for newer Thinkpad models.
The soft lockup detector can now be configured to trigger a kernel panic instead of a warning message. This makes it possible for users to generate and analyze a crash dump during a soft lockup for forensic purposes.
To configure the soft lockup detector to generate a panic, set the kernel parameter soft_lockup to 1. This parameter is set to 0 by default.
oprofile did not correctly identify processors based on the Next-Generation Intel Microarchitecture (Nehalem). Consequently, the performance monitoring unit could not be used and the processor fell back to the timer interrupt. The kernel has been updated to resolve this issue.
Support has been added to the kernel for the CPU power state, C3, on the Next-Generation Intel Microarchitecture (Nehalem). The ability to enter C3 (also known as the sleep state) improves the power efficiency of the CPU when idle.
Previously, the
MAX_ARG_PAGES limit that is set in the kernel was too low, and may have resulted in the following error:
execve: Argument list too long
In this update, this limit has been increased to 25 percent of the stack size, which resolves this issue.
autofs4 updates have been backported to Red Hat Enterprise Linux 5.3 from linux kernel version 2.6.27.
Red Hat Enterprise Linux 5.3 now includes the ability to specify that core files be piped to a forked copy of a user space application, rather than directly to a file. This is enabled by placing | path/to/applicationin /proc/sys/kernel/core_pattern. When a core is dumped, a copy of the specified application will be executed, and the core will be piped to it on stdin. This allows for the core to be augmented, analyzed and actively handled at core dump time.
The file /proc/cpuinfo now reports the ID of the Advanced Programmable Interrupt Controller (APIC) that is used by each individual CPU.
The Machine Check Exception (MCE) kernel subsystem has been enhanced to support larger memory configurations as needed by new systems.
The mount command now supports Kerberos authentication when mounting filesystems via Samba. The sec=krb5 or sec=krb5i switch allows the kernel to call a userspace application (cifs.upcall) which returns a SPNEGO (Simple and Protected GSSAPI Negotiation Mechanism) security blob (Binary Large OBject). The kernel can then use this blob to authenticate with the server and mount the requested filesystem.
If you configured the kernel parameter kernel.unknown_nmi_panic on a system that used the IOAPIC NMI watchdog method, a kernel panic could occur. This is because the NMI watchdog could not disable the source of NMIs securely.
With this release, the NMI watchdog code has been revised to allow users to safely disable the NMI source. As such, you can now safely configure the kernel parameter kernel.unknown_nmi_panic on systems that use the IOAPIC NMI watchdog method.