From owner-freebsd-current  Sat Dec  2 23:56:37 2000
Delivered-To: freebsd-current@freebsd.org
Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5])
	by hub.freebsd.org (Postfix) with ESMTP id 3BEE237B400
	for <freebsd-current@freebsd.org>; Sat,  2 Dec 2000 23:56:35 -0800 (PST)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id eB37uRk98118;
	Sun, 3 Dec 2000 16:56:27 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: nsayer@quack.kfu.com
Cc: freebsd-current@freebsd.org, acpi-jp@jp.freebsd.org
Subject: Re: ACPI and Sony laptop
In-Reply-To: <3A2975B8.6D757E65@quack.kfu.com>
References: <3A2975B8.6D757E65@quack.kfu.com>
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: <20001203165627S.iwasaki@jp.FreeBSD.org>
Date: Sun, 03 Dec 2000 16:56:27 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 32
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

> Also, if I compile device acpica into the kernel, it hangs probing and
> attaching ACPI stuff. In particular, it gets a little further if I put
> an ENXIO at the start of acpi_tz's attach routine, but after doing that
> a couple times in acpi_*_attach() I gave up. I don't see a lot in the
> recent archives of -current, so either everyone but me is running with
> ACPI happily or everyone knows to keep away. I'm not sure which. :-)

I have 3 machines with ACPI BIOS here, I have no serious problems
with ACPICA code luckly (or unfortunately? :-) 
However It seems that there are some bugs in ACPI CA code, acpi-jp
folks and some developers from Intel are discussing this sometimes at
acpi-jp@jp.freebsd.org.

The problem you are having is reported by VAIO Z505JX user; some ACPI
methods seems cause infinite loop within the method.
Unfortunately we haven't find the effective solutions for it.  Could
you disable dev/acpica/acpi_*.c lines in sys/conf/files and see which
module cause this hang?

Oh yes, and please dump your Z505JE's DSDT data with `acpidump -o' and
send it for us.  This would be useful for debugging.

> Those paying attention on -hackers know I've offered a prize for a
> jogdial driver. I've gotten some stuff off the web and am hoping to take
> a crack at a spic driver (Sony Programmable I/O Controller), but I think
> I need working ACPI first.

Sounds interesting :-)

Thanks


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message