Questions about Linux Kernel 2.6.28 or more defective and re-initiated on 208.5 days

See today a reprint as follows:

Linux Kernel 2.6.28 or more defective and re-initiated on the first 208.5 days

https://access.redhat.com/knowledge/solutions/68466

Sched_clock () overflow around 208.5 days in Linux kernellast modified by Raghu Udiyar on 04/10/12-09:12issue

• Linux Kernel panics when Sched_clock () overflows around 208.5 days
• Does RHEL 6.1 have a reboot problem which are caused by sched_clock () overflow around 208.5 days?

Environment

• Red Hat Enterprise Linux 6
• Kernel version earlier than kernel-2.6.32-220.4.2.el6
• TSC Clock Source
• Intel CPU

Linux Kernel 2.6.28 above is flawed, and after 208.5 days of activation, the event emerges pool table.

Sched_clock () overflow after 208.5 days in Linuxkernel (okkyの Galaxy Tumbler Chi Tan)

The flaw was found in the fact that the Pentium 4 of Intel-based CPUs (with compatible CPUs, 32bit/64bit) were discovered. Running on a virtual machine, or running a non-Intel-based CPU, is not discovered.

This flaw has been fixed in Linux Kernel 2.6.32.50/3.0.13/3.1.5. The response on each release is as follows.

Fedora 16: revised in Fedora Update:kernel-3.1.6-1.fc16.
Vine Linux 6: Fixed with core repair.
Red Hat Enterprise Linux 6: No revision core has yet been released. Please re-activate in 200 days after the activation to avoid the activity.
CentOS 6: The revised core has not yet been released. Please re-activate in 200 days after the activation to avoid the activity.
Debian 6.0: The revised core has not yet been released. Please re-activate in 200 days after the activation to avoid the activity.
Ubuntu 11.10: The revised core has not yet been released. Please re-activate in 200 days after the activation to avoid the activity.
Ubuntu 11.04: The revised core has not yet been released. Please re-activate in 200 days after the activation to avoid the activity.
Ubuntu 10.10: The revised core has not yet been released. Please re-activate in 200 days after the activation to avoid the activity.
Ubuntu 10.04 LTS: The revised core has not yet been released. Please re-activate in 200 days after the activation to avoid the activity.
SuSE One-SP1: can get PTF from support services.

Take a closer look at the explanation of Readhat:

Does Red Hat Enterprise Linux 6 or 5 has a reboot problem which iscaused by Sched_clock () overflow around 208.5 days? Updated, 8:54 AMGMTRate5 average:5 (1vote) Issue

• Linux Kernel panics when sched_clock() overflowsafter a uptime of around 208.5 days.
• Red Hat Enterprise Linux 6.1 system reboots with sched_clock () overflow after a uptime of around 208.5 days

Environment

• Red Hat Enterprise Linux 6

  • Red Hat Enterprise Linux 6.0, 6.1 and 6.2 are affected
  • Several kernels affected, see below
  • TSC Clock Source
  • Intel CPU

• Red Hat Enterprise Linux 5

  • Red Hat Enterprise Linux 5.3, 5.6, 5.8:please refer tothe sectionfor affected kernels resolution
  • Red Hat Enterprise Linux 5.0, 5,1, 5.2, 5.4, 5.5, 5.7:all kernelsaffected
  • TSC Clock Source
  • Intel CPU

• An approximate uptime of around 208.5 days.

From the above official statements can be seen when the conditional trigger:

1. Using the TSC clock source

2. Using Intel CPUs

3. The above series version and kernel-related

There may be an unusual risk of downtime

Can be turned off when boot, the method can refer to http://kb.vmware.com/selfservice/microsites/search.do?language=en_us&cmd=displaykc& externalid=1006427

Questions about Linux Kernel 2.6.28 or more defective and re-initiated on 208.5 days