From owner-freebsd-current Sun Feb 24 11:14:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from etek.chalmers.se (quarl0.etek.chalmers.se [129.16.32.20]) by hub.freebsd.org (Postfix) with ESMTP id EE50D37B416; Sun, 24 Feb 2002 11:14:14 -0800 (PST) Received: from downy.etek.chalmers.se (_7-268@downy.etek.chalmers.se [129.16.32.207]) by etek.chalmers.se (8.10.0/8.8.8) with ESMTP id g1OJEDV28686; Sun, 24 Feb 2002 20:14:13 +0100 (MET) Received: from localhost (b@localhost) by downy.etek.chalmers.se (8.10.0/8.10.0) with ESMTP id g1OJEDu09112; Sun, 24 Feb 2002 20:14:13 +0100 (MET) Date: Sun, 24 Feb 2002 20:14:12 +0100 (MET) From: Magnus B{ckstr|m To: Mike Smith Cc: current@freebsd.org Subject: Re: HEADS UP: ACPI CA updated In-Reply-To: <20020222215647.A54975@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wow! This did away with the once-a-minute error messages from Notify()s on processor objects on my laptop. However, I am now getting frequent panics from from a GIANT_REQUIRED assertion in kmem_malloc(). kmem_malloc() gets called via malloc() from AcpiOsAllocate(), without Giant locked. The call to AcpiOsAllocate() happens deep in a AML object evaluation in from acpi_tz_thread(). I tried naively to modify AcpiOsAllocate to grab Giant before malloc() and release it afterward, but this appears to be a very bad idea: There is a mtx_assert(&Giant, MA_NOTOWNED) in ithread_loop() in kern/kern_intr.c which blows up during boot. Regards, Magnus On Fri, 22 Feb 2002, Mike Smith wrote: > Subject: HEADS UP: ACPI CA updated > > > I've finally updated the ACPI CA codebase with Intel's 20020214 drop > (yes, I tagged it 0217, my bad). > > This is the first drop that Intel haven't asked me not to commit since > the 20011120 version, so there are a large number of changes and > bugfixes. See Intel's logs at > http://developer.intel.com/technology/iapc/acpi for more details. > > There aren't many changes in the FreeBSD-specific code, this is just > catching up with major improvements in the interpreter. > > As usual, please report any problems or success to the list. > > Regards, > Mike > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message