System freezes after more than 208 days uptime
This document (7009834) is provided subject to the disclaimer at the end of this document.
------------[ cut here ]------------
WARNING: at /usr/src/packages/BUILD/kernel-default-18.104.22.168/linux-2.6.32/kernel/sched.c:3847 update_cpu_power+0x151/0x160()
---[ end trace 63f382152a7c7034 ]---
As far as we know the issue happens under the following conditions:
- CPU vendor is Intel
- /proc/cpuinfo contains both of the following CPU flags:
- dmesg and/or /var/log/boot.msg does not contain the string
Marking TSC unstable
- kernel flavor is not xen
Only if all four conditions are met the system is affected.
Be aware that this also affect any virtualisation that forward the CPU Flags to the guest (Xen,KVM,VMware)
The freeze/crash can happen anytime after 208 days uptime. It cannot happen before the system reaches 208 days uptime.
Since the issue happens due to an overflow of a CPU register it is strongly recommend to do a cold reboot. A warm reboot might not clear CPU/hardware registers.
A similar issue exists on SUSE Linux Enterprise Server on System z, except that it occurs after 417 days. Please refer to TID 000018212 System freezes after more than 417 days uptime for details and resolution.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7009834
- Creation Date: 01-Dec-2011
- Modified Date:14-Oct-2022
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com