--XF85m9dhOBO43t/C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 07, 2005 at 06:57:47PM +0100, Vincent wrote:
> >As noted, /sbin/init can cause issues. Another problem may be if libc is=
=20
> >updated to use a new call that isn't there; ALL programs can crash. I=20
> >remember when we went to having getcwd() based on a system call. If you=
=20
> >used a new userland (that expected the system call) with an old kernel=
=20
> >(that didn't have it), most every program crashed. I don't know if init=
=20
> >crashed then, but I think every shell did. :-)
>=20
> I was specifically thinking about that.
> Anyway, related question : how to debug the kernel when the failure=20
> consists in unescapable reboots after the "acpibat" message ?
>=20
> If anybody has a clue, I'll be glad to catch it ;)

All I can think is to add printf()s after that message and keep trying.=20
You should be able to find out which call is crashing (since all the=20
subsequent printf()s won't print), then figure out what is being passed=20
in.

Beyond that I can't help much as I don't know ACPI at all well.

Take care,

Bill

--XF85m9dhOBO43t/C
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFCLJ7BWz+3JHUci9cRAqKIAJ9iTV26Vi4XaATuj1Eo9kEo8RiXgwCcC7bh
FWomvtnWJDfG8zzYPPjz7EE=
=4B/n
-----END PGP SIGNATURE-----

--XF85m9dhOBO43t/C--