Date: Mon, 10 Feb 2003 19:18:53 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: Fredde <fredde@borg.cx> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: ACPI related issue with 5.0R on a compaq evo n160 Message-ID: <20030210191853.D50606@freebie.xs4all.nl> In-Reply-To: <3E47A097.40201@borg.cx>; from fredde@borg.cx on Mon, Feb 10, 2003 at 01:52:39PM %2B0100 References: <3E47A097.40201@borg.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 10, 2003 at 01:52:39PM +0100, Fredde wrote:
> Hi,
>
> I have this strange(?) problem with the acpi drivers in 5.0-R on my
> laptop, it's a compaq evo n160 (perhaps it has a broken acpi
> implementation).
"It works fine with Windows"...
> When I boot the system with acpi enabled, it detects alot of acpi
> "devices" on the machine but when the kernel is done detecting all
> hardware and is about to enter multiuser mode the system freezes (or
> goes in to sleepmode or something...) and a hard shutdown is required.
> Booting in verbose mode, the last line to show up is
> start_init: trying /sbin/init
> then, nothing more.
> But the machine doesn't completly freeze becase if i close the lid
> acpi reports "lid closed", "lid open".
> Another note is that if I leave the machine in this state for a while,
> the fan goes on, which tells that the cpu usage probably is at 100%.
Then it gets further down the road than my N160 with 5.0R...
See also:
Date: Sun, 26 Jan 2003 21:16:15 +0100
From: Wilko Bulte <wkb@freebie.xs4all.nl>
Subject: ACPI locks up during boot on Compaq EVO N10
To: freebsd-mobile@freebsd.org
Hi,
I could use some expert advice on the following.
I recently loaded 5.0-RELEASE on my Compaq EVO N160 laptop.
Given that this is a newish laptop which really depends on
ACPI FreeBSD 5 is the way to go. 4.7-stable runs fine on it,
but lacks all power management etc.
Unfortunately during boot the machine locks up with a couple
of ACPI messages. This happens just after the "Mounting root"
message.
ACPI says:
ACPI-0331: Connot release mutex [MUT0], not acquired
ACPI-1287: error: method execution failed, AE_AML_MUTEX_NOT_ACQUIRED
> Disabling acpi (hint.acpi.0.disabled=1) solves it, but I really would
> want acpi (battery status and such things). Another thing is that apci
> worked (as far as I can remember) on the same machine when I tried
> 5.0-current last summer.
Hmm, I got panics then, but I don't remember when I tried it exactly.
--
| / o / /_ _ FreeBSD core team secretary
|/|/ / / /( (_) Bulte wilko@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030210191853.D50606>