Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 394581

Summary: Enforce report_lost_ticks boot time parameter in time.c
Product: Red Hat Enterprise Linux 5 Reporter: John Sobecki <john.sobecki>
Component: kernelAssignee: Prarit Bhargava <prarit>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: low    
Version: 5.1CC: bmaly, dzickus, prarit
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0314 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 15:02:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
enforce report_lost_ticks
none
RHEL5 fix for this issue none

Description John Sobecki 2007-11-21 16:47:49 UTC
Description of problem:

During high database load testing (Oracle OLT) the kernel issues both of
these lost tick related warning messages:

1) kernel: warning: many lost ticks.
   kernel: Your time source seems to be instable or some driver is 
           hogging interupts

2)  kernel: Losing some ticks... checking if CPU frequency changed.

Version-Release number of selected component (if applicable):

2.6.18.*

How reproducible:

Under large Oracle OLT load testing, with 1000+ processes, this can
be reproduced 100% of the time. 

Steps to Reproduce:
1. Create Oracle DB
2. Load OLT test kit (available at htto://oss.oracle.com/projects/olt)
3. Run large load with 1000+ processes
  
Actual results:

Machine will slow and kick out multiple lost ticks messages.
Expected results:

Only print lost ticks messages if booted with 'report_lost_ticks'.

Additional info:

Customer noticed this after they switched from SLES9 to RHEL5; in SLES9
there is only one place where lost ticks warnings are printed, and it
includes an if (report_lost_ticks) check before the code block.

Comment 1 John Sobecki 2007-11-21 16:47:49 UTC
Created attachment 266131 [details]
enforce report_lost_ticks

Comment 4 Prarit Bhargava 2007-11-27 18:48:50 UTC
Created attachment 270051 [details]
RHEL5 fix for this issue

Updated patch.

Comment 5 RHEL Program Management 2007-12-06 00:15:33 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 7 Don Zickus 2007-12-17 19:37:42 UTC
in 2.6.18-61.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Comment 10 errata-xmlrpc 2008-05-21 15:02:14 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0314.html