From owner-freebsd-current Thu Sep 28 2:51:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id C2EDA37B422 for ; Thu, 28 Sep 2000 02:51:22 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8S9qcA00717; Thu, 28 Sep 2000 02:52:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009280952.e8S9qcA00717@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Takanori Watanabe Cc: Munehiro Matsuda , current@freebsd.org, acpi-jp@jp.freebsd.org Subject: Re: My system hang with ACPI kernel thread In-reply-to: Your message of "Thu, 28 Sep 2000 13:38:57 +0900." <200009280438.NAA63726@shidahara1.planet.sci.kobe-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 02:52:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >With the addition of ACPI kernel thread, my system hangs in about > >10 miniutes use after boot up. By disabling kernel thread, system > >runs just fine. > > > >Do you have any idea where to look at? > >I'll try and see what I can do myself. > > Please set debug.aml_debug and debug.acpi_debug to 1 and > see what will happen. It wouldn't surprise me if the system wasn't running out of kernel memory. Right now we just keep mallocing storage to queue ACPI events (bad idea). The entire event/Notify stuff needs to be somewhat rethought (eg. I think we need an event filter). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message