From owner-freebsd-current Thu Aug 1 14:24:45 2002 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 94ACC37B400; Thu, 1 Aug 2002 14:24:42 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6B8843E5E; Thu, 1 Aug 2002 14:24:41 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA26071; Thu, 1 Aug 2002 17:24:40 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g71LOAi17212; Thu, 1 Aug 2002 17:24:10 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15689.42746.415219.256369@grasshopper.cs.duke.edu> Date: Thu, 1 Aug 2002 17:24:10 -0400 (EDT) To: obrien@freebsd.org Cc: freebsd-current@freebsd.org, iwasaki@jp.FreeBSD.org Subject: Re: kernel panic on boot, acpica related? In-Reply-To: <20020801173021.GB82778@dragon.nuxi.com> References: <3D49307C.5050903@gmx.net> <20020801221434X.iwasaki@jp.FreeBSD.org> <20020801173021.GB82778@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 David O'Brien writes: > On Thu, Aug 01, 2002 at 10:14:34PM +0900, Mitsuru IWASAKI wrote: > > Hmmm, I don't think so. How about typing > > unset acpi_load > > in loader prompt, and see if this panic disappear or still happen? > > Where is it documented what to do to stop the autoloading of acpi.ko? I tend to not build modules because -current is so slow. When I do, I just move it to acpi.broken.ko.. Now, to attempt to hijack your thread: I really wish somebody could tell me why my ServerWorks LE based PIII generates about 20 messages like this: ACPI-1046: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[20], disabling event For each ethernet (fpx0) interrupt I get. If that didn't happen, I'd love to use acpi. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message