From owner-freebsd-current Fri Sep 14 16:19: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2CF2637B40C; Fri, 14 Sep 2001 16:19:02 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8ENQW504850; Fri, 14 Sep 2001 16:26:32 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109142326.f8ENQW504850@mass.dis.org> To: Geoff Rehmet Cc: Mike Smith , Geoff Rehmet , Bosko Milekic , current@FreeBSD.ORG Subject: Re: ACPI??? was - Re: -current TCP performance hosed? In-Reply-To: Message from Geoff Rehmet of "Sat, 15 Sep 2001 01:08:28 +0200." <20010915010828.A21183@hermwas.is.co.za> Date: Fri, 14 Sep 2001 16:26:32 -0700 From: Mike Smith 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 > It seems that, on Fri, Sep 14, 2001 at 03:18:47PM -0700, > in message <200109142218.f8EMIl504199@mass.dis.org>, Mike Smith wrote: > > > Nope, no debug options, but I am getting loads of > > > > > > microuptime() went backwards (29804.3839847 -> 29804.925730) > > > > ALi chipset? Try turning off the ACPI timer if you haven't already; > > > > set debug.acpi.disable="timer" > > > > at the loader prompt. If this works, please let me know (with ACPI in the > > subject line so I don't miss it). > > Tried that, also tried "set hint.acpi.0.disable=1" - neither > had any effect. Can you explicitly disable the ACPI module? unset acpi_load at the loader prompt. If it still happens with that, then something else is b0rked and I can stop panicking. 8) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message