Date: Wed, 1 Oct 2003 11:28:45 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Jeremy Bingham <jeremy@satanosphere.com> Cc: freebsd-current@freebsd.org Subject: Re: Problem w/ ACPI in -CURRENT: Update Message-ID: <20031001112435.C85421@root.org> In-Reply-To: <20031001170457.GA55275@lagash.satanosphere.com> References: <20030930144703.W81965@root.org> <20030930220658.GA51513@lagash.satanosphere.com> <20031001162256.GB55082@lagash.satanosphere.com> <20031001170457.GA55275@lagash.satanosphere.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Oct 2003, Jeremy Bingham wrote:
> On 01/10/03 09:33 -0700, Nate Lawson wrote:
> > > > As far as debugging prints, add the following printfs to
> > > > acpi_cmbat_get_bif():
> > > >
> > > > printf("Before getting BIF\n");
> > > > as = AcpiEvaluateObject(h, "_BIF", NULL, &bif_buffer);
> > > > printf("After getting BIF\n");
> > > >
> > > > -Nate
> >
> > Ok, that's good to know. How about the printfs? Did the second one
> > trigger? I could use a URL to your ASL and full dmesg on boot:
>
> The second one did not trigger (I had actually been using ACPI_VPRINT
> for a while to get info like that). I have a dump of my ASL here:
> http://home.satanosphere.com/bsd/jeremy.asl.gz.
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.
-Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031001112435.C85421>