From owner-acpi-jp@jp.freebsd.org  Sat Dec  8 02:04:30 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id CAA13762;
	Sat, 8 Dec 2001 02:04:30 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from router.hackerheaven.org (qn-213-73-194-22.quicknet.nl [213.73.194.22])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id CAA13757
	for <acpi-jp@jp.freebsd.org>; Sat, 8 Dec 2001 02:04:24 +0900 (JST)
	(envelope-from coolvibe@hackerheaven.dyndns.org)
Received: by router.hackerheaven.org (Postfix, from userid 1000)
	id 9467F1CA3; Fri,  7 Dec 2001 18:03:50 +0100 (CET)
Date: Fri, 7 Dec 2001 18:03:49 +0100
From: Emiel Kollof <coolvibe@hackerheaven.org>
To: acpi-jp@jp.freebsd.org
Cc: current@freebsd.org, Andy Sparrow <spadger@best.com>
Message-ID: <20011207180349.A1944@laptop.hackerheaven.org>
References: <20011124051109.593EE3E31@CRWdog.demon.co.uk> <px8elm7fcg4.wl@hunter.muc.macsch.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <px8elm7fcg4.wl@hunter.muc.macsch.com>
User-Agent: Mutt/1.3.23i
X-Mailer: Mutt 1.3.23i (2001-10-09)
X-Editor: Vim http://www.vim.org/
X-Info: http://www.hackerheaven.org/
X-Info2: http://www.cmdline.org/
X-Info3: http://www.coolvibe.org/
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1526
Subject: [acpi-jp 1526] Re: ACPI causes immediate reboot [Omnibook 6100] ?
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: coolvibe@hackerheaven.org

* Georg-W Koltermann (Georg.Koltermann@mscsoftware.com) wrote:
> Hi,
> 
> I CVSuped yesterday and still see the problem that was discussed in
> this thread, i.e. immediate reset during kernel initialization when
> ACPI is enabled on an HP Omnibook 6100.  The error message flies by so
> quickly that I cannot even read it.
> 
> Has there been any progress towards a solution?  What can I do to
> help?

If ACPI is broken for you, try setting debug.acpi.disable in
/boot/loader.conf.

Read acpi(4) manpage for more info on this. When all else fails, try
disabling "bus" or "children". Oh, and please report to this mailinglist
what works. Be sure to try all of 'em (maybe one of the driver
subsystems is faulty).

Cheers,
Emiel
-- 
Broad-mindedness, n.:
	The result of flattening high-mindedness out.
