From owner-freebsd-stable@FreeBSD.ORG Thu Dec 2 18:54:10 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F0D616A4CF for ; Thu, 2 Dec 2004 18:54:10 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04A9F43D4C for ; Thu, 2 Dec 2004 18:54:10 +0000 (GMT) (envelope-from avleeuwen@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so320870rns for ; Thu, 02 Dec 2004 10:54:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ubt8KRjdv2yFA1S6aNUArrO/lqeiCXMKw7SHeDRrx6jQ26RTOkvAEYvY2xhhF6DACuvFZApFMH4grC9V9tOOMZzU3R+hzb8F827uxXWsFWIrFuT4piSRWM3Gsvg50AoKo6fS20ozY4KUBTk2kF/x03MHktfNkP3pg/3NJS/ismc= Received: by 10.38.179.40 with SMTP id b40mr2291542rnf; Thu, 02 Dec 2004 10:54:09 -0800 (PST) Received: by 10.38.206.16 with HTTP; Thu, 2 Dec 2004 10:54:08 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 19:54:08 +0100 From: Arjan Van Leeuwen To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Timecounter problems on 5.3 - things take twice as long X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Arjan Van Leeuwen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 18:54:10 -0000 Hi, I have a weird problem on a dual Xeon 550MHz system running 5.3-RELEASE. Everything takes twice as long as it should. Example: winston% time sleep 2 sleep 2 0.00s user 0.00s system 0% cpu 4.006 total The same for pings, the scsi delay when booting, etc. The time of the system itself doesn't seem to be affected (but maybe ntpd takes care of that). I tried changing the kern.timecounter.hardware sysctl from ACPI-safe to TSC and i8254, but that didn't help. Any other suggestions on how to fix this? Do I have to provide more information? Arjan