Rhel6 versions with intel xeon processors, rhel6xeon
A few days ago, in the general "oracle O & M advanced group", BBQ said a RHEL bug, which is included in the following URL:
Https://access.redhat.com/solutions/433883
This problem does not occur on Red Hat Enterprise Linux 5 kernels.
We recommend that you install rhel6.5 in the production environment.
The details are described in the following post:
Https://access.redhat.com/solutions/433883
The full text below is reproduced:
Servers with Intel Xeon Processor E5, Intel Xeon Processor E5 v2, or Intel Xeon Processor E7 v2 and certain versions of Red Hat Enterprise Linux 6 kernels become unresponsive/hung or incur a kernel panic
Updated October 17 2014 at AM
Issue
The server becomes unresponsive with processes blocked in the uninterruptible state 'D', or it incurs a kernel panic 'ung _ task: blocked tasks '. in very rare circumstances the system's kernel can also crash/reboot due to an attempted divide-by-zero. please see the Diagnostic Steps section for further details about possible symptoms. the issue occurs if all of the following conditions are met.
- A Red Hat Enterprise Linux 6 kernel that contains this change from Red Hat private Bug 765720 is warm booted (for example, via
shutdown -r
Command ):
[sched] x86: Avoid unnecessary overflow in sched_clock
The kernel is warm booted on a machine with any of the Intel Xeon E5, Intel Xeon E5 v2, or Intel Xeon E7 v2 series processors.
The kernel is warm booted on a machine that has not been power cycled (hard reset) for a long time (typically more ~ 200 days ).
Notice that this does not mean that a kernel is affected if it has more ~ 200 days uptime. It is the warm boot after ~ 200 days of 'hardware uptime' that actually triggers the issue. The issue occurs at a random point in time after the warm boot, typically within the range of a few minutes to a few hours.
KVM guests (on rhel kvm hosts or RHEV-H hypervisors) that configure KVM clock as their clock source by default are not affected by the issue. For other implements alization platforms, please contact the platform vendor.
Red Hat Enterprise Linux 5 kernels that are based on upstream kernel version 2.6.18 are not affected by the issue.
Please see the Environment section for details about the versions of the Red Hat Enterprise Linux 6 kernel that are prone to the issue.
Environment
- Red Hat Enterprise Linux 6.1 (
kernel-2.6.32-131.26.1.el6
And newer)
- Red Hat Enterprise Linux 6.2 (
kernel-2.6.32-220.4.2.el6
And newer)
- Red Hat Enterprise Linux 6.3 (
kernel-2.6.32-279
Series)
- Red Hat Enterprise Linux 6.4 (
kernel-2.6.32-358
Series)
- Any Intel Xeon E5, Intel Xeon E5 v2, or Intel Xeon E7 v2 series processor
- The issue has been observed in the following environments with 64-bit kernels. Notice that 32-bit kernels of the above mentioned versions are prone to the issue too.
RHEL6.2 kernel version |
CPU model |
2.6.32-220.42.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2650 0 @ 2.00 GHz |
RHEL6.3 kernel version |
CPU model |
2.6.32-279.19.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2440 0 @ 2.40 GHz |
2.6.32-279.22.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2640 0 @ 2.50 GHz |
2.6.32-279.22.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2630 0 @ 2.30 GHz |
RHEL6.4 kernel version |
CPU model |
2.6.32-358. el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2670 0 @ 2.60 GHz |
2.6.32-358.0.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2640 0 @ 2.50 GHz |
2.6.32-358.6.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2640 0 @ 2.50 GHz |
2.6.32-358.6.2.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2650L 0 @ 1.80 GHz |
2.6.32-358.6.2.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2603 0 @ 1.80 GHz |
2.6.32-358.15.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-4617 0 @ 2.90 GHz |
2.6.32-358.18.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-4617 0 @ 2.90 GHz |
2.6.32-358.18.1.el6.x86 _ 64 |
Intel (R) Xeon (R) CPU E5-2690 0 @ 2.90 GHz |