Date: Thu, 28 Sep 2000 23:35:11 +0900 From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org> To: msmith@freebsd.org Cc: takawata@shidahara1.planet.sci.kobe-u.ac.jp, haro@tk.kubota.co.jp, current@freebsd.org, acpi-jp@jp.freebsd.org Subject: Re: My system hang with ACPI kernel thread Message-ID: <20000928233511G.iwasaki@jp.FreeBSD.org> In-Reply-To: <200009280952.e8S9qcA00717@mass.osd.bsdi.com> References: <200009280438.NAA63726@shidahara1.planet.sci.kobe-u.ac.jp> <200009280952.e8S9qcA00717@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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). Currently kernel thread seems broken, so mallocing storage in acpi_queue_event() never be freed. I think number of events at a point of tme is limited and we can have static storage for the events. The implementaion of sys/i386/apm/apm.c:apm_record_event() (it's for apmd) would be a good example. 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?20000928233511G.iwasaki>