From owner-freebsd-current@FreeBSD.ORG Thu Oct 2 12:01:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C14CC16A4B3 for ; Thu, 2 Oct 2003 12:01:44 -0700 (PDT) Received: from lagash.satanosphere.com (216-210-218-82.atgi.net [216.210.218.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABDE843FE9 for ; Thu, 2 Oct 2003 12:01:41 -0700 (PDT) (envelope-from jeremy@lagash.satanosphere.com) Received: (from jeremy@localhost) by lagash.satanosphere.com (8.12.9/8.12.9) id h92J9qfE061158 for freebsd-current@freebsd.org; Thu, 2 Oct 2003 12:09:52 -0700 (PDT) (envelope-from jeremy) Date: Thu, 2 Oct 2003 12:09:52 -0700 From: Jeremy Bingham To: freebsd-current@freebsd.org Message-ID: <20031002190952.GB60400@lagash.satanosphere.com> References: <20030930144703.W81965@root.org> <20030930220658.GA51513@lagash.satanosphere.com> <20031001162256.GB55082@lagash.satanosphere.com> <20031001170457.GA55275@lagash.satanosphere.com> <20031001112435.C85421@root.org> <20031002190806.GA60400@lagash.satanosphere.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eAbsdosE1cNLO4uF" Content-Disposition: inline In-Reply-To: <20031002190806.GA60400@lagash.satanosphere.com> User-Agent: Mutt/1.4i Sender: jeremy@satanosphere.com X-PGP-Key: http://home.satanosphere.com/jeremy-pubkey.asc Subject: Re: Problem w/ ACPI in -CURRENT: Update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2003 19:01:44 -0000 --eAbsdosE1cNLO4uF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 01/10/03 11:28 -0700, Nate Lawson wrote: > dmesg is not necessary. The only way to find what is hanging is to keep > working printfs deeper into the _BIF method. Start with > AcpiEvaluateObject in sys/contrib/dev/acpica/nsxfeval.c and sprinkle > printf A, B, C etc. throughout to find where it hangs. Alternatively, if > you have a serial console and gdb, you can step through the method. >=20 > -Nate I think I've tracked the offending line down, in sys/contrib/dev/acpia/spar= se.c Status =3D WalkState->AscendingCallback (WalkState); The line shows up several times in the file, but that's the first occurance of it in the file. Interestingly, the function that line's in (or the while loop) does seem to be successfully run a few times before it fails. Is there anything else I should be looking for? I've looked around the source tree trying to figure out exactly what AscendingCallback is, but I'm not finding anything. -j =20 ---------------------------------------------- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ jeremy@satanosphere.com --eAbsdosE1cNLO4uF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE/fHf/z9BfgBOfXn0RAjWnAKDI2lFfXjJvjxkAaF0Y2YsBcy7oPwCdGNcH 3tG+Qk6iWcdltNNVrgpYcMw= =pVtk -----END PGP SIGNATURE----- --eAbsdosE1cNLO4uF--