From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 19 02:30:24 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CE7816A4D0 for ; Thu, 19 Aug 2004 02:30:24 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171C243D5E for ; Thu, 19 Aug 2004 02:30:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i7J2UNEe015910 for ; Thu, 19 Aug 2004 02:30:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7J2UN0k015908; Thu, 19 Aug 2004 02:30:23 GMT (envelope-from gnats) Resent-Date: Thu, 19 Aug 2004 02:30:23 GMT Resent-Message-Id: <200408190230.i7J2UN0k015908@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Suihong Liang Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B38DF16A4CE for ; 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 ; 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 ; 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 To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: kern/70649: system clock slows down when heavily loaded X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2004 02:30:24 -0000 >Number: 70649 >Category: kern >Synopsis: system clock slows down when heavily loaded >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Aug 19 02:30:23 GMT 2004 >Closed-Date: >Last-Modified: >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: >Unformatted: