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 [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
