From owner-acpi-jp@jp.freebsd.org  Thu Sep 28 19:30:51 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id TAA36806;
	Thu, 28 Sep 2000 19:30:51 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (daemon@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id TAA36801
	for <acpi-jp@jp.freebsd.org>; Thu, 28 Sep 2000 19:30:50 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e8SAUmr80101;
	Thu, 28 Sep 2000 19:30:48 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: takawata@shidahara1.planet.sci.kobe-u.ac.jp
Cc: haro@tk.kubota.co.jp, current@freebsd.org, acpi-jp@jp.freebsd.org
In-Reply-To: <200009280438.NAA63726@shidahara1.planet.sci.kobe-u.ac.jp>
References: <20000928101721L.haro@tk.kubota.co.jp>
	<200009280438.NAA63726@shidahara1.planet.sci.kobe-u.ac.jp>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000928193031R.iwasaki@jp.FreeBSD.org>
Date: Thu, 28 Sep 2000 19:30:31 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 15
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 680
Subject: [acpi-jp 680] Re: My system hang with ACPI kernel thread
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

> In message <20000928101721L.haro@tk.kubota.co.jp>, Munehiro Matsuda wrote:
> 
> >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.

I could find a couple of possibilities from VersaProNX.asl; lack of
SleepOp or EC I/O.  If the former, I can try to write it as well as
StallOp tonight, of course Intel ACPICA compatible one.
