Date: Wed, 05 Dec 2012 11:05:36 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Stefan Farfeleder <stefanf@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: ACPI panic Message-ID: <50BF0E60.30705@FreeBSD.org> In-Reply-To: <20121204085000.GA1445@mole.fafoe.narf.at> References: <20121125140008.GA1497@mole.fafoe.narf.at> <50B244A1.1040800@FreeBSD.org> <20121126091101.GA1469@mole.fafoe.narf.at> <50B33693.2060000@FreeBSD.org> <20121126093704.GB1469@mole.fafoe.narf.at> <50B34484.1090807@FreeBSD.org> <20121126104737.GC1469@mole.fafoe.narf.at> <50B34EEA.4000209@FreeBSD.org> <20121129084627.GA1450@mole.fafoe.narf.at> <50B7D717.4030402@FreeBSD.org> <20121204085000.GA1445@mole.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
on 04/12/2012 10:50 Stefan Farfeleder said the following: > These checks have not triggered additional panics. I still get the cycle > one. I am really out of ideas now on how that cycle could be created... :-( Perhaps, try to add another copy of the loop detection code to the place after an object is added to the cache list and before the mutex is released. And also, just in case, another copy to AcpiOsAcquireObject. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50BF0E60.30705>