Red Hat Enterprise Linux systems using the TSC clock source reboots or panics when 'sched_clock()' overflows after an uptime of 208.5 days

Solution Verified - Updated -

Issue

  • Linux Kernel panics when sched_clock() overflows after an uptime of around 208.5 days
  • Red Hat Enterprise Linux system reboots with sched_clock() overflow after an uptime of around 208.5 days
  • This symptom may happen on a system using the Time Stamp Counter (TSC) clock source
  • Some processes may generate following log message:
BUG: soft lockup - CPU#N stuck for 4278190091s!

Environment

  • Red Hat Enterprise Linux (RHEL) 6
    • Red Hat Enterprise Linux 6.0 (some kernels)
    • Red Hat Enterprise Linux 6.1 (some kernels)
    • Red Hat Enterprise Linux 6.2 (some kernels)
    • With TSC clock source
  • Red Hat Enterprise Linux (RHEL) 5
    • Red Hat Enterprise Linux 5.0
    • Red Hat Enterprise Linux 5.1
    • Red Hat Enterprise Linux 5.2
    • Red Hat Enterprise Linux 5.3 (some kernels)
    • Red Hat Enterprise Linux 5.4
    • Red Hat Enterprise Linux 5.5
    • Red Hat Enterprise Linux 5.6 (some kernels)
    • Red Hat Enterprise Linux 5.7
    • Red Hat Enterprise Linux 5.8 (some kernels)
    • With TSC clock source
  • Red Hat Enterprise MRG 1.3 Realtime kernel
  • An approximate uptime of around 208.5 days

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In