From owner-freebsd-current Thu Jan 23 12:59:46 2003 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 E6FB037B401 for ; Thu, 23 Jan 2003 12:59:42 -0800 (PST) Received: from mail.adelphia.net (pa-plum1b-166.pit.adelphia.net [24.53.161.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 110FA43F13 for ; Thu, 23 Jan 2003 12:59:37 -0800 (PST) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([172.16.0.95]) by mail.adelphia.net (8.12.3/8.12.3) with ESMTP id h0NL0vko003173 for ; Thu, 23 Jan 2003 16:00:57 -0500 (EST) (envelope-from wmoran@potentialtech.com) Message-ID: <3E3057BF.2090001@potentialtech.com> Date: Thu, 23 Jan 2003 15:59:43 -0500 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: calcru: negative time ... messages in 5.0-RELEASE Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I posted this to -STABLE on Monday, since then I've come to understand that -STABLE doesn't really include 5.0 (even though it's been released). That, combined with the fact that I received no answer, has propted me to post this to -CURRENT. Following is my original post: We're trying out 5.0-RELEASE on a test machine, and all is working well (so far) except for the continual "calcru: negative time ..." messages. I found information about this in the FAQ, but 5.0 doesn't seem to have a kern.timecounter.method oid. I also found information in the 5.0DP1 errata that pointed me to the -CURRENT mailing list, but a search of that list produced very little information, and the only thing to try (setting kern.timecounter.hardware=TSC) didn't change anything. Is there any more information on this? Is the last paragraph in the FAQ (that my interrupts are too hosed) applicable? Any pointers/help is appreciated. Since I posted this, I've gathered a little additional information: kern.timecounter.hardware is still set to TSC via sysctl.conf. It appears as though this has changed behaviour. We aren't seeing the calcru messages any more _except_ during boot, where they intermingle with the boot messages. Does this mean that the calcru problems are occurring during boot, until the sysctl is changed, and then they stop? Is this a reliable solution? dmesg output follows: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003 root@hollin.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0673000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06730a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 450130982 Hz CPU: AMD-K6(tm) 3D processor (450.13-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0xffffffff80000800 real memory = 62914560 (60 MB) avail memory = 54222848 (51 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Using $PIR table, 7 entries at 0xc00fa040 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0x50000000-0x5fffffff at device 0.0 on pci0 atapci0: port 0x2040-0x204f,0-0x3,0-0x7,0-0x3,0-0x7 at device 0.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0x40200000-0x40200fff irq 11 at device 1.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: device problem, disabling port 1 pcib1: at device 2.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) rl0: port 0x2400-0x24ff mem 0x41000000-0x410000ff irq 3 at device 4.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:c0:ca:14:03:eb miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 10.0 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: