From owner-freebsd-current  Fri Dec  7  9: 4:25 2001
Delivered-To: freebsd-current@freebsd.org
Received: from router.hackerheaven.org (qn-213-73-194-22.quicknet.nl [213.73.194.22])
	by hub.freebsd.org (Postfix) with ESMTP id 88B2037B416
	for <current@freebsd.org>; Fri,  7 Dec 2001 09:04:21 -0800 (PST)
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>
Subject: Re: [acpi-jp 1525] Re: ACPI causes immediate reboot [Omnibook 6100] ?
Message-ID: <20011207180349.A1944@laptop.hackerheaven.org>
Reply-To: acpi-jp@jp.freebsd.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/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.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.

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