From owner-freebsd-current@FreeBSD.ORG Tue Mar 16 23:12:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CF2916A4D1 for ; Tue, 16 Mar 2004 23:12:12 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4497D43D39 for ; Tue, 16 Mar 2004 23:12:11 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i2H7Bt4V004415; Wed, 17 Mar 2004 08:12:09 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Don Bowman From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Mar 2004 22:04:32 EST." Date: Wed, 17 Mar 2004 08:11:55 +0100 Message-ID: <4414.1079507515@critter.freebsd.dk> cc: "'current@freebsd.org'" Subject: Re: equivalent of kern.timecounter.method? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2004 07:12:12 -0000 Can you check that both the periodic interrupts actually fire ? critter phk> vmstat -i interrupt total rate irq0: clk 85613519 99 <<< irq1: atkbd0 1222031 1 irq6: fdc0 2 0 irq7: ppc0 1 0 irq8: rtc 109586318 127 <<< irq9: acpi0 1638 0 In message , Don Bo wman writes: > >in 4.x there is a sysctl kern.timecounter.method. >If this isn't set to '1', the system doesn't work >correctly (at least with SMP), you get microuptime() >backwards, and problems with processes hanging >while time catches up, etc. > >What is the equivalent of this sysctl in 5.x? > >kern.timecounter.nbinuptime: 6810682 >kern.timecounter.nnanouptime: 4 >kern.timecounter.nmicrouptime: 2218 >kern.timecounter.nbintime: 7091 >kern.timecounter.nnanotime: 172 >kern.timecounter.nmicrotime: 6919 >kern.timecounter.ngetbinuptime: 0 >kern.timecounter.ngetnanouptime: 490 >kern.timecounter.ngetmicrouptime: 30909 >kern.timecounter.ngetbintime: 0 >kern.timecounter.ngetnanotime: 0 >kern.timecounter.ngetmicrotime: 187117 >kern.timecounter.nsetclock: 4 >kern.timecounter.hardware: ACPI-fast >kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-1000000) >kern.timecounter.tick: 1 >kern.timecounter.smp_tsc: 0 > >is what i have. > >I'm having a problem with this machine sometimes hanging... >sometimes for 5-10s, sometimes permanently (?). When hung, >everything (serial console, etc) is locked. This includes >the key-sequence to drop to db on the serial. > >I'm not sure the time and the hang are related, but there's >a suspicious ntpd message just before the hang, >kernel time discipline status [2041, 2040, etc] > >5.2.1-RELEASE-p1 (RELENG_5_2) is what its running, with the (absolutely >critical ufs_vnops.c fix of 1.235). > >The only thing the machine runs is postgresql. > >Suggestions on how to debug this lockup? > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.