From nobody@FreeBSD.org  Thu Aug 19 02:28:05 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B38DF16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 19 Aug 2004 02:28:05 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ABCED43D45
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 19 Aug 2004 02:28:05 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i7J2S5v7066246
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 19 Aug 2004 02:28:05 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i7J2S5fv066240;
	Thu, 19 Aug 2004 02:28:05 GMT
	(envelope-from nobody)
Message-Id: <200408190228.i7J2S5fv066240@www.freebsd.org>
Date: Thu, 19 Aug 2004 02:28:05 GMT
From: Suihong Liang <s2liang@uwaterloo.ca>
To: freebsd-gnats-submit@FreeBSD.org
Subject: system clock slows down when heavily loaded
X-Send-Pr-Version: www-2.3

>Number:         70649
>Category:       kern
>Synopsis:       [rtc] system clock slows down when heavily loaded
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 19 02:30:23 GMT 2004
>Closed-Date:    Wed Oct 12 15:09:34 UTC 2011
>Last-Modified:  Wed Oct 12 15:09:34 UTC 2011
>Originator:     Suihong Liang
>Release:        5.2.1
>Organization:
Univeristy of Waterloo
>Environment:
FreeBSD hurricane.cs.uwaterloo.ca 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #2: Fri Jul  2 16:25:54 GMT 2004     root@hurricane.cs.uwaterloo.ca:/usr/src/sys/i386/compile/ORIGIN  i386
>Description:
      It takes "SHORTER" time in scp a file while heavily loaded, in
fact, the receiver shows that it takes LONGER!

I think the kernel does not handle the system clock well when it is heavily loaded.

I've tried the built-in time, GNU time, and my simple home-brewed timer programs, same result was yielded.

>How-To-Repeat:
      1. cpu workload program can be a infinite loop program.
2. In my testing, I run 32 instances of such workload programs.
3. Use command "time" to time the scp in an ethernet environment. Do NOT trust the time reported by scp.
4. I used the same set of 30 files (each of 100MB).
5. reboot the sender after each set of scp is done.
>Fix:
      
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: jh 
State-Changed-When: Fri Sep 23 19:18:02 UTC 2011 
State-Changed-Why:  
Can you still reproduce this on recent FreeBSD versions? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=70649 
State-Changed-From-To: feedback->closed 
State-Changed-By: remko 
State-Changed-When: Wed Oct 12 15:09:33 UTC 2011 
State-Changed-Why:  
Feedback timeout 

http://www.freebsd.org/cgi/query-pr.cgi?pr=70649 
>Unformatted:
