Bug 746092 - RHEL4.8: Fix time of gettimeofday() going backward (EM64T)
Summary: RHEL4.8: Fix time of gettimeofday() going backward (EM64T)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 20:50 UTC by Matthew Whitehead
Modified: 2012-06-20 15:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 15:55:03 UTC
Target Upstream Version:

Attachments (Terms of Use)
reproducer code (2.23 KB, application/octet-stream)
2011-10-13 20:54 UTC, Matthew Whitehead 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Matthew Whitehead 2011-10-13 20:50:47 UTC 
Description of problem: Time goes backwards on RHEL4.8 with x86_64 Harpertown L5240 2.GHz cpu with multiple cores active.


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


How reproducible: 100% with reproducer code


Steps to Reproduce:
1. g++ ttt.cc -o ttt -lpthread
2. ./ttt
3. Look for "found negative delta" message.
  
Actual results: Time goes backwards.


Expected results: Time should be monotonic.


Additional info: Please assign to Prarit Bhargava, per his request.
Comment 1 Matthew Whitehead 2011-10-13 20:54:43 UTC 
Created attachment 528101 [details]
reproducer code
Comment 2 Jiri Pallich 2012-06-20 15:55:03 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.
Note You need to log in before you can comment on or make changes to this bug.