Red Hat Training

A Red Hat training course is available for Red Hat Enterprise Linux

Chapter 25. Kernel

kernel component, BZ#1019091
The following RAID controller cards are no longer supported. However, the aacraid driver still detects them. Thus, they are marked as not supported in the dmesg output.
  • PERC 2/Si (Iguana/PERC2Si)
  • PERC 3/Di (Opal/PERC3Di)
  • PERC 3/Si (SlimFast/PERC3Si)
  • PERC 3/Di (Iguana FlipChip/PERC3DiF)
  • PERC 3/Di (Viper/PERC3DiV)
  • PERC 3/Di (Lexus/PERC3DiL)
  • PERC 3/Di (Jaguar/PERC3DiJ)
  • PERC 3/Di (Dagger/PERC3DiD)
  • PERC 3/Di (Boxster/PERC3DiB)
  • Adaptec 2120S (Crusader)
  • Adaptec 2200S (Vulcan)
  • Adaptec 2200S (Vulcan-2m)
  • Legend S220 (Legend Crusader)
  • Legend S230 (Legend Vulcan)
  • Adaptec 3230S (Harrier)
  • Adaptec 3240S (Tornado)
  • ASR-2020ZCR SCSI PCI-X ZCR (Skyhawk)
  • ASR-2025ZCR SCSI SO-DIMM PCI-X ZCR (Terminator)
  • ASR-2230S + ASR-2230SLP PCI-X (Lancer)
  • ASR-2130S (Lancer)
  • AAR-2820SA (Intruder)
  • AAR-2620SA (Intruder)
  • AAR-2420SA (Intruder)
  • ICP9024RO (Lancer)
  • ICP9014RO (Lancer)
  • ICP9047MA (Lancer)
  • ICP9087MA (Lancer)
  • ICP5445AU (Hurricane44)
  • ICP9085LI (Marauder-X)
  • ICP5085BR (Marauder-E)
  • ICP9067MA (Intruder-6)
  • Themisto Jupiter Platform
  • Callisto Jupiter Platform
  • ASR-2020SA SATA PCI-X ZCR (Skyhawk)
  • ASR-2025SA SATA SO-DIMM PCI-X ZCR (Terminator)
  • AAR-2410SA PCI SATA 4ch (Jaguar II)
  • CERC SATA RAID 2 PCI SATA 6ch (DellCorsair)
  • AAR-2810SA PCI SATA 8ch (Corsair-8)
  • AAR-21610SA PCI SATA 16ch (Corsair-16)
  • AAR-2610SA PCI SATA 6ch
  • ASR-2240S (SabreExpress)
  • ASR-4005
  • ASR-4800SAS (Marauder-X)
  • ASR-4805SAS (Marauder-E)
  • ASR-3800 (Hurricane44)
  • Adaptec 5400S (Mustang)
  • Dell PERC2/QC
  • HP NetRAID-4M
The following cards detected by aacraid are also no longer supported but they are not identified as not supported in the dmesg output:
  • IBM 8i (AvonPark)
  • IBM 8i (AvonPark Lite)
  • IBM 8k/8k-l8 (Aurora)
  • IBM 8k/8k-l4 (Aurora Lite)


Note that the Kdump mechanism might not work properly on the aforementioned RAID controllers.
kernel component, BZ#1061210
When the hpsa_allow_any option is used, the hpsa driver allows the use of PCI IDs that are not listed in the driver's pci-id table. Thus, cards detected when this option is used, are not supported in Red Hat Enterprise Linux 7.
kernel component, BZ#975791
The following cciss controllers are no longer supported:
  • Smart Array 5300
  • Smart Array 5i
  • Smart Array 532
  • Smart Array 5312
  • Smart Array 641
  • Smart Array 642
  • Smart Array 6400
  • Smart Array 6400 EM
  • Smart Array 6i
  • Smart Array P600
  • Smart Array P800
  • Smart Array P400
  • Smart Array P400i
  • Smart Array E200i
  • Smart Array E200
  • Smart Array E500
  • Smart Array P700M
kernel component, BZ#1055089
The systemd service does not spawn the getty tool on the /dev/hvc0/ virtio console if the virtio console driver is not found before loading kernel modules at system startup. As a consequence, a TTY terminal does not start automatically after the system boot when the system is running as a KVM guest. To work around this problem, start getty on /dev/hvc0/ after the system boot. The ISA serial device, which is used more commonly, works as expected.
kernel component, BZ#1060565
A previously applied patch is causing a memory leak when creating symbolic links over NFS. Consequently, if creating a very large number of symbolic links, on a scale of hundreds of thousands, the system may report the out of memory status.
kernel component, BZ#1097468
The Linux kernel Non-Uniform Memory Access (NUMA) balancing does not always work correctly in Red Hat Enterprise Linux 7. As a consequence, when the numa_balancing parameter is set, some of the memory can move to an arbitrary non-destination node before moving to the constrained nodes, and the memory on the destination node also decreases under certain circumstances. There is currently no known workaround available.
kernel component, BZ#915855
The QLogic 1G iSCSI Adapter present in the system can cause a call trace error when the qla4xx driver is sharing the interrupt line with the USB sub-system. This error has no impact on the system functionality. The error can be found in the kernel log messages located in the /var/log/messages file. To prevent the call trace from logging into the kernel log messages, add the nousb kernel parameter when the system is booting.
system-config-kdump component, BZ#1077470
In the Kernel Dump Configuration window, selecting the Raw device option in the Target settings tab does not work. To work around this problem, edit the kdump.conf file manually.
kernel component, BZ#1087796
An attempt to remove the bnx2x module while the bnx2fc driver is processing a corrupted frame causes a kernel panic. To work around this problem, shut down any active FCoE interfaces before executing the modprobe -r bnx2x command.
kexec-tools component, BZ#1089788
Due to a wrong buffer size calculation in the makedumpfile utility, an OOM error could occur with a high probability. As a consequence, the vmcore file cannot be captured under certain circumstances. No workaround is currently available.