From owner-acpi-jp@jp.FreeBSD.org Tue Mar 16 04:14:57 2004
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id i2FJEv737130;
	Tue, 16 Mar 2004 04:14:57 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet id i2FJEu737125
	for <acpi-jp@jp.FreeBSD.org>; Tue, 16 Mar 2004 04:14:56 +0900 (JST)
	(envelope-from faber@ISI.EDU)
Received: from pun.isi.edu (pun.isi.edu [128.9.160.150])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i2FJEtp20196;
	Mon, 15 Mar 2004 11:14:55 -0800 (PST)
Received: from pun.isi.edu (localhost [127.0.0.1])
	by pun.isi.edu (8.12.10/8.12.10) with ESMTP id i2FJEpDE034835;
	Mon, 15 Mar 2004 11:14:55 -0800 (PST)
	(envelope-from faber@pun.isi.edu)
Received: (from faber@localhost)
	by pun.isi.edu (8.12.10/8.12.10/Submit) id i2FJEjRO034834;
	Mon, 15 Mar 2004 11:14:45 -0800 (PST)
	(envelope-from faber)
From: Ted Faber <faber@ISI.EDU>
To: Nate Lawson <nate@root.org>
Cc: acpi-jp@jp.FreeBSD.org
Message-ID: <20040315191445.GG62226@pun.isi.edu>
References: <20040315144849.GB62226@pun.isi.edu> <20040315094731.Q89517@root.org> <20040315180010.GE62226@pun.isi.edu> <20040315104457.X89855@root.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="kbCYTQG2MZjuOjyn"
Content-Disposition: inline
In-Reply-To: <20040315104457.X89855@root.org>
User-Agent: Mutt/1.4.2.1i
X-url: http://www.isi.edu/~faber
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Mon, 15 Mar 2004 11:14:45 -0800
X-Sequence: acpi-jp 3110
Subject: [acpi-jp 3110] Re: [faber@ISI.EDU: [faber@ISI.EDU: power mgmt woes on CURRENT with Dell Latitude C610]]
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: faber@ISI.EDU
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+040307


--kbCYTQG2MZjuOjyn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Mar 15, 2004 at 10:46:55AM -0800, Nate Lawson wrote:
> On Mon, 15 Mar 2004, Ted Faber wrote:
> > On Mon, Mar 15, 2004 at 09:48:25AM -0800, Nate Lawson wrote:
> > > You can go back to using apm by uncommenting "device apm" and recompiling
> > > your kernel.
> >
> > They don't seem to play nice together, to the tune of "can't boot with
> > both apm and acpi enabled."  :-( And as I said, I can't seem to boot
> > without ACPI running.  I can provide errors on the apm && acpi failure
> > mode if that's helpful.
> 
> After making sure the system works with acpi disabled at the loader
> prompt, do this:
> echo hint.acpi.0.disabled=\"1\" >> /boot/loader.conf
> 
> This is all in the acpi(4) manpage.

I'm apparently not being clear.

I understand how to disable acpi using the tunable.  Any time that
tunable is set to 1 or the machine is booted without the acpi.ko module
loaded, the laptop panics on boot in the way described in the first
message:

}Booting without ACPI stops at 0xc00fc42f with "Fatal trap 12: page fault
}while in kernel mode." Typing trace at the debug prompt gives:
}kernbase(b0a, c075684d, c00fbc50, c00fbc52, c0c21a9c) at 0xc00fc42f
}I couldn't get a dmesg from that.

The laptop will not boot without acpi.

> > >               Unfortunately, you probably won't be able to boot without
> > > acpi because of the bug that results in your system panicing.  That is an
> > > important bug to fix as it is a problem with BIOS32 calls.
> >
> > Is acpi-jp the right place to bring that up?  I'm just trying to find
> > the guy who can tweak this into working.  Because all is well under
> > -STABLE, including power management, it seems like booting w/o ACPI and
> > with APM would be the shortest route to happiness for me.
> 
> The underlying problem running without ACPI is already being looked at.

OK.  If I can provide input to that process, I'm happy to.  That's all I
was trying to get across.

> -stable is entirely different than -current.  Feel free to stick to apm if
> it works for you.

I do not have a working power management system on this laptop under
current.  If I did, I wouldn't be bugging you, I promise.

When I disable acpi with or without apm enabled, the system panics during
boot as I described above.  Running without acpi is not currently an
option for me.  (Yes, I tried it with apm enabled.)

When I try to run with apm and acpi both enabled, the system panics in a
different way on boot which I haven't described to you in the same
detail, but which I would be happy to fill in for you.

Because I cannot boot without acpi and cannot boot with both acpi and
apm enabled, running with apm is not a possibility for me.  My hope that
apm might work for me under current is only a hope, faintly fueled by my
good experience with stable.  I understand that this is only a hope.  I
currently have no way to test this possibility.  I cannot run with apm
enabled.

When acpi is enbled alone with or without the tunable
hw.acpi.disable_on_poweroff set, a suspend to S3 either from zzz or from
acpiconf causes the machine to power cycle.  As a result I have no way
to suspend the laptop, though I can boot it.

Either being able to boot w/o acpi and trying apm *or* having acpi
suspend the hardware for me would delight me.  I'm happy to run patches
and provide output, but I just don't have time to learn enough acpi to
be an active coding help here.  If no help is forthcoming, I understand.

-- 
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG 

--kbCYTQG2MZjuOjyn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAVgClaUz3f+Zf+XsRAsAJAKDwoJL/33cjzJOQpFuA6XgXZsTH3gCeJVc+
0C9jUB4IHnQbvtXr1lvFnh4=
=DhUW
-----END PGP SIGNATURE-----

--kbCYTQG2MZjuOjyn--
