Date: Thu, 1 Aug 2002 17:24:10 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: obrien@freebsd.org Cc: freebsd-current@freebsd.org, iwasaki@jp.FreeBSD.org Subject: Re: kernel panic on boot, acpica related? Message-ID: <15689.42746.415219.256369@grasshopper.cs.duke.edu> In-Reply-To: <20020801173021.GB82778@dragon.nuxi.com> References: <3D49307C.5050903@gmx.net> <20020801221434X.iwasaki@jp.FreeBSD.org> <20020801173021.GB82778@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15689.42746.415219.256369>