Date: Tue, 13 Nov 2012 17:14:48 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Tom Lislegaard <Tom.Lislegaard@proact.no> Cc: freebsd-acpi@FreeBSD.org Subject: Re: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_unreserve: can't find resource] Message-ID: <50A263E8.2060707@FreeBSD.org> In-Reply-To: <E8A24BEFDC390C4491718DEE8A9C4F20924820@Semail03.proact.local> References: <E8A24BEFDC390C4491718DEE8A9C4F2091F824@Semail03.proact.local> <E8A24BEFDC390C4491718DEE8A9C4F2091FC33@Semail03.proact.local> <5092F209.7090803@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20920DD1@Semail03.proact <5093BECC.1030709@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20921BAC@Semail03.proact.local> <50979BCD.3060000@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20921C47@Semail03.proact.local> <5097CB27.8040802@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20921C6A@Semail03.proact.local> <5097F24D.7040206@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F209220E2@Semail03.proact.local> <50995C8F.3040309@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20922E13@Semail03.proact.local> <509B8F15.4030300@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20922F57@Semail03.proact.local> <509BDF86.3080502@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F2092347A@Semail03.proact.local> <509D091A.8080108@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20924820@Semail03.proact.local>
next in thread | previous in thread | raw e-mail | index | archive | help
on 13/11/2012 17:09 Tom Lislegaard said the following: > > >> -----Original Message----- >> From: Andriy Gapon [mailto:avg@FreeBSD.org] >> Sent: 9. november 2012 14:46 >> To: Tom Lislegaard >> Cc: freebsd-acpi@FreeBSD.org >> Subject: Re: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_unreserve: can't find >> resource] >> >> on 09/11/2012 14:17 Tom Lislegaard said the following: >>> kgdb) up 7 >>> #7 0xffffffff802d1bdd in AcpiOsAcquireObject (Cache=0xfffffe00052bac60) at >> /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 >>> 316 ACPI_DEBUG_PRINT ((ACPI_DB_EXEC, >>> (kgdb) x/9a Cache->ListHead >>> 0xfffffffeec85c730: Cannot access memory at address 0xfffffffeec85c730 >> >> [Slaps forehead] Ah, right, indeed.on >> I guess the problem hasn't happened again since then? >> Does the patch appear to work OK so far (with respect to the original problem)? >> > You're right, I haven't had any occurrence of the 'resource_list_unreserve' panic since the original patch. OK. Good news. Thank you! > The patch below works badly on my system. I notice that certain processes start to hang, for instance during boot I have to interrupt /etc/rc.d/initrandom to continue. Xorg also hangs and if I log in on another terminal I see the process is in processorstate 'acmtx'. Yeah... Please revert it. When I said that it was experimental, I was under-estimating its level of incompleteness :-( I have a better patch, which I tested at least. I'll send it to you soon-ish. > The kernel msg buffer is full of messages like this > > ACPI Error: Could not acquire AML Interpreter mutex (20110527/exutils-107) > ACPI Exception: AE_ERROR, Thread 100076 could not acquire Mutex [0x8] (20110527/utmutex-315) > ACPI Error: Mutex [0x8] is not acquired, cannot release (20110527/utmutex-359) > ACPI Error: Mutex [0x0] is not acquired, cannot release (20110527/utmutex-359) > ACPI Error: Could not release AML Interpreter mutex (20110527/exutils-177) > >> I have a suspicion about what causes the new problem. >> If it is correct then the following experimental patch may help with it: [bad patch snipped] -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50A263E8.2060707>