Date: Wed, 23 Mar 2005 13:41:48 -0800 From: Nate Lawson <nate@root.org> To: Warner Losh <imp@bsdimp.com> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_perf.c Message-ID: <4241E29C.7010407@root.org> In-Reply-To: <20050323.143742.74706153.imp@bsdimp.com> References: <1111516858.1198.2.camel@localhost> <424079AB.6050805@root.org> <1111611460.1805.1.camel@localhost> <20050323.143742.74706153.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote:
>>>Ok, I've committed a fix: acpi.c rev 1.207. Please cvsup and test.
>>
>>It does not help, still same panic
>
>
> It doesn't help me either, and an audit of the code suggests that it
> will have no effect. There's a resource that's marked as being
> active, which is why the panic is happening.... I've always hated
> these panics, but have appreciated them in hindsight once the bug has
> been fixed because it is a very effective enforcement of proper
> operations.
>
> Warner
I'm trying to figure out what's going on. The probe routine should not
be called multiple times since it returns 0 and now with my commit it
should completely clean up after itself. Can you put this in
acpi_perf_identify, probe, attach and let me know the full dmesg up to
the panic?
printf("%s called\n", __func__);
--
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4241E29C.7010407>