Version number of RHEL6 used Intel Xeon Processor Time bug

Unfortunately in the first few days "Oracle operation and maintenance of the high-level team" on. BBQ God says a lot of rhel bugs. This bug in this example, the following URL:
https://access.redhat.com/solutions/433883

There is no problem with Red Hat Enterprise Linux 5 kernels.

It is also recommended that you install the rhel6.5 version number in a production environment.

The detailed description is described in the following posts:

https://access.redhat.com/solutions/433883

The following full text 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 pani C

Updated October at 1:49 AM

Issue

The server becomes unresponsive with processes blocked in the uninterruptible state ' D ', or it incurs a kernel panic ' hung _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 sections for further details about possible symptoms. The issue occurs if all of the following conditions is met.

• A Red Hat Enterprise Linux 6 kernel that contains this change from the Red Hat private Bug 765720 is warm booted (for example, via the 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 this has no been power cycled (hard reset) for a long time (typically more than XX days).

Notice that this does isn't mean that a kernel is affected if it had more than ~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) the Configure KVM clock as their clock source by default is not AFF Ected by the issue. For other virtualization platforms, please contact the platform vendor.

Red Hat Enterprise Linux 5 kernels that is based on upstream kernel version 2.6.18 is not affected by the issue.

Please see the environment sections for details on the versions of the Red Hat Enterprise Linux 6 kernel that is prone to the issue.

Environment

• Red Hat Enterprise Linux 6.1 (and kernel-2.6.32-131.26.1.el6 newer)
• Red Hat Enterprise Linux 6.2 (and kernel-2.6.32-220.4.2.el6 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 have been observed in the following environments with 64-bit kernels. Notice that 32-bit kernels of the above mentioned versions is 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.00GHz

RHEL6.3 kernel version	CPU Model
2.6.32-279.19.1.el6.x86_64	Intel (R) Xeon (r) CPU e5-2440 0 @ 2.40GHz
2.6.32-279.22.1.el6.x86_64	Intel (R) Xeon (r) CPU e5-2640 0 @ 2.50GHz
2.6.32-279.22.1.el6.x86_64	Intel (R) Xeon (r) CPU e5-2630 0 @ 2.30GHz

intel (R) Xeon (R) CPU e5-2640 0 @ 2.50GHz

RHEL6.4 kernel version	CPU model
2.6.32-358.el6.x86_64	Intel (R) Xeon (r) CPU e5-2670 0 @ 2.60GHz
2.6.32-358.0.1.el6.x 86_64	Intel (R) Xeon (r) CPU e5-2640 0 @ 2.50GHz
2.6.32-358.6.1.el6.x86_64
2.6.32-358.6.2.el6.x86_64	Intel (R) Xeon ( R) CPU e5-2650l 0 @ 1.80GHz
2.6.32-358.6.2.el6.x86_64	Intel (R) Xeon (r) CPU e5-2603 0 @ 1.80GHz
2.6.32-358.15.1.el6.x86_64	Intel (R) Xeon (r) CPU e5-4617 0 @ 2.90ghz
2.6.32-358.18.1.el6.x86_64	Intel (R) Xeon (r) CPU e5-4617 0 @ 2.90GHz
2.6.32-358.18.1.el6.x86_64	Intel (R) Xeon (r) CPU e5-2690 0 @ 2.90GHz

Copyright notice: This article Bo Master original articles, blogs, without consent may not be reproduced.

Version number of RHEL6 used Intel Xeon Processor Time bug